Having now looked at the web page describing JSLint, I see that my comments (below) 3) and 4) are not entirely valid. Anyone intending to use the widget, needs to read the page describing the (stricter) syntax rules that JSLint enforces.

However, I find that JSLint imposes constraints on my style which I am not prepared to accept, however well-intended they may be.

I tried this on a 160 line "valid" javascript file and came up with a number of issues, which mean that I would not currently be able to use this widget for checking the javascript code of my widgets.

1) Giving the character position of an error is pretty useless - I need the line number, a print-out of the line, and ideally an indication of the location of the error in the line.

2) It would be useful if the widget found more than one error at a time. I know that is difficult, but it… is possible.

3) The option to allow ++ and -- does not work.

4) // comments appear not to be allowed.

5) The widget insists on { } after if (condition), which is too strict.

This could be a very useful widget, but, at present, I would rather use my Widget Tester widget for syntax checking. More