The making of WebCoder 2009 – part 12
December 3, 2008
It brings me a lot of pleasure to write this specific part in the "Making of..." series :). For the last couple of WebCoder versions, and with phpCoder as well, the most requested feature has been JavaScript IntelliSense. JavaScript is more popular than ever before, and I have been wanting it just as much as you guys. But if you look around, you will notice that only very few editors has JavaScript IntelliSense - JavaScript is a tricky technology to support! Fortunately, I have received loads of help from the most talented JavaScript guru I know, Brian Hjøllund. He has written the JavaScript parser for WebCoder 2009, and it allows me to combine knowledge of your code with knowledge about both the JavaScript language and the Document Object Model and thereby bring you some very cool functionality. I promised to make WebCoder 2009 even more web-centric, and I think that the added JavaScript functionality is a very important step in that direction. Here's a couple of screenshots that will show you what I'm talking about:
So, what do you think? :)
« So, what do you think? :) »
Great, as usual :D
looks all great. is there a way to extend the js parser for better support a Framework like JQuery etc.
greetings
Rene
I’m not sure I follow. There’s no need to extend the parser, since jQuery is just regular javascript, it doesn’t “invent” anything new, it just takes advantage of what’s there already, javascript.
Can not wait to test it with Prototype and other JavaScript frameworks.
Thank you both for great work.
I agree with the above… I am very excited to test this.
keep up the amazing work!
brian, sorry for the confusion.
The current Webcoder parse id’s and classes from css definitions. Is there a chance to see id’s and classes from js files in Webcoder 2009. I know this is not a part of the jsparser.
for example:
following line of code in a js file
effect(“#clipHorizontally”, “clip”, { direction: “horizontal” });
when i edit my document it would be great to see it when type div id=”my_js_ids_here”>
Well, that wouldn’t help extending the parser, it would introduce an unnecessary abstraction. A way to do it, is a layer outside of the parser, but that’s currently not supported.