Stefan,

I cannot comment on specific CMSs, like Drupal, but there is no general problem with deploying qooxdoo applications in such an environment.

In general, you would develop your qooxdoo application in the "source" version, and once you are content with it, create a "build" version and copy that over to your CMS. The build version (usually created in the "build" subfolder of your application) is self-contained, you don't have to worry about framework classes, everything needed is within this folder tree.

If the URI from the index page to the qooxdoo application resources is different, you can configure that in the config.json of your application. The same applies for the "script" folder. So in the "jobs" section of config.json, add this job entry:

   "build-script" :{
     "compile-options": {
       "uris" : {
         "script"   : "<uri_to_script_folder>"
         "resource" : "<uri_to_resource_folder>"
       }
     }
   }

See [1] for details.

The generated build version of your application is a coherent mix of all classes necessary for it, be they from the framework, your custom code, or any additional qooxdoo library/contribution you may be using (think of a statically linked executable of a C app). So there is not much sense in splitting it up in library parts and custom parts.


T.

[1] http://qooxdoo.org/documentation/1.0/tool/generator_config_ref#compile-options



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.

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.

I would appreciate advice of best solution in this area.
------------------------------------------------------------------------
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>
------------------------------------------------------------------------

------------------------------------------------------------------------------
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
------------------------------------------------------------------------------
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

Reply via email to