From: Dirk R. <di...@in...> - 2006-08-25 03:00:01
|
Hi Jan, On Fri, 2006-08-25 at 02:54 +0200, jan p. springer wrote: > > or make (what we call) packs. for things conceptually belonging together we > create packs that exhibit an abstract type whose only purpose it is at > registration time to register all types in the pack. if you couple that with > the idea of having .txt files along with the .so (just like bamboo did) > describing dependencies or content or whatever that should be flexible enough. So the system reads the info for all available packs and therefore knows which classes come from which packs, or does the user have to explicitly say which packs to load? I would like to get to the point where we can have arbitrary FCs embedded in an OSB (easy), but have the system load the necessary .sos automatically whenever that OSB is loaded. But for that the FCFactory has to be able to figure out which so to load find it. I would like to avoid having to all possible sos just to collect the info, as that will be a big burden on startup... Dirk |