First of all, I would like to help everyone at InterAKT for their commitment to this product, and the entire beta group for believing in us.

After months of hard work, we have managed to release what we hope is going to be one of the most successful product in InterAKT.

MX AJAX Toolbox is a Dreamweaver extension that enables AJAX development in Dreamweaver. Not only it has a perfect integration with Dreamweaver, but it is also based on one of the most revolutionary AJAX platforms, supporting features like degradability, web services and implementing lots of useful controls and widgets.

Here is a quote from one of our customers:

"This toolbox is nothing short of revolutionary!  I've been playing around with several of the open source AJAX libraries, but they can't compare with the simplicity of implementation that InterAKT's MX AJAX toolbox enables." Timothy Rand- MX AJAX Toolbox customer

And here are to top features:

• AJAX dynamic table
• Graceful degradation
• Categorize items with drag and drop
• Edit-in-place
• AJAX site wizard
• AJAX photo gallery

More links:

• MX AJAX Toolbox homepage
• Product live demo
• Whitepaper

Your name*:
Your email*:
Your comment*:
Word verification*:	Type the characters you see in the picture above

Today I have tried to integrate Spry and MX Ajax Toolbox and guess what?

After ~ 1 hour of de-bugging, I managed to pass all the problems and integrated the 2 products.

What I tried to do was putting some Spry regions and repeaters in a panel. The problems I encountered were mainly some Spry miss-usages of Arrays. There are a few places where they use "for i in array", and we inherited some Array prototype modifications. But I replaced the []s with {}s and now it's working.

Also, they attach onload events to the window object to initialize the regions. I had to move that in the page in <script> tag:

            <script>Spry.Data.initRegions();</script>

Anyway, I'm glad it worked. I'll come back with more details on Monday.

Your name*:
Your email*:
Your comment*:
Word verification*:	Type the characters you see in the picture above

We have just published a sneak preview on our Ajax Toolbox:

http://www.interaktonline.com/Support/Articles/Details/Sneak+preview+into+MX+AJAX+Toolbox.html?id_art=42

Also, we have written a nice white paper detailing different aspects of the product:

http://www.interaktonline.com/files/White%20Papers/MX_AJAX_Toolbox_WhitePaper.pdf

Bogdan

P.S. For those of you who don't know what the product does, MX Ajax Toolbox enables Ajax development in Dreamweaver.

Your name*:
Your email*:
Your comment*:
Word verification*:	Type the characters you see in the picture above

When building Ajax websites, speed is a very important factor. Most of the Ajax-based websites are loading quite slowly, and this can be annoying sometimes.

But why are these websites loading so slowly?

The main reason is that for the website to function correctly, all the Ajax application logic must be loaded into the client. And sometimes, we're talking about a lot of JavaScript code...

On the other hand, we have the degradability concept that says that a website should function correctly even if JavaScript is disabled.

Well... ok, so the website will function if JavaScript is disabled, then again it will wait for the whole Ajax logic to load before actually functioning. This does not really make sense...

Moving one step further, I realized that if a website would degrade while the Ajax functionalities are loading, then you would get both speed and Ajax.

What does this mean: When you access an Ajax-based site, the site loads very fast, and all the functionalities are available for you (the Ajax part of the site is not yet loaded). Then, if you click on a link, it would degrade and the whole page would reload. In the meanwhile, the required JavaScript files are asynchronously loaded from the server, and once everything is loaded and we're ready to go, Ajax comes into action and the site is automagically transforming into an Ajax website.

So, using this technique you would get the speed of a "classic" website (and here I mean the 1^st page loading time), and the power of Ajax.

Does this make sense?

We've just updated our Ajax integration demos (http://mail.interaktonline.com/demos/ajax_integration2/) using this technique and it seems to work. Even on a dial-up connection, after a few clicks, the JavaScript is loaded in the client and the site is 100% Ajax.

And one more thing: If you are interested in the MX Ajax Toolbox, just let us know: http://www.interaktonline.com/demos/ajax/?Content__state=Register

Bogdan

Your name*:
Your email*:
Your comment*:
Word verification*:	Type the characters you see in the picture above

These last days we've been working a lot on integrating MX Ajax Toolbox with other products. And guess what? We've managed to make huge improvements in this direction.

We are working right now on the next prototype, and one on its main features, (beside the fact that it will work with norton firewall :P) is the compatibility with other products.

So I took some of our products (that you're supposed to use in a front-end) and installed a dot version of MX Ajax Toolbox on top of them, and I managed to do this:

http://mail.interaktonline.com/demos/ajax_integration/

It's a site with multiple entries where you will see how well the products integrate with each other.

The main goal was NOT changing the regular workflows and not updating the current products.

Even more, you'll see that we've proved an integration with the default Dreamweaver Server Behaviors (like the repeat region, nav bar and the rs statistics).

So... enjoy!

Bogdan

Your name*:
Your email*:
Your comment*:
Word verification*:	Type the characters you see in the picture above