On May 28, 2006, at 8:59 PM, Nico Klasens wrote:
My opinion again, it is not only the components method which was
blocking. It is also the blurr around which issues you can solve
with software which is developed by the MMbase community. The
mmbase.org website explains MMbase as a web content management
system, but when you get to know MMbase it is a mature data
management engine with a lot of ways to interact with it. MMbase
solves an issue on a different level then you would expect when you
download it. Magnolia for example is more on the level which is
described on mmbase.org. With all the mmbase binaries you can
create the same thing as Magnolia and much more, but you have to
put some effort in it. I think mmbase as a data management engine
is very good and has many nice features. The taglib is a very nice
addition to it.
It is very confusing to me that two jars (mmbase.jar and mmbase-
taglib.jar) are actually one thing (mmbase?).
Of course I could be wrong on this, because I have never heard
anybody say that mmbase is a data management engine. It could also
be that nobody realized it.
Well its sunday and i think we should be doing something else but if
you view mmbase.jar as mmbase and not the whole distrobution than yes
we are having a different view. When i talk about mmbase i am talking
about all the parts we as a community maintain and the actions that
we take. So taglibs, editwizards, contributions and applications i
all see them as parts of mmbase. And that imho is a good thing but
lets talk about this over a drink tomorow atleast this makes it a
little more clear. When i talk about this project i really mean
extend our reach above the bridge and as a community try to solve
problems that has stopped us sofar from sharing.
Daniel.
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
