Not sure if that is as good of an idea - from the docs:
Due to the amount of uncertainty about the environment at the
point that load is invoked, you should avoid using load whenever
possible.
Well, this is mitigated a lot for loadable bundles, though. There,
you're pretty much guaranteed that the app has already been loaded,
you just shouldn't use any other classes in your bundle yet. But
getting your own class object and adding it to an NSMutableArray in
the app itself is hunky-dory.
Which will work fine and dandy up until the point where you decide
that you're going to migrate that plugin class into the app itself
(since you've decided that it is so wonderful that should be part of
the app itself instead of a plugin).
Personally, rather than keeping track of a class list as things are
loaded, I'd just walk the entire class lists as needed (which would
also help to mitigate against forgetting to add your magic
registration into +load).
Glenn Andreas email@hidden
<http://www.gandreas.com/> wicked fun!
quadrium2 | build, mutate, evolve, animate | images, textures,
fractals, art
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
