AJAX Toolkit Beta3
by Dave Carroll on April 21, 2006 at 11:25 AM
First, I want to thank everyone who has submitted bugs and feed back on the AJAX Toolkit to date. Your feedback is crucial for our mutual success and sanity.
I realize that alot of you have been grouping about in the dark due to lack of documentation and any kind of getting started guide. Beta3.3 represents the final beta version of the toolkit. There will be some tweaks here and there and, hopefully, performance enhancements over time, but the core of the toolkit has been ironed out.
View the AJAX Getting Started - Part 1 guide.
View the AJAX Getting Started - Part 2 guide.
TrackBack
TrackBack URL for this entry: http://www.typepad.com/t/trackback/324572/3614765
Listed below are links to weblogs that reference AJAX Toolkit Beta3:
Tracked on April 23, 2006 07:45 PM:
» How Javascript will dent PHP and JAVA hegemony from Kingsley 2.0
[Read More]
Comments
Posted by KevinH on April 28, 2006 11:42 AM:
Glad to see this moving along. Can I recommend for the next update you validate an try to eliminate all the lint/warnings in the JS code. This ensures the code is bug free and help maintain better cross browser compatibility. A good tool to help with this is http://www.jslint.com
Posted by Milos Musicki on May 3, 2006 12:11 PM:
Can someone please let me know where can I download the full manual (not just getting started documents) for the AJAX toolkit?
Thank you.
Posted by tyshock on May 3, 2006 12:53 PM:
Milos:
The best documentation is to install the appExchange toolkit for eclipse, then, from within eclipse, go to help->helpContents->AppExchange Toolkit->AJAXToolkit.
These are the 'javadoc' style class references. Not great, but a decent reference to understand how the objects interact.
Posted by Jonathan Keener on May 4, 2006 07:52 AM:
I noticed when I tried the include with the "?browser=true", I started receiving the "This page contains secure and nonsecure items" Warning Dialog in Internet Explorer. If I do not include the "?browser=true", this does not occur.
Is there an easy way to include the additional browser code without receiving this message in IE?
The comments to this entry are closed.