Jean-Noël Rivasseau wrote: > Forgot to add the exact error message: it's just that FF won't load > any images / resources because it cannot load something with an URL of > http%3A.
Wrong, it can. But it appears that the second slash is missing, after both "http:" and "http%3A", which is the real issue. And resource uri's are not constructed correctly with the absolute URL. Please open a bug for this, have to investigate this. T. > > On Thu, Apr 23, 2009 at 6:44 PM, Jean-Noël Rivasseau > <[email protected] <mailto:[email protected]>> wrote: > > Hi, well I am pretty sure this is a bug because there is no need > at all to url encode this thing where you do it. I am using > Firefox 3.0.8, qooxdoo 0.8.2, Linux. (My colleague had the same > problem under OS X - and Safari). > > Note that only some of the uri have this problems in the loader > file: specifically: > > var libinfo = {"qx": {"resourceUri": > > have messed up uris > > whereas > > qx.$$loader = { > parts : {"boot":[0]}, > uris : > > have the correct uris. So it's not even consistent. > > Jean-Noel > > > On Thu, Apr 23, 2009 at 6:33 PM, thron7 > <[email protected] > <mailto:[email protected]>> wrote: > > Hi Jean-Noel, > > > > > > "uri": "http://static.mydomain.net/qooxdoo/"; > > > > for a library entry, > > > > when I run generate.py the generated loader script as some > problems as > > the uri is translated to http%3A which breaks everything. > > Now, now ... it doesn't break "everything", url encoding is > usually a > good thing, and understood by most browsers. It would be most > helpful if > you could report (a) what you are using (qooxdoo version, > browser and > browser version, os), and (b) what exact error message you are > getting. > > > The fix is probably very easy but this is a pain currently > as i have > > to sed the loader everytime to get it back correctly. > > > > Can I report this problem in your bug tracker? Is there a > current > > workaround? > > There is a bug about problems with url encoded file uris in IE > (http://bugzilla.qooxdoo.org/show_bug.cgi?id=2082). If this is > the same > problem, add your report as a comment, but please provide all > necessary > information about your environment. If in doubt, open an new > bug for it, > and we'll join them if appropriate. > > As for the work-around, I know of nothing generic. But you > could put the > call to sed in your config.json in a "shell" key, and have it > run after > every compile so you don't need to do it by hand. That should > relief the > pain. Put it in its own job, and add a "run" job running the > default > source/build first, then your shell job, like this: > > "my-source" : { "run" : ["source", "my-sed-job"] } > > and > > "my-sed-job" : { "shell" : "sed ...<options here> > source/script/myapp.js"} > > Then invoke "generate.py my-source". > > T. > > > > > Thanks > > > > Jean-Noel > > > > ------------------------------------------------------------------------ > > > > > > ------------------------------------------------------------------------------ > > Stay on top of everything new and different, both inside and > > around Java (TM) technology - register by April 22, and save > > $200 on the JavaOne (SM) conference, June 2-5, 2009, San > Francisco. > > 300 plus technical and hands-on sessions. Register today. > > Use priority code J9JMT32. http://p.sf.net/sfu/p > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > qooxdoo-devel mailing list > > [email protected] > <mailto:[email protected]> > > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > > > ------------------------------------------------------------------------------ > Stay on top of everything new and different, both inside and > around Java (TM) technology - register by April 22, and save > $200 on the JavaOne (SM) conference, June 2-5, 2009, San > Francisco. > 300 plus technical and hands-on sessions. Register today. > Use priority code J9JMT32. http://p.sf.net/sfu/p > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Stay on top of everything new and different, both inside and > around Java (TM) technology - register by April 22, and save > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. > 300 plus technical and hands-on sessions. Register today. > Use priority code J9JMT32. http://p.sf.net/sfu/p > ------------------------------------------------------------------------ > > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
