Ideas for 3.2
Oscar Arevalo
The latest update (3.1.570) will be the last on the 3.1.x branch since
I want to start moving with the 3.2. So far the main features I have
planned for the new version are:
- Move from LGPL to Apache license. Although in theory I liked the
LGPL idea, I think that in reality it limits more the adoption of a
small project rather than protect it. I want to move to Apache since
it removes most of the strict restrictions of the GPL-mindset while
still maintaining an open-source nature. If anyone has comments on
this, please let me know. I'm not a lawyer and the whole open source
licensing stuff is really convoluted.
- Replace/update the Resource Libraries implementation. Lately I've
been doing more and more commercial projects based in HomePortals and
have found that the current resource libraries implementation is not
strong enough for real-world usage. I've been thinking on moving to a
full tree data structure, with unlimited levels and nodes; instead of
the current type/package/node fixed structure. Also, the database
integration REALLY needs to be addressed; its nice to get up and
running without having to worry about setting up a database, but for
real-word stuff, that is not enough.
- Implement resource management as a plugin instead of as a core
feature. I've realized that the strength of HomePortals is in its
rendering and layout capabilities, and in providing an extensible
platform for displaying websites in a modular fashion. Having resource
management embedded as a core feature I think just makes it harder for
HomePortals to specialize on a specific feature and just be good at
that. Also, the plugin architecture has showed that is very capable
for adding non-core functionality to the platform, so I think moving
resource management to a plugin will not be a problem.
Well, if anyone wants to give some input or wants to request a
feature, please do so by all means.
Take care,
Oscar