On Apr 14, 7:29 pm, "Richard Jones" <[EMAIL PROTECTED]> wrote: > > It obviously would not be difficult to os.walk over a directory and > > add everything to the path for resource to index, but I think that's > > kind of working around the real issue. > > It's also the wrong approach, IMO. If you want everything in the same > namespace, move the files around.
I don't necessarily want everything in the same namespace, but that's just the way pyglet.resource currently works. To answer the caller from "find is your friend", I don't particularly want to fight with my artist over *namespacing*. He's been very kind to volunteer his time. I'd much rather fight with him over things like visual style. :) Right now, I've whipped together a static indexer that whips up a text file with paths that I can feed into the loader at runtime. That is to say, I'm using os.walk. Sure, this isn't the Right Way, but it sure does work. > > Which is that we want to be able to have some resources indexed by a > > partial path + name. Say, 'tiles/water.png' should be a separately > > indexed resource to 'animations/water.png'. > > I'm +1 on this. This seems like a more pythonic route for the module to take. I've been looking at the Loader implementation. Changing the index handle shouldn't be hard at all. I still dream of recursive indexing, but I haven't quite figured out how the current reindex method could be bent toward that end. --David Eyk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
