While this can looks like a bad new .... well it is not.

Latest Railo BER ( 3.1.2.019 ) has included also the missing part of RailoAjax project into the Railo core distribution. From this point the development and maintenanace of the tags will be made directly from the Railo project itself.

As per today Railo included the following tags:

• cfajaxproxy
• cfajaximport
• cfdiv
• cfmap
• cfmapitem
• cfwindow
• cflayout and cflayoutarea ( just for tabs )
• ajaxonload function
• the js library that support the previous tags 

I am quite happy about this step. RailoAjax just started like a fun coding of the ajaxproxy and ended into the Railo core..... I really have to thanks all the Railo Team for the support received.

So please note the following:

• If you have a RailoAjax extension installed into your server or we context please remove it before update to 3.1.2.019. Or if you have already updated just remove the extension and restart the Railo.
• The RailoAjax website and the trac  will be shutted down when Railo 3.2 will be delivered.
• The RailoAjax extension provider http://railoajax.org/extensionProvider.cfc  will be still available up to the 31 december 2010.

If you have any issues please contact me or raise a JIRA tickect.

If you want to help coding new functionalities the source code is available on github.

I am a bit late blogging about this but I had a quite 'intense' maech.

Since version 3.1.2.009 Railo starts the ajax tags support . You can read more here.

Ok so what's teh big news? What make me proud is that I developed those tags and after a long debugging they are finally part of the Railo core engine. The tags comes from the RailoAjax project that will go on focusing on the remaining ajax tags to fill the gap with ACF ( that's the plan .... but it's a long road to do ....).

This is an example of how a community effort can really contribute to the main project. I am sure more efforts will come in the future ... so if you an idea .... some spare time ..... and you wish to contribute do not hesitate to contact me .... Railo needs you.

Railo Ajax arrived to version 0.5.2.

From this release cfmap has entered into the set of tags that RailoAjax ships. Cfmap support is still experimental and do not cover event the 50% of the ACF version but development is on the way.

See more here.

Remember that the demo app that you see online is installed ( if required ) when RailoAjax deploy on your Railo server. So you can have a look to the demo code that can help you on development stage.

Another important announcment is that CFMENU is on the way to appear from a community contribution. Cfmenu has been added to 0.6 milestone ( at least in alpha version ).

Next step will be focused on docs. For a month or so the main efforts ( over cfmap implementation ) will be on dodumenting what has been done up to know keeping an eye on bugs of course.

Do not hesistate to contact me for any question and of course .... project is open ... so feel free to jump in ....

A new version has been released.

The most interesting news is the complete refactor of the UI tags. RailoAjax library now provide bridges classes that need a speficic adapter to perform the action required. This allows to switch between one library support to another with no need to change the core code.

An example can be found here.

Once the concrete implementation is done ( the Ext cfwindow is already done ) you can choose the library using the cfajaximport tag.

<cfajaximport library="ext"/>

Having implemented a bridge pattern for any UI implementation has also allowed us to provide a set of new events provided directly by the Railo.Events engine that do not rely on the specific implementation making code even more portable. The following event has been added :

• Window.beforeCreate
• Window.afterCreate
• Window.beforeShow
• Window.afterShow
• Window.beforeHide
• Window.afterHide
• Window.beforeClose
• Window.afterClose
• Layout.afterTabSelect
• Layout.beforeTabInit
• Layout.afterTabInit
• Layout.beforeTabCreate
• Layout.afterTabCreate
• Layout.beforeTabRemove
• Layout.afterTabRemove
• Layout.beforeTabSelect
• Layout.afterTabSelect
• Layout.beforeTabDisable
• Layout.afterTabDisable
• Layout.beforeTabEnable
• Layout.afterTabEnable

What is usefull is that these events will always be usable in the same way not depending by the the tag concrete implementation. So If I need to listen to a window hide event and I have choosed the ext implementation I can use both the following syntax:

Railo.Events.subscribe(callback,'Window.beforeHide')
or
Railo.Window.getWindowObject('mywin').addListener('beforeclose',callback,this);

The RailoLayout.js package has already been rewritten with the default jquery implementation.

Version 0.5.2 will allow ui tags to receive an options arguments called 'args'. This struct will be converted into json and pushed into the implementation init method. In this way any config defined by the jquery or ext apis will become available. I am also working on a start for cfmap implementation. 

I have just finished to move RailoAjax project to the new, and final location, into the brand new space Railo is creating for supporting OS projects.

Site is now visible at http://projects.getrailo.org/projects/railoajax/

Svn has been migrated and can be found at http://svn.getrailo.org/svn/railoajax/  ( checkout as guest/guest)

Trac install  http://getrailo.org/trac/railoajax/

If you have a started project related to Railo or an idea you and you need support on your development please visit :

http://projects.getrailo.org

or drop me a line.