Javascript Library Development Environment
in [JavaScript]
|
Prev: is there any reason not to write google analytics code to single file on my server for speed?
Next: FAQ Topic - Why do some posts have <FAQENTRY> in them? (2010-01-16)
From: Thomas 'PointedEars' Lahn on 15 Jan 2010 11:09 Ivan S wrote: > On Jan 15, 2:07 pm, Stevo <n...(a)mail.invalid> wrote: >> 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 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 -- Danny Goodman's books are out of date and teach practices that are positively harmful for cross-browser scripting. -- Richard Cornford, cljs, <cife6q$253$1$8300dec7(a)news.demon.co.uk> (2004)
From: Jorge on 15 Jan 2010 12:00 On Jan 15, 2:07 pm, Stevo <n...(a)mail.invalid> wrote: > (...) For Safari and Chrome there's > nothing useful for debugging. WebInspector video @ ADC(a)iTunes: "WWDC 2008, Session 418 - Debugging Websites Using Safari's Integrated Developer Tools" https://deimos.apple.com/WebObjects/Core.woa/BrowsePrivately/adc.apple.com.2131504983.02131504989.2136683884?i=1451393751 +videos @ ADC(a)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 -- Jorge.
From: Stevo on 15 Jan 2010 12:26 Ivan S wrote: > On Jan 15, 2:07 pm, Stevo <n...(a)mail.invalid> wrote: >> 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 Thanks for that, I tried Firebug lite already. It's only mildly useful.
From: Stevo on 15 Jan 2010 12:29 Jorge wrote: > On Jan 15, 2:07 pm, Stevo <n...(a)mail.invalid> wrote: >> (...) For Safari and Chrome there's >> nothing useful for debugging. > > WebInspector video @ ADC(a)iTunes: > "WWDC 2008, Session 418 - Debugging Websites Using Safari's Integrated > Developer Tools" > https://deimos.apple.com/WebObjects/Core.woa/BrowsePrivately/adc.apple.com.2131504983.02131504989.2136683884?i=1451393751 > > +videos @ ADC(a)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 > > -- > Jorge. 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.
From: Thomas 'PointedEars' Lahn on 15 Jan 2010 20:41
tpot wrote: > 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 -- Use any version of Microsoft Frontpage to create your site. (This won't prevent people from viewing your source, but no one will want to steal it.) -- from <http://www.vortex-webdesign.com/help/hidesource.htm> (404-comp.) |