Thanks for the solution. It works now.
Why is it better?
Well, there might be many answers to that question. I think some people would
appreciate the following:
1. shorter loading time with big projects, especially if you have many
2. shorter loading time if you have more than one project embedded in the same
html page.
3. more structure.
4. and maybe the most important one; the CMS does not need to store more than
the custom code in the database and the qooxdoo base will be a folder on the
disk.
There might be some other reasons too.
Don't you think the above reasons are strong enough to motivate a structure of
base + custom?
Date: Thu, 14 Jan 2010 06:31:49 -0800
From: [email protected]
To: [email protected]
Subject: Re: [qooxdoo-devel] How to integrate qooxdoo with a CMS for example
Drupal or OpenCMS? Still no answer....
Hi Stefan,
On Thursday January 14 2010 12:16:44 Stefan A wrote:
> I have two question to get some advice regarding qooxdoo integration:
>
> 1. How can I change the path to resources when I have put qooxdoo in web
> container such as JBOSS? How does it change if the resource folder is not a
> subfolder to the index.html file loading and activating qooxdoo? THis can
> happen if you use a database oriented CMS, where the custom qooxdoo
> application (with or without the qooxdoo library) is saved within the
> database and is connected to an for example an article of a webpage as
> embedded. Give me some advice for example how to integrate qooxdoo in
> Drupal.
You can take a look at the "compile-options" job documented at
http://qooxdoo.org/documentation/1.0/tool/generator_config_ref#compile-options
At the "uris" block you can provide an alternative URI to the resources which
qooxdoo should use. You have to write your own job/extend existing ones to
achieve this. You can extend the "source-script" and "build-script" jobs
which are defined by the framework and which need to be changed to use your
settings.
> 2. How is it supposed to be with a custom qooxdoo application and the
> qooxdoo library? How is it possible to compile the two in separate modules;
> one base module (the qooxdoo library) and one application module (the
> custom code)? This is better when you again deal with integration of
> qooxdoo in a java CMS.
Why is it better? Normally a build qooxdoo application is compiled into one
javascript file containing every necessary class and a loader logic to start
the application. Why do you need two separate files? Is it really better here?
cheers,
Alex
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
View message @
http://n2.nabble.com/How-to-integrate-qooxdoo-with-a-CMS-for-example-Drupal-or-OpenCMS-Still-no-answer-tp4391938p4392788.html
To unsubscribe from How to integrate qooxdoo with a CMS for example Drupal or
OpenCMS? Still no answer...., click here.
_________________________________________________________________
Windows Live: Make it easier for your friends to see what you’re up to on
Facebook.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_2:092009
--
View this message in context:
http://n2.nabble.com/How-to-integrate-qooxdoo-with-a-CMS-for-example-Drupal-or-OpenCMS-Still-no-answer-tp4391938p4397359.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
