Alex,
It worked! In fact, I simply copied the sample config.json file included in
the article, modified it to use my application's filenames, and voila!
One question (which I suppose is actually a couple): will I still be able to
access all of the qooxdoo javascript variables from within the main HTML
file? So that, say, if I have two Inline components running in different
places on the same HTML file, I'll be able to allow one to access the
variables of the other. For my own purposes I have a situation where I need
the Inline components to talk among each other, but they really won't work
as one monolithic application. And if they can in fact see each other's
variables (where in practice they become variables floating in the main
HTML(?)), can I/we be sure that any default variables generated by qooxdoo
will not overlap and cause unpredictable or fault-causing behavior?
In the article, you might want to mention that the "root" field should
include the path to the *directory *of the user's HTML file, not to the HTML
file itself. For example, on my first attempt I put "C:/website/site.html"
and it failed; it needs to be just "C:/website".
Many thanks,
Joseph
On Wed, Oct 22, 2008 at 4:34 AM, Alexander Back <[EMAIL PROTECTED]>wrote:
> Hi Joseph, hi Chris,
>
> I guess Joseph you are talking about setting a different
> application-root (the relative path in which your index.html resides
> based on the path of the "config.json") for your application. This is
> only needed for the source version of your application.
> It seems a bit like telepathy, because I've just re-activated our
> "snippets" section by adding a short article about "Setting a different
> application-root" ;-)
>
> So, please check out this article located at
>
>
> http://qooxdoo.org/documentation/0.8/snippets/different_application_root
>
> and tell me if the article fits for you. Comments welcome!
>
> cheers,
> Alex
>
>
> Chris Banford wrote:
> > Hi Joseph,
> >
> > Good question for so early in the morning! :-)
> >
> > I'm also curious as to how this might work, as I need to do the same
> > thing (and I would imagine most people trying to use qx inline will
> > also). I hadn't tried it yet, but had just assumed that one could simply
> > adjust the path to the loader .js file in the target html page and
> > things would be happy, regardless of where the html file was located.
> > Doesn't appear to be the case...
> >
> > Cheers,
> > -Chris
> >
> >
> >> I am building my website to include some qooxdoo Inline components,
> >> and I have encountered a hurdle getting them to render (or, for the
> >> generate.py script to do what I need it to do) in my html file. I have
> >> a separate html file for my website which is NOT the same as the
> >> default index.html created by generate.py and lives one directory
> >> higher than the qooxdoo application folder. That is, for example:
> >>
> >> website is at C:/website/site.html
> >>
> >> qooxdoo Inline component at C:/website/qooxdoo/... (contains the
> >> index.html, which I don't intend to use, and all of the class, script,
> >> and resource folders).
> >>
> >> I want to include the qooxdoo application in a script tag in site.html
> >> (in a div element, to be specific), but generator.py of course builds
> >> the entire application relative to the file structure one directory
> >> lower at /website/qooxdoo. I want to do this, rather than use the
> >> default index.html generated by qooxdoo, because I expect to use
> >> multiple qooxdoo elements separately around my website, and therefore
> >> no single index.html will apply. From the online documentation I
> >> suspect I will need to edit the config.json file, but exactly what I
> >> need to edit is unclear. Some tentative test edits I made (in
> >> particular, trying to code absolute file paths into config.json rather
> >> than the relative paths that generate.py generates) didn't work. If
> >> there is already an online discussion on this topic that I have missed
> >> I would be very happy to be directed to it.
> >>
> >> Best regards and thanks,
> >>
> >> Joseph Gangestad
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel