version 2.2.5 (hotfix)

things done in version 2.2.5

We've made two minor (but important none the less) fixes in this version.

1. Some parts of the code were leaking. Now they are fixed and sardalya is 100% leak-free.
   
2. _.load shortcut had a minor parameter error. We've fixed it as well.

things done in version 2.2.4

things done in version 2.2.4

We replaced the compression logic of orkinos (sardalya's js compressor engine) with Dean Edwards' packer. This resulted in a better compression ratio (almost twice better), in the compressed version of sardalya.

Dean generously provides a **C#** version of packer. Thank you Dean for sharing your library with the rest of the world.

So what's done in this version:

1. Added new Shorthand notations.
   
2. Plus some javascript optimization.
3. Added a DOMManager.quickLoad method which triggers a passed delegate as soon as DOM content is ready. This is much faster than traditional window.onlaod approach, if you have images and external object in the page.
4. New methods for custom DOM-node creation have been added.
5. We have a new Try object which is used to execute a group of function even if an error occurs during execution.
6. EventRegistry now has a finalize method and a remove method.
7. We have a brand new MessagePane object.
8. We have optimized the AJAX stub XHRequest further.
9. Used a new compression algorithm which resulted in nearly 60% code reduction in the production release.
10. Updated the bug repository.
11. Updated the wiki.
    

released a hotfix

Just fixed a few small (but important) bugs in some of the core objects.
The bugs were not there before and they have been introduced in the recent stable version.
Unless they are fixed, the API will not work properly in Internet Explorer.
Oddly enough, those bugs do not affect Mozilla and Opera :)

Luckily we've fixed all of those little bugs :).

The fixed version (2.2.1.unstable) is more bug free than the former one, and we strongly recommend it.

You can download the latest version from http://www.sarmal.com/sardalya/Download.aspx


.

things done in version 2.2.0

things done in version 2.2.0

1. We mostly worked with enhancing the Effect object. Give it a try and see it for yourself.
   
2. Plus some javascript optimization.

s@rdalya is now ready for the new ajax project we are working on.

things done in version 2.1.9

things done in version 2.1.9
This is a transitional release and there will be much more in version 2.2.0.

1. The documentation has moved to s@rdalya wiki.
2. The API is JSLinted. Some seemingly unnoticed bugs were killed. Code optimized.
3. Shortcuts are a new feature, which increase typing speed and hence make coding faster, when getting used to it.
4. s@rdalya now has a central bug repository.
5. We have two brand new objects: ModalDialog and Effect.
6. We have enhanced XHRequest to better serve your AJAX needs.
7. We have decoupled the Editor from the API. We have stopped its development for some time, though we plan to use its codebase somewhere else (like a template management system).
8. StyleManager.remember now receives a timeout value as the third parameter. This is the number of days that the style will be remembered.
9. And many more changes which are hard to recall. We worked hard, but the end result was worth it.

We now have a wiki.

s@rdalya 's API documentation was formatted in XML for maximum portabilility.

However, as the time goes by the documentation grew more and more.

The API develops too fast and it is really hard to keep the documentation up-to-date.

So I've chosen an easier to edit format:

a wiki!

This way, s@rdalya will be open for discussion and collaboration of anyone who's interested.

Although the pages and the general layout of the wiki are incomplete, I think it's a good time to introduce you with the

peanut and butter wiki of s@rdalya.

.

pending the development of Editor

Now that Opera supports desing mode (from 9.0 developer release and further), my article on the utopic rich content editor that works in opera and all dom-supporting browsers for that matter is now more of experimental/academic importance.

I guess other non-supporting browsers will sooner or later will converge to support designMode, and their support will be almost identical and will not lead any cross-browser issues (fingers crossed).

Opera, supporting designMode just the same way mozilla does, is just the beginning of this forecoming convergence.

Though the part of the article discussing "the necessity of designmode" is worth reading imo.

Plus, the code is not useless none the less and I plan to integrate it into a more complicated infrastructure, something like a content management system, or more like a template generator application.

I am pending my development on the Editor for some time.

Instead I will focus the ajax integration and effects modules of sardalya.

The new version of sardalya will be ready within at most two weeks.

Just wait and get excited until that time.

how do you like your sardalya? mexican. hot and chilly please!

Then here it goes.

sardalya is now on hotscripts dot com.

Cheers.