Thanks Sebastian.

I'm really trying to gauge to what extent Qooxdoo with be able to detect and
handle syntax error and runtime errors. It also seems that in the case of
runtime errors Qooxdoo does not catch every error to the log. Some of them
still show up in my JavaScript console instead of the Qooxdoo log.

So this kind of brings me back to something I was working on before. I have
also been working on some scripts to provide integration between the browser
and editor/IDE upon any sort of JavaScript error. Basically,
this allows you to use any web browser and any text editor or IDE to
develop with and get syntax checking and pleasant error feedback without
needing to switch back and forth manually. The catch is that the scripts are
currently Mac only atm as they use AppleScript. So if there are any Mac
users on the list and you're interested in this let me know. Thanks. I 'll
try not to bring it up again. ;-)

Phil

On 7/27/07, Philip Weaver <[EMAIL PROTECTED]> wrote:
>
> Yeah that was it - I was using an error it didn't catch. Sorry to trouble
> you - wokring better. Thanks for the cache location.
>
> On 7/27/07, Sebastian Werner <[EMAIL PROTECTED]> wrote:
> >
> >  Currently it does not find all types of syntax errors. There is no
> > built-in syntax validation yet. It is just a parser and tree generator. And
> > even if some parts may not work you might not get errors from the parser
> > yet. If you are interested in this please open a new bug report in our
> > bugzilla. Just to keep track of this.
> >
> > The cache folder is inside the frontend/framework named ".cache"
> > (starting with a dot)
> >
> > Sebastian
> >
> >
> > Am 27.07.2007 um 13:47 schrieb Philip Weaver:
> >
> > Thanks Sebastian.
> >
> > I am now seeing "make source" run quickly on subsequent runs. However, I
> > put a syntax error in in Application.js of the skeleton and "make
> > source" does not complain about any syntax error? Should the default
> > MakeFile and "make source" check the syntax and complain if any syntax
> > errors exist? Or do I need to pass any other parameters via the MakeFile or
> > calling generator.py directly? Is there also some way I can customize
> > error output so I can integrate with my IDE Xcode?
> >
> > Also, where does everything get cached to?
> >
> > Thanks very much,
> > Philip
> >
> >
> > On 7/27/07, Sebastian Werner <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi Philip,
> > >
> > > welcome to qooxdoo.
> > >
> > > "make source" is quite fast when working with the cache. You can use
> > > it also to validate your files - this is correct. Only the first
> > > execution is a bit slower because it needs to parse and cache all
> > > files. After this it is OK to just check the modified files as the
> > > system does. So when "make source" ends really fast because most of
> > > the files are not modified and it runs through smothly this also
> > > means that the syntax of all files is OK. Does this answer your
> > > question
> > >
> > > Sebastian
> > >
> > >
> > >
> > > Am 27.07.2007 um 11:07 schrieb Philip Weaver:
> > >
> > > > I'm new to Qooxdoo. I understand that the make process of Qooxdoo
> > > > can be used to check the syntax of a project. But what is the most
> > > > efficient way to do this? When I run "make source" the script loads
> > > > 415 (qooxdoo) source files and takes forever "resolving
> > > > dependencies". What is the most efficient method to heck the syntax
> > > > of my project? Also, each time I add a new source file or class to
> > > > my project I have to run "make source" again and again? Is this
> > > > correct? I am trying to read the online docs...
> > > >
> > > > I do understand that I have an alternative of using JSEclipse or
> > > > Anatan with the Qooxdoo component but I prefer to use my
> > > > traditional text editor and use the supplied scripts to check
> > > > syntax as needed before each run.
> > > >
> > > > Thanks in advance,
> > > > Philip
> > > >
> > > ----------------------------------------------------------------------
> > > > ---
> > > > 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
> >
> >
> >
>
-------------------------------------------------------------------------
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

Reply via email to