On Fri, Apr 13, 2012 at 11:48 AM, Phil Charlesworth <[email protected]> wrote:
> Peter, > As explained in the issue comments, the DisclosurePanel and Tree > widgets use images which are located in library/pyjamas/ui/public. When > you pyjsbuild an app (in a directory yourappdir) using those widgets, > the images are copied to yourappdir/output/ and that's where the widgets > then access the images. However, the images are not accessible to pyjd > unless you manually copy them to yourappdir/public/. I proposed a > mechanism which allowed pyjd to access the images direct from > library/pyjamas/ui/public/, while pyjs would still get them from > yourappdir/output/. > > Luke rightly pointed out that, if you wanted to use different images, > instead of the standard ones, you couldn't do that with my scheme. In > fact, as I pointed out, you can't do that with pyjs either. whatwhat? they can't? err... that's bad. if you drop images into public/ they should over-ride the ones that are in library/pyjamas/ui/public [in some fashion]. > However, I > proposed a further modification which would allow you to tell the > widgets to look for the images in an alternative location. You would > then put the images in yourappdir/public/images/ and pyd would access > them from there. okaay... that should be.... > When you did a pyjsbuild, the would automatically get > copied to yourappdir/output/images and pyjs would access them from there. that happens automatically already (i.e. the entire ./public/* structure gets copied to ./output/ or wherever the -o option specifies it) l.
