Re: [atf-dev] javascript validator slowness

[David M Williams <david_williams@xxxxxxxxxx>]

Seems to me the .cvsignore file is useful
only because CVS (an external system) uses it already. That's not the case
here, right? 

I'd think some more direct way of controlling
validation preferences (via normal validation framework) would be more
Eclipse-integrated. 

BTW, I agree with the incremental validation
statement, and will also point out that validators should be easily cancelable.

For example, if this problem is with
"as you type" validation, you'll want to be sure any current
validation cycles are canceled once a new keystroke comes in.

"Gino Bustelo" <lbustelo@xxxxxxxxx>
Sent by: atf-dev-bounces@xxxxxxxxxxx

10/23/2006 11:03 AM

Please respond to
AJAX Toolkit Framework discussion <atf-dev@xxxxxxxxxxx>

To	pombredanne@xxxxxxxxx, "AJAX Toolkit Framework discussion" <atf-dev@xxxxxxxxxxx>
cc
Subject	Re: [atf-dev] _javascript_ validator slowness

One idea that we are thinking of implementing is something
analogous to the .cvsignore file. We would call it .jsvalidateignore or
something like that. The concept is that we will have the JS validator
look at for this file in every folder and determine what should be validated.
A good use for this is to be able to ignore the entire set of _javascript_
files of an Ajax runtime/framework. A user of Dojo does not really care
about errors inside Dojo because he either does not know how to fix them
or is really out of his control. 

Thanks, 

Gino Bustelo
ATF Developer

On 10/22/06, Philippe Ombredanne <pombredanne@xxxxxxxxx
> wrote:
John
You wrote:
>I have a _javascript_ file that the validator does not like. To 
>spite me it makes editing excruciatingly slow.  Is there a way
to
>tell it to stop, give up, you will not be able to validate this file?
IMHO WTP validation is subpar speed wise in general.
And ATF uses the WTP validation framework. :-\ 

Yet you can disable it either globally in the prefs, or for a project in
the project properties.
You can also always "kill" a currently running validation in
the
progress view.
I typically use the global validation prefs such that it is set to be 
only manual  (ie not triggered by a build) and invoke it manually
now
and then.
I did also define a keybing of rth validate command in the prefs
(Uncategorized ?validate ) to make that process less of a PITA. 

If you have some ideas to make it work better and faster in general that
would be nice.
May be something like incremental validation would help quite a bit!
Cordially

--
Cheers
Philippe

philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com
nexB - Open by Design (tm) - http://www.nexb.com
http://easyeclipse.org
  -  irc://irc.freenode.net/easyeclipse


_______________________________________________
atf-dev mailing list
atf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/atf-dev
_______________________________________________
atf-dev mailing list
atf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/atf-dev