FWIW, no Ajax library plugins will ship with Studio 1.3. Instead you'll be able to choose which ones to install on first launch (and whenever after that by choosing Help > Install Aptana Features...

Yeah, it was hard to miss that the AJAX libraries have been left out... with one being greeted by the Install Feature dialog first. However, I was under the impression that the visual jQuery view came with the jQuery plugin bundle .jar file. so if it's not too much of a hassle maybe you can sneak it back in? It helped me alot when first starting out with jQuery and it really was one of the primary features why I chose Aptana Studio for my learning - because the jQuery support felt quite complete and naturally.

Now with the $/jQuery Code-Assist bug (no Code Assist for '$' but only for 'jQuery') and the visual jQuery browser gone this feels much less naturally. If you prefer you could also just tell me how to infuse the current jQuery plugin bundle in my local Aptana copy with the Visual jQuery view - like where to change some values so that it will appear in Aptana. That would work fine for me too.

1. Change the .jar extension on the jquery 1.2 and 1.3 plugins to .zip and double-click to unzip them.
2. Copy the view folder from the 1.2 plugin folder to the 1.3 plugin folder.
3. Open the plugin.xml file from the 1.3 folder in a text editor.
4. Find the commented-out org.eclipse.ui.views extension point and replace it (and the comment markers) with this:

<extension
         point="org.eclipse.ui.views">
      <view
            category="com.aptana.ide.documentation"
            class="com.aptana.ide.core.ui.views.browser.DefaultBrowserView"
            icon="views/visual_jquery/images/favicon.png"
            id="com.aptana.ide.documentation.jquery.visualjquery"
            name="Visual jQuery">
         <description>bundleresource://com.jquery.1.2/views/visual_jquery/1.2.6.htm</description>
      </view>
   </extension>

5. Save the plugin.xml file.
6. Select all the files in the jquery 1.3 plugin folder (not the folder itself!) and zip them up again.
7. Change the extension from .zip to .jar.
8. Move that .jar to the top level of the plugins folder (if it's currently inside the jquery 1.3 folder).
9. Repeat steps 6-8 if you want to use the 1.2 plugin, too.
10. Delete (or move out of the plugins folder) the jquery 1.2 and 1.3 folders, leaving only the .jars.

Hopefully that'll get you what you want; I'll try to post a new jQuery plugin (it'll be 00002) tomorrow.

Had to rest for a moment was a long night. I followed your instructions to the letter and it worked perfectly. The Visual jQuery view is back in.
A tiny problem remains: both Visual views (Visual jQuery and Visual ScriptDoc) show up blank... and now that I remember it I had this problem from the start with Visual ScriptDoc and Aptana Studio 1.3RC2.

I was able to work around this by opening the internal browser and navigating to the 1.2.6.htm manually so it shouldn't be tied to the view itself. Maybe those views are looking at some wrong URLs...

closest(expr)
context (Core/jQuery Object Accessors)
selector (Core/jQuery Object Accessors)
die(type, fn)
live(type, fn)
toggle(switch)
toggleClass(class, switch)
$.fx.off
$.isArray(obj)
$.support

It doesn't show what was changed however...

For the changes between jQ 1.2.6 and 1.3, I got those from the jQuery API browser as well – I used it as a reference to update the docs.

I was never sure if I got it all in, thats why I decided to change the api-loader.js and api-docs.js scripts included with Visual jQuery a little so that they would use the XML docs that I generated from jQuery's SVN trunk with the createjQueryXMLDocs.py Python script. That way I was absolutely certain that every bit is in. I also got rid of the older unused jQuery libraries that where still included for no apparent reason. I also changed the exmaple URL to use at least jQuery 1.3.1 instead of 1.2.6 since when viewing the API for 1.3.x it only makes sense that the actual examples use the version one is viewing the docs for. I also slightly changed some CSS code so that the application would behave more nicely on smaller display sizes.

Finally, I also wrote a little readme/how-to about how one can automatically update the XML docs for future versions quite easily. That way other user do not have to wait for us to update to the latest version. I believe it is the superior way to go since the functionality was there already and it doesn't take a whole lot of effort or knowledge to update for future versions.

As a workaround for the Visual jQuery display bug one could use a Monkey script to open the Internal Browser at the URL thats pointing to the Visual jQuery htm file...

For the visual_jquery view it looks like you added 1.3.2.htm and replaced the api-docs.js with the new version without including the data/jquery-docs.xml file.
Unfortunately, this broke both versions.

Because 1.2.6 relies on the full documentation passed as JSON object in api-docs.js' loadDocs() function and I had to remove the JSON data from loadDocs() so that the ajax request in api-loader.js to the jquery-docs.xml file would instead be triggered.

If you look at api-loader.js on line 22 there is the line
url: xmldoc || 'data/jquery-docs.xml', // generated from jquery source: /tools/wikiapi2xml/createjQueryXMLDocs.py

so for 1.3.2 to work it needs the jquery-docs.xml file in a /data dir.

I am not quite sure why 1.2.6.htm is included for a 1.3.2 release of the jquery support plugin.

Btw, I hadn't meant for the plugin to be "live" yet; it has to go up for testing, but I didn't intend for it to be downloaded by users. I'd forgotten that technically it would be live because jQuery 1.3 as a feature is live.

If you want you can also just include the cleaned up folder structure from the zip above but that's up to you of course.

Cheers

/*

• Menu: jQuery > Visual jQuery 1.3.2
• Kudos: Andre Berg
• Key: M1+M3+1
• License: EPL 1.0
• DOM: http://download.eclipse.org/technology/dash/update/org.eclipse.eclipsemonkey.lang.javascript
  */

function main() { webView = views.getView("VisualJQueryView"); webView.showView(true); webView.setTitle("Visual jQuery v1.3.2"); webView.url = "/Users/andre/Documents/Aptana Studio Workspace/Aptana Studio Extensions/views/visual_jquery/1_3_2/1.3.2.htm"; }

of course the webView.url will have to be changed to the URL where the downloaded visual_jquery_1_3_2 and it's 1.3.2.htm file resides.
and you can change the Key comment property to something other than CMD/CTRL+ALT+1.

I also think I know what's wrong with the internal web browser and the Visual... views:

I have the impression that they tend to break when a URLencoded URI is provided.
Note that in the webView.url above I provide the pathname as copied directly from the properties dialog of my visual_jquery project.

However, when I enter this instead it won't work:

"file:///Users/andre/Documents/Aptana%20Studio%20Workspace/Aptana%20Studio%20Extensions/views/visual_jquery/1_3_2/1.3.2.htm"

The same with other URLs that I enter into the internal web browser...

changed the googleapis jquery link for the examples iframe to use the 1.3.2 version now that it is updated.
changed the included version of jquery to use the minified 1.3.2 version instead.

Sure. Take whatever you need from it, when you need it

As before, if anyone finds uses for it, then by all means, take whatever you need from it...

• $.browser et al. and $.support.boxModel are not functions
• prependTo() and appendTo() now correctly show that they need a selector and not some content as function arguments
• minor adjustment to the layout
• included a favicon.png that matches the new jQuery 1.3 logo

Cheers,

André