On 12/04/12 23:56, Peter Bittner wrote:
> Phil,
>
>
>> Yes, you're right but the point is the public/images/ directory and its
>> contents get copied by pyjsbuild to output/images/, so if you place
>> alternative images in public/images/ and rebuild the pyjs version, the
>> images will be available to both pyjd and pyjs.
>> Hope this clarifies the point.
>>
> Not completely, why would you want to do that? What does "alternative
> images in public/images/" mean? (Not getting that, sorry.)
>
> The output folder is, if you want so, a deployment area or a build
> area. Everything there is supposed to be generated. And, as such, it
> must be taken from elsewhere -- clearly, outside of ./output.
>
> Peter
>
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. 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. When you did a pyjsbuild, the would automatically get
copied to yourappdir/output/images and pyjs would access them from there.
Not sure how I can make it any clearer than that.
Regards,
Phil
