might also be nice to have a standard way to install add-ons, etc.
Not sure that it would work because it would only allow a single add-on for a single component (unless you implemented some type of 'context' where the relevant component would be returned dependant on the context).
I think the component registry is a good idea but maybe not the best if you thinking of add-ons. I think any type of add-on functionality should be in the form of a plugin architecture where multiple plugins can take advantage of single extension points.
Wouldn't it be great to use cfcUnit to check that your extended component doesn't break the core. Would anybody like to volunteer 6 months of their life writing unit tests that cover all the core functionality? j/k =)
-- tim lucas
http://www.toolmantim.com
--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
