ColdBox 2.1.0 wishlist, what do you want?


ColdBox 2.1.0 wishlist, what do you want?

Posted by Luis Majano
Aug 17, 2007 00:00:00 UTC
As ColdBox has gathered steam and continues to do so, development for the 2.1.0 release has already begun. We are also in need of your observations and suggestions. We have gotten several wishlists and feature requests that will be implemented for version 2.1.0

 


Tim

http://code.google.com/p/litepost/

A ColdBox version.

Damien McKenna

SES. Any chance of moving it back from 2.3? I can probably write a .htaccess file for you to remove the need for the whole "index.cfm/go/my/page" part and have it simply do "my/page", if you'd like?

Dave

I second the SES, without the need need to type index.cfm/.

Luis Majano

I think both approaches can be done. One with the front controller and the other one by pure web server rewrite

Damien McKenna

Any plans for an official ORM?

Luis Majano

Not really, it is so easy to use Transfer or Object Breeze or Reactor with ColdBox, that it just doesn't make sense for me to delve into building an ORM. My personal choice is Transfer, I have been using it for a while now and don't see why I would ever want to create one.

John

How about adding the File Browser from the Dashboard as a plugin?

Dave

Handling form data like this:

http://www.briankotek.com/blog/index.cfm/2007/9/4/Implicit-Creation-of-Arrays-and-Structures-from-Form-Fields

It would be really neat to be able to pass arrays and structs based on the input names.

-Dave

Luis Majano

That is very interesting Dave, it could be a great addition to the beanFactory as an implicit manipulation. Maybe a setting in your application that activates complex form fields. Do you think that having a setting to turn this ON/OFF would be a good idea?

Dave

You would need to have a on/off setting I would think or it would break backwards-compatibility. -Dave

Dave

Having had sometime to think on it... I would think that add a new function or argument to the event scope might be better then an on/off setting... Such as: event.getCollection('Implicit') or event.getImplicitCollection that way it wouldn't be an all or nothing thing and you could use it when the situation suited you. -Dave

Site Updates

Entry Comments

Archives

Entries Search