I don't know what the proper place is to put this, but after playing with Orcas' Javascript editor I would like to suggest a few things. BTW, I am finding myself regularly using Aptana for JavaScript editing and can't wait to get back to a single unified editor, so I really want Orcas to succeed; BTW, IMNHO Orcas still has to get around #1 on this list to match Aptana. Since I now know #1 is there I may be uninstalling Aptana soon! (thanks guys).
1) I need Intellisense in SCRIPT files (read .JS files) to be able to somehow give me access to objects that are in other script files. Aptana gives me the concept of a profile where I drag various script files into the profile area which adds their contents to the Intellisense (for any file I'm editing JS in). I've actually thought that maybe the solution is to have some syntax that is a comment that notifies both Orcas and a programmer using this script to be aware of what files are necessary for this script to work... something like:
// Using "../MSAjax.js"
2) Refactoring! Yes, I'm serious! The main refactoring that I want is to be able to highlight code and to extract a method... rename and make property is just icing on the cake for me, but extract method would be awesome! (Aptana doesn't have this one)
3) Built-in JS library testing. Ok, I know this is a stretch, but it's worth asking for.
4) While I'm at it, get Nikhil K. to turn over Script# and add it to Orcas! It rocks and would really help adoption to MS Ajax (since oen only really needs to know C# to use Script# and therefore create JS code)
Technorati Tags: Orcas, JavaScript editor