On Jan 24, 2005, at 9:02 PM, Emile wrote:
Hi All
from my perspective mmbase is little more than an abstract framework - not
because of what it delivers (before anyone takes offence), but because of
the way I'm using it. I like the cloud, security, tags, etc, but my needs
are more complex than mmbase can deliver, so I have to build a vertical
framework on top of mmbase - which is a state machine/rules engine
framework, which I then have to build my final application on top of.
To my mind "integration" sounds like more of the same (replacement of
existing functionality), whereas building vertical frameworks on top of what
already exists will be a far better use of time - will also mean that the
core mmbase framework will change less and therefore become a lot more
stable over time. WIAB partly did something along the lines of a
framework - incorporated into the application, but it was built for a
purpose rather than with a generic approach to delivery in mind.
Regards Emile
I agree 100% with your comments, mmbase sofar is a cms toolkit not a cms. The result
is a flexible system for people to build their own frameworks/cms. What is needed is more
ideas on how to create 1 or even better several open finished cms products ontop of the mmbase
core. In my own head ive been starting to call these things profiles.
If we want to grow and imho even safe (sorry i am that negative at the moment) mmbase what is needed
is not only mmbase core but several profile frameworks that are complete cms concepts. For example 1 aimed
at goverment, one aimed at self publishing, one aimed at ....
Daniel.
_______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
