If a value is only used by one component, put the default in the
component spec.
If a value is shared across components, you could create an ASO with
global scope and inject it into your components -- or you could go
old-school, and just create a MyComponentSettings singleton and use it.
P
On May 15, 2006, at 3:04 PM, Dan Adams wrote:
I have a library of components that are used by a couple different
projects. One of the things I would like to do is to set system-wide
defaults for each project that would be used by the components so they
didn't have to be specified each time the component was used. I could
also create a wrapper component to set the properties but in this case
that is not optimal. Anyone know of a way other than setting system
properties that could do this? Something like setting it in a
properties
or config file somewhere.
--
Dan Adams
Software Engineer
Interactive Factory
617.235.5857
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
Piano music podcast: http://inthehands.com
Other interesting stuff: http://innig.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
