On 25/04/12 08:23, Vsevolod Fedorov wrote: > On 04/24/12 20:19, Phil Charlesworth wrote: >> Not sure I understand your problem. As a test I am running the >> KitchenSink example under pyjd on Windows 7. The URL for pyjd.setup is >> 'http://localhost/examples/kitchensink/public/KitchenSink.html', so the >> html file is being served by the local server. > Yes >> When I click on the Trees page link, pygwt.getImageBaseURL() gets called >> with no arguments and is returning >> 'C:\pyjamas/library/pyjamas/ui/public/', which is where the images for >> the Tree widget are by default. I have NOT copied the images to the >> .../kitchensink/public/ directory. > You see, this path is not 'http://localhost/...', this is file system > path. Which is absolutely wrong. But it IS the path to where the files are and the code works. > > Well, I made a small sample to show the problem, attached it as > zip-archive. > To reproduce problem, I first start ./server.py (or "python > server.py"), then run ".../pyjamas/bin/pyjd index.py". > Then I get the following log: > ------- > $ ./server.py > localhost - - [25/Apr/2012 11:10:26] "GET /public/index.html HTTP/1.1" > 200 - > localhost - - [25/Apr/2012 11:10:26] code 404, message File not found > localhost - - [25/Apr/2012 11:10:26] "GET > /home/seva/pyjamas/library/pyjamas/ui/public/tree_white.gif HTTP/1.1" > 404 - > localhost - - [25/Apr/2012 11:10:26] code 404, message File not found > localhost - - [25/Apr/2012 11:10:26] "GET > /home/seva/pyjamas/library/pyjamas/ui/public/tree_closed.gif HTTP/1.1" > 404 - > ------ > > Seva > > Seva, I feel that there must be something radically different about your setup. My understanding of pyjd is that it HAS to have access to the file system to find the pyjamas code. If that's the case, why would it not be able to access the images in pyjamas/library/pyjamas/ui/public/ ?
My applications depend on lots of JSONRPC which all works fine. The application code is under the webroot of the server (which is necessary for JSONRPC to work) but the pyjamas code is outside the webroot and cannot possibly be accessed by an HTTP GET. How is that your code is using an HTTP GET to access these files? Phil
