Turning off Eclipse 2020-06 Javascript Validation Notes - javascript

Using Eclipse's 2020-06 built in JavaScript editor, I need to disable the JavaScript informational notes on syntax and warnings as displayed with an (i) icon to the left of the line number and with markers to the right of the scroll bar. See links to the two images showing what these look like.
An example of the informational icon
An example of the markers
There are two warnings repeating numerous times:
'aVariableName' is declared but its value is never read.
This constructor function may be converted to a class declaration.
I would rather turn off these two individual messages since they do not apply to the project, but such control does not appear to exist, but they are overly spamming the editor and are interfering with other notifications and informational notes. FYI: I'm needing to follow specific coding conventions for the project and therefore the warnings don't even apply to the project and are just spam.
So I'll just settle for shutting off javascript validation, but the validation will not turn off.
I've tried to disable the project level settings for the javascript validation through the menu option Window, Preferences, Web, HTML Files, Client-side Javascript, Validator, Errors/Warnings: and unchecked both options of Strict Validation of Javascript keywords usage, and Enable JavaScript semantic validation. But making those changes accomplishes nothing since the warnings are still there even after running validation on the project, cleaning the project, and even restarting eclipse.
The specific version of Eclipse is:
Eclipse IDE for Enterprise Java Developers Version 2020-06 (4.16.0)
To try to better explain the need to install Node.js, this is the dialog requested Node.js be installed. The text of the dialog reads: "Missing node.js" "Could not find node.js. This will result in editors missing key features. Please make sure node.js is installed and that your PATH environment variable contains the location to the 'node' executable."
Eclipse's Missing Node.js dialog
Are there any other ways to shut off individual warnings/messages, or the javascript validations? Any help, or constructive suggestions would be very much appreciated. Thanks!
Sorry, the stackoverflow editor won't allow in-lining simple images.
Update: So I have not been able to figure out how to disable the informational notices that are showing up in the JavaScript editor along both the left and right margins. I would still love to find out how to do that. I'm wondering if the issues I'm seeing may have been resolved in the current release of Eclipse? I cannot put my development environments at risk if downgrading is not possible. But some hopeful and important details that I have learned is that the latest release of Eclipse "can" support java 1.8 although it says the minimal version supported is Java 11. And also the latest release is better integrated with Node.js so an external install is no longer required. At this time I cannot risk testing the latest Eclipse release due to possible lockout of the workspaces if eclipse cannot be downgraded. I will make plans to rebuild some of the workspaces on another workstation so it will not impact vital projects if something should go wrong.

I was able to disable these javascript validation notes by changing the following setting.
Eclipse -> Window -> Preferences -> General -> Editors ->Text Editors -> Annotations
find "Infos" in the "Annotation types" and click it
uncheck both the "Vertical Ruler" and "Overview Ruler"
optional - uncheck "Text as "Squiggly Line"
Click Apply and Close
Voila enjoy the less cluttered javascript files

Related

Use Quorum Plugin on another IDE; Sonic Pi; MIDI; javascript

I wrote a program that plays a song using sonic pi. I have to transcribe the code to a web language (javascript). Since I'm new at javascript I thought it would be ideal to use QUORUM (http://quorumlanguage.com/) to transcribe it since there is easy access to MIDI libraries, etc. (that I absolutely need). I have a mac and tried to use netbeans, etc (all processes suggested on the quorum site) but they are not working. So, I figured I should be able to use the Quorum plugin that I downloaded on another IDE (a cloud IDE would probably be better). I keep failing and I honestly don't know really know what I'm doing. I'd prefer not to pay for an IDE. I tried orion's cloud ide "che" but it won't let me download the plugin via the internet or give me an option for uploading or running a native file.
Basically, I would like to find someway I can use quorum on my Mac.
Please help.
Doing all this for my graduate degree.
Thanks.
Em.
In order to use The Quorum Programming language, it MUST be in the Netbeans IDE. No exceptions.
The process of installing the plugin for Quorum Language Support is as follows:
MAKE SURE YOU HAVE THE LATEST VERSION OF THE JAVA DEVELOPMENT KIT!!! - This is VERY important as Quorum 3.0 uses the Latest Version of Java and Quorum compiles to Java Byte Code.
You MUST Have Netbeans 8.0 or greater (at most Netbeans 8.0.2). - This is also very important as Quorum 3.0 takes advantage of features in Netbeans 8.
Go to the plugins page. This can be done by clicking on "Tools" in the Menu Bar and then going to "Plugins"
Go to the Settings Tab and hit the button that says "Add"
In the Name Field, Type "Quorum"
In the URL Field, Type the following: http://quorumlanguage.com/updates/quorum/updates.xml
Now under "Available Plugins", Check the Box for Quorum
Click the Install Button
Restart Netbeans.
Now, upon completed load of the Netbeans IDE, The Quorum Module should ask you if you would like dictation of everything you do. If you do not want this, tell it that you do not. If you do, then go for it.
When you go to Create a new Project in Netbeans, you should see an option for Quorum. If you do see this,then you have successfully installed the Quorum Plugin to Netbeans.

Debugging Visual Studio web application in Release Mode

I have a Visual Studio 2013 Web Application project that breaks when in Release mode. No console errors are thrown and I think that it must have something to do with script minifying/concatenating. Everything's fine when I build in Debug Mode.
So I'm trying to figure out how to debug when in Release mode and having no luck.
Most articles, like this one, suggest modifying C/C++, Linker and other properties... but I don't have see those options, I assume because I'm working on a web app project.
Are there other ways I can enable debugging, break points, console.logs, etc in Release Mode?
If you're trying to debug a web application then no you're not going to see those options, as they're only available for C++ solutions. To debug a C# or VB web application you need shouldn't need to do any special configuration.
If it's not working however there are some simple things you can check, firstly that the PDB files are generated. These are essentially debug symbols that match the original source code up to the compiled output, allowing visual studio to step through the code and they should be placed in the same directory as your DLLs.
Once you've got your PDB in place all you need to do is attach the debugger. Now for a web application this can be a little confusing at first (if you're using IIS). IIS has several application pools:
The IIS process that you want to attatch to is called w3wp which is a little confusing at first. And potentially there are several of them (one for each AppPool that is active and running). Make sure you've got the Show processes from all users checked to see the processes listed:
To make this whole process easier, if you're running a version of Visual Studio that allows extensions take a look at AttatchTo. It adds a menu option you can click (and convert to a toolbar button/shortcut) that will automatically attach to all the IIS instances to debug your code.

How do I properly run the VJET development tools for NodeJS on Eclipse?

The default javascript editor for Eclipse has very poor outlining and code completion. As a result of this, for any modern javascript application like ExtJS or NodeJS where you need to write a lot of object literal statements, Eclipse becomes pretty useless. And it is impossible to ask how to do this properly.
Now I found that Ebay Open Source seems to have tools that are specifically designed to replace this flaw in the standard editors, both for javascript in general as for NodeJS specifically.
Installing the normal NodeJS V8 debugger on a default WDT install of Eclipse is pretty straightforward, and apart from setting up some script mapping, it's easy to get to work.
But when I tried installing VJET, stuff just didn't work. No code assist at all, no debugging anymore, nothing. VJET mode was set as default for debugging and stuff, but when I couldn't get it to work, I couldn't find any option to switch back to normal Eclipse/JS Editor/V8 Debugger either. Even when I removed all VJET stuff, my Eclipse installation was bombed and a complete wipe of the workspace and home configuration + downloads finally fixed this.
So I was hoping that anyone could explain:
What are the exact steps to getting VJET to work for Node.JS development in Eclipse, and possibly how can one switch between 'VJET' mode and 'default' mode?

Is there a working JSLint Eclipse plug-in?

Can anyone point to a functioning JSLint plug-in for Eclipse?
Use this:
In Eclipse, Install New Software to http://svn.codespot.com/a/eclipselabs.org/mobile-web-development-with-phonegap/tags/r1.2/download
I used jslint4java to add jslint to the Eclipse plugin for Android PhoneGap development. If you're not interested in PhoneGap or Android, you can choose only the jslint4java feature in the install wizard
Usage information here.
There is a plugin here and it works ok. (site is down sometime in 2011)
The update site is http://update.rockstarapps.com/site.xml (site down 2012-07-24)
You can also run jslint4java as an external tool:
Download jslint4java
Put jslint4java.jar somewhere
Add an external tool configuration in Eclipse (Run > External Tools > External Tools Configurations > Program > New...):
Location: /usr/bin/java
(or your path to javaw.exe)
Arguments: -jar /path/to/jslint4java.jar ${resource_loc}
Now you can select a js file in the Project Explorer and run jslint4java from the external tools menu.
I think I've found the simplest solution. If you install Aptana Studio, a free Eclipse plug-in, you get among other things, an excellent JavaScript IDE with support for Ext, jQuery and other major libraries.
Using these instructions (copied here in case blogspot is blocked at work), you can easily turn on JSLint support.
You can enable it by doing:
Open Aptana Studio- Go to Window > Preferences
Go to Aptana > Editors > JavaScript > Validation in the left hand menu
Check "JSLint JavaScript Validator"- Hit OK- Go to Window > Show View > Validation
(may need to go to Show View - Other - Aptana Views)
You'll see the Validation on the bottom right of the screen- Now also click Toggle Information and Toggle Warnings (found on the top left corner of the validation pane)
You're all set. JSLint will warn you whilst writing code
You might consider a JsHint Eclipse plugin as an alternative.
From what the project objective reads, JSHint was originally a fork of JsLHint with more option configuration.
Eclipse plugin http://github.eclipsesource.com/jshint-eclipse/
JsHint reference http://www.jshint.com/about/
I do this a different way that integrates nicely with the IDE In eclipse most of this is one time set up and then it becomes quite easy to validate your code after that.
Help -> Install new software
Click the 'Add' button
Name : Rockstar Apps (or whatever you want)
Location : http://update.rockstarapps.com/site.xml
expend the selection and check Rockstar JsLint
Click 'Next'...again
Accept and install
(you'll have to hit okay when it prompts you about installing unsigned content).
Restart Eclipse...
Almost done
Now when you want to validate your javascript right click the file Rockstarapps -> Validate with JsLint...
customize your validation settings and your done. (i usually just choose recommended)
the problems will show up in your problems panel.

Javascript, Firebug: How do I have multiple views or what is the right of way of doing development?

Most of my javascript work is done with Firebug and I feel annoying most of the times having to switch between the HTML mode and console mode (which again I split into output mode and input mode). When I switch to a different page to see the HTML and come back, I lose the code that I write. What is the best way to go about developing javascript applications using firebug?
Something like a mini IDE would be awesome: It just has to let me insert some code, examine the current page and then let me execute it. Any suggestions?
I use a simple text editor (vim) to write Javascript and HTML, and I check the result every now and then in Firefox. I have always two windows open: one for my text editor, and one with the current page open in Firefox. After saving a change in the Javascript, I switch to the browser and refresh the page to observe results. That was my workflow until recently.
A couple of weeks ago, I discovered the Combiner tool by Nicholas C. Zakas. To release my Javascript code, I am now using a complete build process based on Apache Ant, similar to what I was using while doing Java development previously.
The first step is to check the Javascript code with the JSLint tool by Douglas Crockford. I used to painfully copy and paste my Javascript code in the online version of the tool, once in a while; being able to run it on all my Javascript files at once with this Ant script is a huge convenience.
The second step is to combine all my Javascript files into a single file using the Combiner tool. The third step is to minify the Javascript code using YUI Compressor by Yahoo!. These last two steps allow to optimize the delivery of Javascript code to reduce page loading.
You can find an example Ant build file that you may adapt to your own needs. I am currently using this file to build my own Javascript library, bezen.org.
The other answers so far have been correct: I've never heard of anyone actually developing inside Firefox/Firebug, because it's a tool designed for debugging, not coding. To do your coding, you should use a tool designed for it (either a text editor or a full-fledged IDE).
But that being said, you might want to check out FireEclipse (Link). It will allow you to integrate Firebug with the Eclipse IDE (which itself has at least three different JS plug-ins to choose from). Alternatively I think the main (aka Web Standard Toolkit, aka WST) JS editor for Eclipse has some functionality which is similar to Firebug, but I've never used it so I don't know the details.
Hope that helps.
Write your HTML in an editor/IDE
Save your changes
Preview it in your browser
Debug using Firebug
Make your code edits in your SOURCE CODE
Repeat
Firebug is for debugging and allows you to do some "what if" fiddling while the page is live. This is not a replacement for an IDE.

Categories