Javascript Library Development Environment

[tpot]

I have been using eclipse for a while to write javascript
applications. But when it comes to writing and maintaining fairly
large javascript libraries, I can't help but feel there is a better
way.

I would be interested in ideas and suggestions from anyone that has
developed a copmlex javascript application or library.

I can't seem to find much on the internet about IDEs that are geared
to this kind of development.

Thanks

 

[Thomas 'PointedEars' Lahn]

I have been using eclipse for a while to write javascript
applications. But when it comes to writing and maintaining fairly
large javascript libraries, I can't help but feel there is a better
way.

I would be interested in ideas and suggestions from anyone that has
developed a copmlex javascript application or library.

I am using Eclipse Galileo (20090920-1017) with JSDT 1.0.200.v200905242047
to maintain JSX and cannot think of any considerable problems doing that.
What is your use case and what are you missing?


PointedEars

 

[tpot]

I am using Eclipse Galileo (20090920-1017) with JSDT 1.0.200.v200905242047
to maintain JSX and cannot think of any considerable problems doing that. 
What is your use case and what are you missing?

I'm not attempting to create a general library, rather I am trying to
organise my own javascript as a library. I've come to the conclusion,
so far, that this is the best way to develope a large application in a
consitent way. As a library of components (whether or not they are
used in more than one place) and a set of small custom scripts
"plumbing" to use the components.

My use case, or at least what I think is the most relevant parts, is:
1. I wish to use multiple 3rd party general libraries, for example
JQuery and YUI
2. I wish to organize my javascript into many separate files for ease
of maintenance and to maximize the potential for reuse
3. Splitting the application into smaller components allows me to
focus more on what I'm current developing without having too much
mental noise.

I feel I am missing:
1. Library sensitive editing (where the editor understands the objects
and functions of the library) for 3rd party libraries
2. Library sensitive editing for the library I am developing /
maintaining
3. The abitlity to annotate dependencies between my many js files
4. The ability to 'compile' a number of js files into one based on the
requirements of a particular page or particular custom script.
5. The ability to run ad-hoc jsunit (or other) tests from within the
IDE at the push of a button.
6. See a visualization of the components and their dependencies.
7. Anything else that I haven't yet thought of

It may be I just need some pointers or education, or just a lot more
time searching on the net.

 

[Stevo]

I am using Eclipse Galileo (20090920-1017) with JSDT 1.0.200.v200905242047
to maintain JSX and cannot think of any considerable problems doing that.
What is your use case and what are you missing?

PointedEars

Any strong reasons for preferring JSDT over Aptana? Do you know if
either of them will attach themselves to JS running in a IE, Firefox,
Safari or Chrome? For me the only reason to want Eclipse+JS Plugin is to
debug code running on one of the browsers. Currently I use Firebug in
Firefox and MS Visual Studio in IE. For Safari and Chrome there's
nothing useful for debugging.

 

[Ivan S]

For Safari and Chrome there's nothing useful for debugging.

Chrome version 4 beta supports extensions. Here is one familiar:

https://chrome.google.com/extensions/detail/bnbbfjbeaefgipfjpdabmpadaacmafkj

 

[Thomas 'PointedEars' Lahn]

Chrome version 4 beta supports extensions. Here is one familiar:

https://chrome.google.com/extensions/detail/bnbbfjbeaefgipfjpdabmpadaacmafkj

And Safari 4.0.4 has a built-in debugger, among other tools. You just need
to enable the "Develop" menu under Edit/Preferences/Advanced.


PointedEars

 

[Jorge]

(...) For Safari and Chrome there's
nothing useful for debugging.

WebInspector video @ ADC@iTunes:
"WWDC 2008, Session 418 - Debugging Websites Using Safari's Integrated
Developer Tools"
https://deimos.apple.com/WebObjects...131504983.02131504989.2136683884?i=1451393751

+videos @ ADC@iTunes:
http://developer.apple.com/adconitunes

+info @ developer.apple.com:
http://www.google.com/search?q=safari+filetype:pdf+site:developer.apple.com
e.g. "Safari User Guide for Web Developers"

+info @ webkit.org:
http://www.google.com/search?q=webinspector+site:webkit.org

 

[Stevo]

Chrome version 4 beta supports extensions. Here is one familiar:

https://chrome.google.com/extensions/detail/bnbbfjbeaefgipfjpdabmpadaacmafkj

Thanks for that, I tried Firebug lite already. It's only mildly useful.

 

[Stevo]

WebInspector video @ ADC@iTunes:
"WWDC 2008, Session 418 - Debugging Websites Using Safari's Integrated
Developer Tools"
https://deimos.apple.com/WebObjects...131504983.02131504989.2136683884?i=1451393751

+videos @ ADC@iTunes:
http://developer.apple.com/adconitunes

+info @ developer.apple.com:
http://www.google.com/search?q=safari+filetype:pdf+site:developer.apple.com
e.g. "Safari User Guide for Web Developers"

+info @ webkit.org:
http://www.google.com/search?q=webinspector+site:webkit.org

Thanks Jorge. I really should have added in my question that I'd seen
all these things and find them all really bad. They also don't help when
you want to debug a specific older version of Safari. That's why I was
hoping that eclipse+aptana or eclipse+jsdt would do a proper job of
attaching to safari.

 

[Thomas 'PointedEars' Lahn]

My use case, or at least what I think is the most relevant parts, is:
1. I wish to use multiple 3rd party general libraries, for example
JQuery and YUI

I am afraid I cannot help you with that, because I made it a rule for
myself to try not to do stupid things.

2. I wish to organize my javascript into many separate files for ease
of maintenance and to maximize the potential for reuse

BTDT. No problems.

3. Splitting the application into smaller components allows me to
focus more on what I'm current developing without having too much
mental noise.
ACK.

I feel I am missing:
1. Library sensitive editing (where the editor understands the objects
and functions of the library) for 3rd party libraries
2. Library sensitive editing for the library I am developing /
maintaining

I think I have answered these only days ago.

3. The abitlity to annotate dependencies between my many js files

JSdoc or JSDoc can take care of that. Of course, there should be as few
dependencies as possible without sacrificing flexibility.

4. The ability to 'compile' a number of js files into one based on the
requirements of a particular page or particular custom script.

If copy and paste will not suffice, I doubt any IDE could. Usually one
uses annotations to have a script include the files in the correct order.
The most reliable way to do this is server-side, of course.

5. The ability to run ad-hoc jsunit (or other) tests from within the
IDE at the push of a button.

Since JSUnit as I know it requires a browser, you run the test case in the
browser. Eclipse can embed some browser components if needed.

6. See a visualization of the components and their dependencies.

Hard to do in a programming languages as dynamic as ECMAScript
implementations.

It may be I just need some pointers or education, or just a lot more
time searching on the net.

Probably. You appear to have missed all the Eclipse tutorials to begin
with.


PointedEars