On Monday 22 October 2007 12:47, Eric Schlegel wrote:
> Maybe you should use fewer widgets? Neither HIToolbox nor AppKit are
> really tuned to handle that many views very well. Qt might not be
> either.
Yup... there is always the option of making my own "uber widgets" wherein I
have my own internal "widget tree" and do all the appropriate event handling
logic, etc myself.
OTOH, that seems like a huge amount of redundant code, and even if I
implemented it all there's no guarantee that my GUI implementation would be
much faster than TrollTech's or Apple's version (after all, their engineers
are much smarter than me ;^))
Add to that the fact that TrollTech seems like they are already headed in that
direction for their library (the still-in-development Qt 4.4.x has been
redesigned to present just a single window-sized uber-widget to the OS, with
Qt handling the widget hierarchy in an opaque manner... although it sounds
like they may not implement that mode under MacOS/X, alas)... and it seems
even more like "rolling my own" would be a waste of time in the long run.
And even if there is a way to optimize my GUI code to be "fast enough" to run
in a single thread, there will always be another app (or a later version of
my app) that will want to do more in the GUI... and as we go from dual core
to quad core to 16 core, the potential speedup to be had by allowing multiple
GUI threads will only get larger.
So while there are doubtless other ways to solve this particular problem, it
would still be cool to have a multi-process GUI solution too.
IMHO :^)
-Jeremy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
