Hi guys,
Marcus Lindblom wrote:
> That is what I was thinking as well. I was rather wondering if Dirk
> wanted something like what you "accused" me of. :)
>
Not really. I was more thinking about how to handle loaders that we
don't have the code for (or don't want to change the code). Those are
the problem, as we can fix all our own ones to whatever we want.
> Imageloaders do use iostreams now, AFAIK. At least that's what I'm
> feeding to ImageFileHandler. :)
>
Yeah, most of the existing code has been moved to iostreams. There is
still a filename interface for backwards compatibility, though.
> Yes. I posted about this a while ago, as I have some code for this. I
> use it also to cache what comes out post-graphop
> (strippings/transforms/sharing) to speed up subsequent loads.
>
I've been thinking about this idea before and it might make sense, but
honestly I'd think this is a separate issue (which some relation in the
code, but not necessarily the same thing). I'd like to figure out the IO
abstraction first and add caching later.
> Yes. The cache should of course be configurable, with very strict
> settings as default (it could only save files if required by the loader,
> and delete them on exit).
>
What's the benefit of removing the files after exit? Do you have files
that are loaded more than once?
> True. But all that is abstracted away from the user. SceneFileHandler
> need not change.
>
That's the goal.
Dirk
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
