On Sep 16, 2009, at 01:27 , thron7 wrote:

>> OK, I managed to make the default app working as I wanted : source in
>> the web server all in my favorite IDE.
>
> That's good to hear :-). Which IDE are you using?

IntelliJ

>
>> While documented in the URL provided by Thon7, this is really
>> disturbing and counter intuitive since it will change all URL at  
>> runtime
>> (http://localhost:8080/myapp/source instead of usual
>> http://localhost:8080/myapp)
>
> This shouldn't be too much of a worry in a development environment.

Even in dev, I don't like such artificial differences.
Why should we access the application with different URL ? In fact,  
there is no valuable reason.
This is just because of the tool. So we report tool constraint on dev  
users.
That's not a blocker, but here is a scenario where it could be at  
least annoying :

What about end to end test (Selenium) ?
You first run it against build target. If it fails, you want to know  
more and you would like to run it against source so you'll have the  
debug message that time.
Unfortunatly, you'll have to take care of that URL difference.

That is just an example, but the argument is that there are no reasons  
to see the same URL from build and source for the same application.

> What is another element in the path?!

well ... the word source.
The URL to call the application after generate.py source is 
http://localhost:8080/myapp/source
The URL to call the application after generate.py build is 
http://localhost:8080/myapp

>
>> Maybe this could be improved by letting, optionally, the possibility
>> to set the QOOXDOO_PATH under the webserver, so this can be different
>> at build-time and run-time.
>
> See my answer to your previous mail, this might do the trick.

Yes, I'll have a deep look because I think this is the solution for my  
"shared code between applications" issue.

>
>> Anyway, its working both source and build using Tomcat on a powerful
>> IDE, so, I'll start migrating our code to 0.8.3 and to python build.
>> Still have to test RPC in that context, but it should be OK.
>
> Good stand!
>
> T.

Again, thanks for your help !
JBB.

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to