AndreaCfm

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 ....

I decided to play around with cfwheels cause I was amazed by some examples I saw around and I have to admit is good fun.

After 1 hr testing I realized that no ioc support is build into cfwheels and ..... I really cannot live with no Ioc container available at any time so I decided to add a plugin for managing a beanFactory into cfwheels.

Probably is not the best cfwheel plugin ever written but was very easy and painless. While I tend to be very OO guy I am amazed by conventions in last period ( I am also playing with Sean Corfield FW1 ). While I am also an happy user of Coldbox and ModelGlue I find that sometimes frameworks added complexity also to easy tasks. From here my desire to look into frameworks that make of conventions their core basement.

In my mind conventions means less code in default situations and about this cfwheels and fw1 at the moment are the best. Btw I also think that for a more complex task Coldbox really has something more to help development of more advanced applications.

You can find the plugin here to play with it and have a look to cfwheels.

I am a big coldbox fan and I am very glad to post about the release of the ColdBox Book. I am ordering a copy for me and, if you are serious about coldbox, I strongly recomend it.

Coldbox has always been very well documented and the book will surely be an interesting way to go deeply into coldbox framework.

Thanks to Luis for the hard job.

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.