On Wed, Apr 25, 2012 at 4:42 PM, Phil Charlesworth <[email protected]> wrote:
> 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. ... actually... that could be arranged to not be the case. the reason is because it's possible to write a custom importer that loads python files from absolutely anywhere. the .egg and .zip importers for example are actually written as python code that hooks into __import__ i did seriously consider implementing an http:// importer that would look for the source code off the server. it would however mean writing a /usr/bin/pyjd.py which would be given one argument - the http loader file. oh, and maybe the width and height parameter as well. > If that's the case, why would it > not be able to access the images in pyjamas/library/pyjamas/ui/public/ ? because they're not there: he's done a system-wide install. everything's in /usr/share/pyjamas. which is probably what the problem is: ui/public probably hasn't been copied over (because it has to be explicitly added to run_bootstrap_first_then_setup.py as a data directory to be copied) let's check: lkcl@teenymac:~/pyjamas$ ls /usr/local/share/pyjamas/library/pyjamas/ui/public/ disclosurePanelClosed.png gchart.gif tree_closed.gif disclosurePanelClosed_rtl.png history.html tree_open.gif disclosurePanelOpen.png __init__.py tree_white.gif lkcl@teenymac:~/pyjamas$ err, no - they're there all right.
