Thomas, I finally found the time to file a bug (#4322) concerning urllib/2.
And thanks to your suggestions I could solve my problem of a contrib-enhanced program not showing up in the browser window. I found out that - at least under Windows - the cache/downloads directory for contributions has to be located on the same drive/partition as the application's source files. Otherwise the browser simply stops processing the generated application as soon as the first module of the contribution is supposed to be loaded. No error, no indication, no nothing - neither in Firefox nor in Firebug. I didn't dig very deep into this issue, but my impression is that the generator doesn't seem to find/include the contrib files if they are stored on another partition than the application itself. Do you want me to file a bug? Norbert thron7-2 wrote: > > Norbert, > > thanks for exploring this. Please go through the effort of creating a > bug and dump your findings into it, including the URL you mentioned and > the patch you applied to the generator. Maybe we switch to urllib2 in > general. > >> However, when I try to run such an application it does get loaded into >> the >> browser (according to Firebug) but nothing shows up, i. e. the browser >> window remains blank. If I remove all references to the contribution from >> config.json and the application itself everything is fine. (BTW: I've >> tested >> with the DarkTheme and the Dialog contributions using qx 1.0.1.) > > Check the downloaded contrib itself. You can find the path to your > downloads using 'generate.py info'. Is the directory structure ok? Can > you look at all the source files? > > If that looks good, decouple the contrib from the web by just pointing > the "manifest" entry to the local path on your disk (rather than using > the "contrib://" scheme). Now you are using the contrib like a local > library. Does that change something? > > Finally, what does Firebug say? A blank browser usually means some class > files cannot be loaded. You can try running your app through HTTP [1], > then failing requests are easier to see (in the Net tab). Which URL/path > is the browser failing to load? > > T. > > [1] > http://manual.qooxdoo.org/1.2.x/pages/snippets.html#running-a-source-version-from-a-web-server > > ------------------------------------------------------------------------------ > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > -- View this message in context: http://qooxdoo.678.n2.nabble.com/Generator-contributions-proxy-server-tp5724085p5743619.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
