Amplify.JS (pre alpha) ready to play with
http://www.codeaccessory.net/2007/11/amplifyjs-pre-alpha-ready-to-play-with.aspx
If you’ve been itching to play with some javascript and visual studio 2008 (beta). I have a pre-alpha project for you to play with. The intellisense works in visual studio and there is even a set up for Ajax Doc and SandCastle Helper File Builder. It took a bit of tweaking and testing, but here it is.
https://labs.opensourceconnections.com/svn/amplify/amplify.js/trunk/
currently listening to.. u2 – elevation
September 4th, 2007 at 2:41 pm
All good comments, thanks. I’d like to point out that I developped AjaxDoc for our own documentation needs (we use it internally to generate our Intellisense files and documentation), which explains why today it’s limited to stuff that you build on top of ASP.NET Ajax. On the other hand, the project is under the MS-PL license and I’d be more than happy to take contributions that widen its scope to other programming styles or remove the current IE only limitation (which does not come from having to write the xml file (this is handled server-side) but from some limitations in the way Firefox and others handle XML and XPath on documents created from strings).
September 4th, 2007 at 7:44 pm
I had actually planned on writing some extensions for Ajax for at least prototype inheritance, possibly dojo as well, and probably add the remarks tag, rather than trying to create my one tool (since there is already plenty for me to do) and publish that later along with how to include a javascript meta data file so that you could take a defined object, if found and add __class, __type and etc and includ the script as more of a meta file during development in order to enhance intellisense, with out having to totally adhere using the asp.net ajax object model.
Right now thats a bit on hiatus till I get what I currently have working, totally documented, into source control, and tested. (Including a different take on BDD for javascript compared to something like ruby’s RSPEC and sprinkling “should” everywhere).
Granted this is constructive criticism, I definitely appreciate having a building block to work from, I hope other people see this and build on top of it. Especially if it would increase interoperability between tools and platforms. With that said, Thanks for sharing this and letting dorks like me point out stuff, so that someone out there will hopefully see a need and contribute.
November 21st, 2007 at 2:32 am
I too am disappointed by the gotchas of this feature. I may have found some ways lessen the pain in the future.
Would have been nice to just work out-of-box.
http://extjs.com/forum/showthread.php?p=89505#post89505