Why does LightFront have "Flexible Conventions"? Why should I care?

The concept behind flexible conventions is simple.

Typically, a CFML framework tackles concepts convention vs. configuration with one simple answer.

That's where LightFront is different.

LightFront does not offer a great deal of configuration, but there are some things you must define. It was a conscious decision to define those values in Application.cfc.

I, personally, have spent a great deal of time developing applications on frameworks that offer a great deal of flexibility, through the use of a config file in XML. While this has its advantages, one major disadvantage is the lack of ability to configure actions dynamically. You also have to maintain an XML file.

It's always felt like the XML file has been an extra step. I wanted something simple.

So, "Flexible Conventions"?

Right... Flexible conventions give you the opportunity to define a few key settings in your application. If none has been defined, LightFront sets the value from its default.

For example, you can turn off switch based controllers altogether. You can change the default controller and view locations, as well as default actions, pre-actions and post-actions.

By giving you a little configuration, it makes it possible to "set your own convention".

FAQ

The FAQ's are a work in progress... Some of these may be not found, incomplete or out of date...