Eric Schlegel wrote:
>> Can you name a single non-apple framework based on carbon?
>
> MacApp, PowerPlant, MacZoop, SWT, Nitrogen (not really a framework,
> but close enough).
Wrong answers.
MacApp:
MacApp is no longer active. (besides, it is an Apple product.)
PowerPlant:
This is the one denounced by Steve Jobs.
MacZoop:
If <http://www.maczoop.com/future.html> is accurate, it is at
least as dead as MacApp and PowerPlant.
The page states:
"As of May 1st, 2003, it has been decided to terminate ongoing
development of MacZoop. [...]"
"MacZoop has kept pace up to the level of Jaguar,
but new technologies within Carbon and the OS are
making it increasingly difficult to keep pace,
and at the same time less attractive and beneficial to
do so. [...]"
And I agree. However, MacZoop is a free software. A commercial
product vendor cannot afford to make a comment like this.
And not keeping up with Apple's latest scares users away.
"However, for longer term developments or where you
are starting a larger project, you may prefer to
consider Cocoa as an alternative."
MacZoop is a C++ framework, so migrating from it to Objective-C
is not that painful.
SWT:
Don't know much about it, but I doubt it can be kept up to date
with Mac OS X. (Cocoa is said to have dropped Java support btw.)
> > Are you sure? WaitNextEvent based event dispatch is oblivious
> > to what composite windows are doing behind the scene. How can
> > they work together?
>
> In the context of Florian's specific problem, compositing status of a
> window doesn't change how the window handles text input, so it's
> irrelevant in this case. In general, however, event handlers are
> always called within WaitNextEvent as appropriate, so you can still
> use WaitNextEvent for your main loop, and install event handlers on
> any event target, and they'll be called properly.
The point is that I do not use WaitNextEvent. It is used by the
framework I use. Actually I did not have to be aware of
WaitNextEvent (I hardly knew how it works) until OSX.
And I know I can install carbonevent handlers. I use them
here & there because I have to.
> You won't get
> updateEvts out of WaitNextEvent for compositing windows, of course,
> and you wouldn't get mouseDown events either since those would be
> dispatched via Control Manager events.
Perhaps I could use composite windows if I try hard enough like
tracing hidden carbonevents by TraceEventByName just as you
suggested. However, I need to do that precisely because a WNE based
framework and composite windows do not work together.
_______________________________________________
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
