A book on Gtkmm

[Al-Burak]

Ever since I started tinkering around the GTK+ and later on Gtkmm
toolkits, I've noticed a steady flow of programmers talking more and
more, and more passionately, about these toolkits.

It came as a blessing when "Sams Teach Yourself GTK+ Programming in 21
Days" was put on the bookstores' shelves in the year 2000. I remember
having to line up at the teller and noticing that two out of five
people had this book in their baskets or under their arms. That was my
queue to get on my newly installed Linux box and start typing GTK+
code, sooner than later, I said to myself, this toolkit will become a
bread maker. Six years have gone by and there are very few programmers
who don't know what GTK+ is, and they are now making bread with it
(that is. are making money with it, in case you don't get my meaning).
I have found many GUI applications written in the C++ paradigm, but
using GTK+ code, which we fondly called "GTK++ code". The reason these
programmers are doing this is because it is easy to learn from a book,
since it can be taken to an unoccupied boardroom or a coffee shop. I
have found myself reading for hours in front of the computer,
neglecting my own biological needs because I cannot take the PC to
attend to them, or in buses or airplanes wishing I was able to just
pull a book and continue reading more about Gtkmm. The flexibility that
printed information provides is undoubtedly unmatchable.

The documentation of Gtkmm is substantial and reach with examples,
however, for some programmers, like myself, who find the eloquence of a
book as important as the dry and tacit information it tries to convey,
as well the ability to carry that information to more convenient places
very important, a book on Gtkmm would come as true blessing.

Gtkmm is no longer a baby child of GTK+, it has become a young adult
deserving of recognition and a status of independence. A book on Gtkmm
*must be written, there is no other option, and this must be done
before new programmers start to drift away, to a less powerful, but
more flexibly documented toolkit.

[mlimber]

Al-Burak wrote:

Ever since I started tinkering around the GTK+ and later on Gtkmm
toolkits, I've noticed a steady flow of programmers talking more and
more, and more passionately, about these toolkits.

It came as a blessing when "Sams Teach Yourself GTK+ Programming in 21
Days" was put on the bookstores' shelves in the year 2000. I remember
having to line up at the teller and noticing that two out of five
people had this book in their baskets or under their arms. That was my
queue to get on my newly installed Linux box and start typing GTK+
code, sooner than later, I said to myself, this toolkit will become a
bread maker. Six years have gone by and there are very few programmers
who don't know what GTK+ is, and they are now making bread with it
(that is. are making money with it, in case you don't get my meaning).
I have found many GUI applications written in the C++ paradigm, but
using GTK+ code, which we fondly called "GTK++ code". The reason these
programmers are doing this is because it is easy to learn from a book,
since it can be taken to an unoccupied boardroom or a coffee shop. I
have found myself reading for hours in front of the computer,
neglecting my own biological needs because I cannot take the PC to
attend to them, or in buses or airplanes wishing I was able to just
pull a book and continue reading more about Gtkmm. The flexibility that
printed information provides is undoubtedly unmatchable.

The documentation of Gtkmm is substantial and reach with examples,
however, for some programmers, like myself, who find the eloquence of a
book as important as the dry and tacit information it tries to convey,
as well the ability to carry that information to more convenient places
very important, a book on Gtkmm would come as true blessing.

Gtkmm is no longer a baby child of GTK+, it has become a young adult
deserving of recognition and a status of independence. A book on Gtkmm
*must be written, there is no other option, and this must be done
before new programmers start to drift away, to a less powerful, but
more flexibly documented toolkit.

This post is off-topic in this newsgroup. See the FAQ for what is
on-topic here and for some suggestions on better places to post:

http://www.parashift.com/c++-faq-lit...t.html#faq-5.9

Cheers! --M

[Al-Burak]

Well, I am glad you noticed.

Thanks.
PD
I work during the afternoons and most of the night, but I notice that
you replied to this message in the early hours of the morning. I guess
you are one of those people getting a cup of coffee at the nearest
coffee-shop-drive-thru at the time when I am coming from work. I have
not had a cup of coffee in the morning for a very long time, I miss
those days when I could see the sun rise holding on to a huge mug
filled with coffee. I used to love the way steam rose from the mug. But
having a sip of coffee in the morning during the fall season was the
best, the way my breath mixed with the steam coming from the coffee mug
cooling it down. Ahh, there is no better life than the one in the
Northern countries.
Have a good day!
By the way, I am sure that by the time I start typing a reply to you
message you were at the gym or having fun with your loved ones.
Well, if you would like to have a quick chat, please, don't hesitate
to write back. Pay no attention to those people complaining about you
ideas being off topic, since most them are the kind of people that are
always being pooped on by others; they are the only ones who take any
and every opportunity to show that they can and will poop on others if
they are given the chance, my advice... don't get angry at them, just
pity them.
Again, have great day!!