I think that would depend on how the add ons were implemented.
If the registry file just made farcry aware of them and allowed it to load them into the application scope it might serve a useful purpose for some.
I agree that the registry would be mighty useful for project based extensions of core components.
I was trying to make the distinction between 'add-ons' and the registry. If somebody wants to install my 'add-on' into their install and I've overridden a core component which they have also overridden then who is to decide what component should be instantiated?
It's the same idea as delegation vs notification. You can only delegate a single replacement of the one class, but if there was a notification (callback) mechanism that addons could register for then it would allow multiple add-ons to work side-by-side.
I'm not saying that I need a plugin architecture such as this (as I don't!), I was just pointing out that it may not be so simple to use the registry for 'add-ons' (where people would most likely want to install multiple add-ons from, say, the community dev site)
/me *snips the rest* -- time for bed
-- 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/
