Hi, On Wed, 2007-12-12 at 16:50 +0100, Marcus Lindblom wrote: > Antonio Bleile wrote: > > Marcus Lindblom wrote: > > > >> In our system, we have every "object" that need extra updating being > >> registered to a "updater" when it's created. (By checking the type > >> dynamically.) The order of update is simply the order of creation, and > >> this has worked surprisingy well for almost three years now. The time > >> (both absolute and relative) is fetched from a singleton (that provides > >> different clocks for each aspect). > > > > Sounds good, the Observer pattern is always good ;) That would > > work well with a global "animation pool" (a pool that contains all > > the animation data of the scene). > > Ugh. I don't like global things. But it seems the only way to distribute > things in a cluster without having them shown (otherwise there wouldn't > be a MaterialPool), or?
not quite IIRC it was more to be able to store materials that are not referenced from withing the graph in a file (osb). If you want to for example store material variants with the model. The file part is the tricky bit as it usually works/sees on a (sub)tree. The cluster is much more straight forward as it does not rely on the graph. kind regards, gerrit ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Opensg-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-core
