Bill Pringlemeir wrote: >> I think they are two different uses/meanings. On Mon, 7 Jun 2004, [EMAIL PROTECTED] wrote:
> I see this but to me it's rather subtle. I changed it because I > thought it was wrong or at least read somewhat awkward. If CVS would > work ATM, I or someone else would gratefully apply your suggestions. Well, to start with I just wondered if some English professor from Oxford had emailed you requesting the change. ;-) I am not expert on English grammar. It just seemed strange to me and I wondered why the change. I work with many developers (China, Czech, Solvak, Slovinean, Serbian, Indian, Veitnamize, Japanese, Rumanian, Brazilian, Belgian and French); English is not at all a criteria for being a good developer! I am certainly aware that it is a very confusing language. Then again, the x86 is probably one of the worse CPU instruction sets, but 90+% of computers use it... someone likes irony. >> btw. That was my only nit in the many recent changes. Although I >> glossed over the GTK2 changes, because I don't know a lot about GTK >> (or at least less than 'C'). > In my experience, you really have to *use* GTK+ to understand it and > find appropriate usage schemes. The documentation itself doesn't > mention a lot of subtle things and you often have to peek at the > source code to decide what's better or worse. There are mainly two > things that suck especially in GLib/GTK+ 2.x. First, the excessive > use of dynamically allocated memory. In theory that's cleaner but it > causes severe performance penalties due to memory copies (cache > killer) and can easily cause memory leaks. The other bad thing is > the internal use of UTF-8. That's OK for accessing files but > internal and for the GUI you want to use a flat encoding. Thanks, I am learning little by little. I have used Zinc, Windows (basic API), several embedded GUIs, 3274, 5250, 2392, and Atari GEM. Most Gui frame works suffer from the malloc issue. Doug Lea wrote his allocator initially to address this. Any C++ book I have read always uses graphics (elements) as an examples. I think that "dynamically allocated memory" and GUIs go hand in hand. The best idea is something like SLABs that *nix kernel people developed. I think the observer pattern using function callbacks is more central. This is much different than event loops. At least that is what I understand so far about GTK... Maybe I am mislead by "event.h". I haven't seen any event queues though, so I think that is right. Regards, Bill Pringlemeir. ------------------------------------------------------- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
