What I did was to use Traits to define the different systems for the
different applications, using them as modules.
However I was not very comfortable with Traits (it was the
first generation of Traits), so I started "prototyping" a Descriptor
system that didn't rely on the selectors to resolve class models,
descriptors, and tables, and instead was more declarative (and
delegated to the classes as a last resort to "install" themselves into
a Descriptor System), but that got abandoned and now I have no reason
to build it that way (although I'd like to have it that way).
So... answering your question, you subclass DescriptorSystem to
resolve things the way you prefer, or you also subclass
DescriptorSystem and install different traits for the different
applications you have.
There is a cost in the setup of a DescriptorSystem if it contains a
lot of models and descriptors, because it validates them when starting
them up, that was something I also did optimize back then, having a
"lazy validation" for regular use, and a full validation to work only
as a "type checking mechanism".
Esteban A. Maringolo
> You received this message because you are subscribed to the Google Groups "glorp-group" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to glorp-group...@googlegroups.com
> To view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/7ac3f962-6327-4de1-930b-cf06765f4a28n%40googlegroups.com