Re: [qooxdoo-devel] Qooxdoo and XHTML documents

[Alessandro S. <ale...@mc...>]

Hello Sebastian,

> I don't like both things. We cannot use server side processing in this 
> case. And I also don't like that one needs to process the files first. 
> I really like the current file header, which doesn't differ between 
> the "source" and the "build" version.
>
> If you have already used XmlHttp to load the files, why not use 
> window.eval to evaluate the code afterwards. Is there any reason why 
> we need to write script tags at all?
>
Yes, I think there is a reason: as I stated before, using XmlHttpRequest 
to load classes and inserting them into the document (be it by 
window.eval() or by any other technique such as embedded <script> tags, 
as I first did) certainly works, but will result in losing references to 
the original source files.

I understood that the source build should ease the debugging of the 
application during development by allowing the browser to report 
javascript errors along with a meaningful source file name and line 
number; in addition tools like Firebug can be used to inspect the code 
and set breakpoints looking at the original sources: all this is lost if 
we don't use <script src=...> tags to load the sources.

This is why I struggled to keep script tags and used XmlHttp only as a 
workaround for IE.

Anyway if I'm wrong, or if you think that the above reasons are not 
worth the effort of using script tags, I'll [not so much :-( ] happily 
remove them and only use XmlHttpRequest!

Let me know.

Ciao,
Alessandro