hi all,
i'm trying to instance and manage the life-cycle of avalon components specified by the user of an application i'm currently writing. what container should i use? i think containers that require an XML configuration file would not fit because the components to use are determined at runtime.
as you may have guessed, i'm new to avalon. please help!
btw, this is the app: http://xfp.sourceforge.net
The link is temporarily down, so let me ask a couple questions to help me understand what you are doing.
1) Is XFP an application framework where users extend the basic one and add their components later?
2) Exactly how does XFP allow users to specify their own components?
There are a number of ways to incorporate configuration information, and it doesn't always have to be done by XML, although that's what most do. In just about all the Avalon containers, if there is no explicit custom configuration information, the container will pass in an empty configuration element. Most components know how to handle that, and they operate with the default settings for the configurable components.
You might want to provide a way to let the components be configured, but to give you ideas I need the answers to the above two questions.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
