The State of Reflex

Yesterday I got a nice, simple, and direct question in may mailbox: “How goes work on Reflex?” The answer is that it’s taking more time than I expected (it’s not the first time I say that obviously). But it’s also going to be something great when it goes out.

What’s happening is that I’m currently building the administrative interface, and it forces me to rethink one by one many things of the underlying system. The interesting thing is that the admin interface will be made from same template system you’ll use to build pages of your Reflex-powered website, which imply that it will be easy to make forms on any page that can create or edit parts of your website. It’s a little tricky to get everything work right, but I’ll get to it eventually.

To those who fear that I’m mixing the application logic with the display logic by putting everything in the template, don’t worry: it’s not the case. The template only choose the logic to use on a page (like which button performs which action), while the framework or modules define the action (with some PHP code).

This makes Reflex a mix between a traditional CMS (where you manage the content, and the logic is all decided for you) and a web application framework (where you write both the application logic and the pages).