Yesterday I committed release 36 to the SVN. Since release 32 there have been some really minor improvements to the framework but there’s a lot of work to do in many areas. Still, the whole thing is now working “quite well”¹ so I’m thinking of making a clean list of things to be done. I’ll publish it in the next few days so if anybody feels like giving love to someone, Origami would be a nice candidate :)

Both as a side project and a proof of concept, I’m working on a CMS (called Aroo) which is not yet public but it will be in some months. I’ll be more explicit in the future. But for now, long live Origami.

1. As in “if you know the oddities, you know how to avoid them”. [↩]

There’s something in the air. And in Revision 32 too!

At this very moment I’m a bit tired and in these weeks I’m busy for work and study. But still I’m working on taking good ideas, bringing pieces together and try to understand why I felt so wrong working with other (even more complete and powerful) frameworks¹.

Revision 32 is a really good point to begin with looking at Origami and I’ll try to write some guides in the following days. For now just go and see the code. It may seem a bit messy but I tried my best to write useful comments.

1. Other than «not written by me», of course :) [↩]

After some months off the project, here I am back at coding. Origami’s architecture has been modified quite a bit and now I’m working on the refactoring.

This will include the deletion of the current SVN trunk branch in the next days and soon the new Origami Framework will see the light.

EDIT: The development took some exciting directions in the past few days. I’ll try to complete the sketch in the following days and then something will be released before the end of September.

Welcome to the Origami Framework development blog¹ and web site. Here you can follow the development process and look for help both as a user and as a developer.

So let the dice rolling and get back to work.

1. nope, it is not (yet) built with Origami [↩]