AJAX support

There are always issues with this kind of plugins. I remember Phil's tailor ajax plugin. First we neve could use it in modules. Second he was selling advanced version. So to add advanced ajax features our customers have to go to Phill's website to buy. THis is not good idea I think.

The same may happen here. What if we add full support on his plugin and later he start selling it?

Another problem with ajax wat to work on not component native pages. For example you see com_content but in menu com_cobalt with favorite ajax button. If we relay on plugin, we have to be sure this plugin loads all needed classes. But what if not?

Another thing is complexity. Would be not smart to add another requirement to understand how Cobalt will work to install this plugin. We wil have questions like "Or my follow buttons does not work!" and will answer "You have to install plugin from this guy!"

Another thing which is always an issue there in compatibility. The situations like situation they had with Nooku may happen very often. For example this guy release new version with something changed. But we do тещ change so we state that our customers have to install this version of plugin. But they have other extensions that require higher version of plugin, ...

That is why we use only direct AJAX. It means we do not use any adapter or wrapper. We make it directly so we ensure it works anywhere in any case no matter what.

The raw AJAX we use now is also fully ajaxed. And not difficult to write.:D