The unification makes sense. But how would intentional overriding (as is
usual for messages) versus unintentional collisions be handled? Conventions
or some kind of extra scoping?
Cheers,
Nick.
Howard Lewis Ship wrote:
I don't see this as a problem, message catalog and symbols are very closely
I don't see this as a problem, message catalog and symbols are very closely
tied together.
An interesting possibility would be for each component to have its own
symbol source, derived from a related file, that tied into the global
SymbolSource ... but that looks *exactly* (well almost, leave out
I know from a "user" perspective I'd like to have things be able to
default all the way out to symbol / global properties file definitions
when developing libraries and such if possible
There may be some performance or other internal framework decisions /
reasoning behind it but I started to s
So right now I have a situation where I need my library to provided some
default values for some things it provides. The natural place for this
seems to be FactoryDefaults. The problem is that certain things are only
looked up in the component messages when determining defaults and it
doesn't appea
