Hello, Here is what you should do: 1) Install a tomcat server on the same machine you are developping your web application 2) Install the eclipse tomcat plugin (http://www.eclipsetotale.com/tomcatPlugin.html)
Here, you should be able to create a tomcat project from Eclipse, and to start/stop the server from Eclipse. The important thing to understand is that your context is linked to the eclipse project: you can work on your tomcat project and check the results with your web browser WITHOUT having to re-start or re-deploy your web application every time you are doing modifications. 3) Work with the qooxdoo 'source', not with the 'build'. You dont need to re-compile qooxdoo everytime you are doing changes !! The 'source' version of your application is a javascript script that will load all the classes involved in your project. This mean that you need to re-compile qooxdoo (make source) everytime you add a new class : and that's all ! To summarize: * Your firsrt 3 steps are not necessary : use tomcat eclipse and qooxdoo 'source' * Compared to the build version, your in-developpement application will load a little bit slower: that's because instead of getting one big file containing all the classes (with data compression) -- the 'build' --, your web browser will load each classes as individual files --the 'source' -- (it means that when using 300 classes, you will load 300 small javascript files instead of one big javascript file) : but, you can change sources and check up the results by reloading your web page. I am using tomcat and qooxdoo since more than 1 year, and I am happy with the cycle I did described. Please let me know if you need more details on that cycle. Hopes this will help you, Charles. 2007/11/4, Marcel Ruff <[EMAIL PROTECTED]>: > Hi, > > my round trip cycle during development is very uneffective. > (My qooxdoo app needs a servlet for communication to backend servers) > > 1. make build (40 sec) > 2. create a war > 3. deploy to tomcat (20 sec) > 4. reload in firefox (20 sec) > > So one single edit in Application.js takes several > minutes to verify. > > Is it possible to somehow have a symbolic link > from tomcat/webapps/myapp/.../Application.js to > my Application.js which i edit to ommit step 1.,2. and 3.? > > When i do a file:// load in firefox (for my app) i can't access > the servlet url from javascript (permission problem), > is there any workaround for this? > > > I'm using eclipse with Aptana and/or JSEclipse, > is there some other support for a more efficient development cycle? > > > Thanks for your thoughts, > Marcel > > -- > Marcel Ruff > http://www.xmlBlaster.org > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
