#APTANA STUDIO JAVASCRIPT HOW TO#

(Who Eclipse has managed to f*k up this?) Turn on: Settings -> Aptana Studio -> Javascript -> Tab policy -> Use spaces to make your source code to be friendly with all the other text editors in the world who use tab size 8. Using sane tab setting and fixing mixed spaces and tabs You probably don’t want to see red marker all over you code, so you might want to tune down warnings a bit.Īdd these to Settings -> Aptana Studio -> Validation -> Javascript -> Ignore.ĭon’t complain about missing jQuery or Console. JSLint is very accurate with every detail – like a Finnish-Swedish lady when it comes to cleaning your apartment. Note that not having wrapping spaces is important here. You can also use JSLint global hints per source file to hint what globals the file has available, so JSLint won’t complain.įor example, to hint that global krusovice namespace is available, add the following line to the beginning of the file: /*global krusovice*/ The Problems view can be found Show -> View -> Problems. There is also Problems view which shows all the errors and warnings in your workspace. Now you can see how bad your Javascript code is (bottom window):Įrrors and warnings are highlighted in the Javascript editor left marginal when you type. Your Javascript code will run on Firefox, but that alone doesn’t make many web developers happy 🙁įirst you need to enable JSList validator in Settings -> Aptana Studio -> Validation -> Javascript. For example, JSLint will caught extra commas in your JS files which would choke on Internet Explorer, but run on other browsers.Īptana Studio Javascript has ability to scan your Javascript while typing and highlight the errors.īy default Aptana Studio uses a validator called Mozilla validator which is very lax.

#APTANA STUDIO JAVASCRIPT HOW TO#

This post tells you how to use JSLint with Eclipse, or more precisisely Aptana Studio. It saves your ass from common Javascript pitfalls.

Aptana studio javascript