On Tue, Feb 3, 2009 at 6:31 PM, Lucio Torre <[email protected]> wrote: > On Tue, Feb 3, 2009 at 6:25 PM, Anthony Lenton <[email protected]> > wrote: >> On Tue, Feb 3, 2009 at 5:27 PM, Lucio Torre <[email protected]> wrote: >>> Why not? cocos comes with some graphic files that are needed for some >>> of the modules to work. >>> How can we do this if we dont put that package path into the resource path? >> >> The problem isn't only adding the package path to resource path, but >> also that later the standard way to create an image is by doing >> >> myImage = pyglet.resource.image(...) >> >> we can change all of those calls for calls to >> >> myImage = pyglet.image.load(...) >> >> but we'd be losing the automatic caching, atlas tiling, flipping and >> rotation that the resource module provides. > > I didnt understand. > > arent we suing resource.image? if no, why not?
At the moment we're using resource.image. > why would we want to move to image.load? I was answering your question: "How can we do this (loading the images that come with Cocos) if we dont put that package path into the resource path?" We could do that by replacing all calls to pyglet.resource.image() by calls to pyglet.image.load(). (I don't think it's a good idea to do the switch.) > maybe we need the pyglet fix before we can do that? > I'm not sure I understand any more. Which fix before doing what? -- Anthony Lenton --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cocos2d discuss" 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/cocos-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
