On Jun 30, 2006, at 12:03 AM, Laurence Harris wrote:
Frankly, this is not a sensible use of Carbon events. Events are
meant to communicate that something has happened. They're not a
long-term data storage mechanism.
If we wanted to do something like this, the right API would be
one that let you attach your dictionary directly to the window:
SetWindowPersistentInfo( window, dictionary ), or something like
that. A Carbon event is not an appropriate solution.
Not only that, but why are we talking about 32-bit OSTypes? Why
limit ourselves to the namespace of OSTypes when we have the
infinite reverse-DNS namespace of UTIs to work with? :) One of the
limitations of the resource manager is unless you already knew
every type of resource, it wasn't always clear at a glance what a
ResType identified.
OTOH, ResTypes are simpler to use and more efficient than strings
of arbitrary length. I just don't know that the demand for resource
support will ever be large enough to need the infinite set of
reverse-DNS namespace of UTIs.
True, but that's what they said about 32-bit IP addresses too :). In
either case, I wouldn't expect the Resource Manager itself to start
playing around with UTIs; the chances of Apple actually working on
that manager again to that extent are practically nil. I was thinking
more in regards to the CF/CE APIs that were being discussed, which
are places that I'd expect Apple to be trying to move away from
limited namespaces.
-- Gwynne, daughter of the Code
"This whole world is an asylum for the incurable."
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
