Michael Cortez wrote:
Can we not have the ObjectManager be something that libsecondlife automatically starts up?
Yes, this is coming soon. The major subsystems are divided up in to only a few different categories so likely they will all be turned off, and applications flip them on as they are needed, before login. The main hurdle is going through all of the code and identifying where one subsystem relies on another, and either removing the dependency somehow, or making note that one is required or at least one is required for another to function.
Just imagine what it would be like if the InventoryManager was on by default, and was downloading your inventory on each login? Eeeeek :)
Probably a bad idea to have libsecondlife automatically initiate downloads, that should be a function or setting that clients have the capability of setting themselves.
BTW would you be interested in me working with the TextureEntry class, so that'll automatically download and cache textures that are encountered?
Lets hold off for now, as the caching system is a big deal that needs to be hashed out on paper first. Aside from caching, I think a good approach might be flipping a bit somewhere that says "download all textures you see" and any callback that may come across texture data can call a master download function that will later be responsible for cache lookups and initializing downloads.
John _______________________________________________ libsecondlife-dev mailing list libsecondlife-dev@gna.org https://mail.gna.org/listinfo/libsecondlife-dev http://www.libsecondlife.org/
