On Sun, Jan 29, 2012 at 2:39 PM, Apexi 200sx <[email protected]> wrote:
> On Sun, Jan 29, 2012 at 8:33 PM, C Anthony Risinger <[email protected]> wrote:
>> On Sun, Jan 29, 2012 at 1:54 PM, Apexi 200sx <[email protected]>
>> wrote:
>>>
>>> Any chance the root cause of the path issues could be fixed tho :)
>>
>> looks like a windows specific bug, probably due to `os.path.join()`.
>> can you confirm the cache files originally said:
>>
>> /lib\pyjamas.ui.js
>>
>> ... and not:
>>
>> /libpyjamas.ui.js
>
> Hi, they were originally as follows...
>
> $wnd.__pygwt_modController.load($pyjs.appname, [
> 'lib\pyjamas.ui.Panel.js',
> 'lib\pyjamas.ui.HTML.js',
> 'lib\pyjamas.Window.__oldmoz__.js',
> 'lib\pygwt.__oldmoz__.js',
> 'lib\pyjamas.Factory.js',
> 'lib\pyjamas.ui.js',
> 'lib\pyjamas.ui.InnerHTML.js',
i haven't fixed this yet, but for now i'll just use a lame workaround like:
.replace('\\','/')
... the real solution involves work maintaining proper lookups of
target/src filenames/etc. also, apparently Windows has supported unix
pathnames since DOS (!) 2:
http://en.wikipedia.org/wiki/Path_%28computing%29#MS-DOS.2FMicrosoft_Windows_style
... and omitting the drive letter means "current drive". since we do
not AFAICT use the shell for subprocesses, it should be safe to import
`posixpath` instead of os.path.
--
C Anthony
