On Wed, 6 Dec 2017 12:10:35 +0100
"R.Wieser"  wrote:

> > Once you have decided to use GTK+
>
> You skip over that as if that only needs a few seconds to do.   In my
> case I was not even aware of several of such environments being
> available, much less which one would be the best/obvious choice.

 Right so the first thing most of us did was to inform you that
there were several alternatives and advise you to take a look at them so
you could pick one.

> I even had to *fight* to get you guys to acknowledge that GTK would
> probably be the best choice, seeing that I was running lxpanel, and it
> was rather easy to program for.

 Mainly because it might not be the best choice, you may find after
looking at them that Qt or SDL or fltk or any one of a bunch of others
suits you better. How can you find out if you don't have a look.

> > As you have found yourself once the choice is made the
> > mechanics are fairly simple
>
> Yep.  And thats your second 20-20 vision (looking backwards from a "I
> already know that!" position) fuck-up.   ONCE THE CHOICE IS MADE.

 Not at all, I (and others) urged you to take a look at the options
and make a choice.

> Pray tell, *how* (on basis of what? ) should I have made that choice ?
> What the **** do you think I was asking my question for ?

 On the basis of what you saw when you took a look at the tutorial
material for the various options of course.

 On what basis do you think anyone else could advise you better ?

> I was *hoping* that, with a bit of help of this forum, I could shorten
> that time a bit and skip the wild-goosechase.  Alas, no such luck. :-(

 But you could - many people suggested that GTK would be a natural
first one to look at. You chose to look no further.

> > But if the only reply had been a set of step by step instructions that
> > you could cut and paste and a sample program to copy then:
> >
> > a) You would learn nearly nothing from it
>
> You mean those 4 *configuration* (once-off) steps that I needed to do to
> fucking start the thing I was actually after, being GUI programming ?
> Yeah, that really makes sense.  Not.

 

> > b) You would get the impression that this was the one true
> > way of doing things when in fact there's no such thing
>
> Did I already mention that I already program on Windows ?   Yea, I think
> I did.  You *might* have taken that as a clue that I've already passed
> that station.

 You clearly had NOT passed that station because you were not aware
that, unlike Windows, GUI programming under unix involves choosing which
framework you want to use because there isn't one built in.

> Especially when such a choice could lead to me picking something which
> would cause making a GUI program unneedfully more complex for a novice.

 Yes it could - we have no idea what you find easy. Most of the
frameworks exist because someone didn't like all the others.

> > c) You wouldn't know where to go for the next steps other than
> > back here to ask.
>
> Yep.  If someone asks you should *never* reply to them with something he
> can actually use.  Better "shoo" him off, never to bother you again.
> Good going dude!

 Well hey nobody here is being paid to help you, most of us aim to
get people started on learning how to help themselves.

> Idiot.   That is a response you give *after* someone abuses your help,
> not the first thing you do.   And believe me, I have had my fill of such
> people.

 I tried to help - you don't get it.

> > If each of us had provided step by step instructions like this
> > for our favourite approach you would probably have drowned
> > in confusion.
>
> Literally *four* lines that I (effectivily) needed, and than "drowned in
> confusion" ?   Really ?

 Ah now you are being an idiot - suppose you had seen step by step
instructions for GTK+, Qt, SDL, fltk and a dozen others each with people
chiming in correcting mistakes and so on.

> What you are mentioning is *exactly* what the "there is the lake, I won't
> give you a fish (slams door)" method has led to: I had to wade thru a
> mess of confusing stuff in the hope I could find bits-and-pieces which,
> when combined correctly, would lead to a workable(! as in, still no clue
> if its a correct or best) solution.

 It is correct if it works, there is no best.

> The whole problem was that *I didn't know what I was after*.  And the
> likes of you made sure I was kept that way.  :-((
>
> You see, *after I was aware what I needed* to be able to write a GUI
> program (those 4 lines, the GTK direction and how to access it) I was
> well able to google and figure out the rest for myself.

 Right and you still have no idea whether you would have preferred
Qt, SDL, fltk or something else or even what the differences are between
them. Had you followed my advice then you would have taken longer to get to
the point of seeing something happen but you would have learned a lot more
about the world you're entering.

--
Steve O'Hara-Smith                          |   Directable Mirror Arrays
C:\>WIN                                     | A better way to focus the sun
The computer obeys and wins.                |    licences available see
You lose and Bill collects.                 |    http://www.sohara.org/

--- SoupGate-Win32 v1.05