reposted it myself since i made even more language mistakes the normal sorry :)
-------------

We don't want to change MMbase to fit the cmsc. We also don't want to change the way you can develop with MMbase. We are only suprised that you can more easily develop with the taglib then with the bridge.

Thanks for the reply Nico, i will have to read it a few more times to let it all sink in maybe ill reply a second time but this line stood out to me and
i wanted to make a point and  question about it.

First the fear of not adding some rules to how to use MMBase (the principles and reason for components) resulted in a flexible product but
also had the result that allmost nothing above the bridge was shared or shareable. This effort is all about us the mmbase developers starting to
add rules (or atleast guidelines) on how to use MMBase. And we are hitting a topic that has been hidden (or we didn't want to admit it) for a few years  now and this comment points to that i think.

I like the fact that the proposal is make components that are shareable over mutliple frameworks and they can themselfs be implemented in several ways because i think there are 2 main ways people use/see mmbase :

1) We make easer scripting tools so that others can make websites with it. taglibs/functions,objectbuilders, defining all in xml instead of sql or java code are examples of this. Its felt dat non java programmers should be able to make or atleast change the products created with it.

2) All should be made by writing in java (or as you say talk to the bridge) this means there are no 'tool' builders but graphics designers and java programmers who make the needed code/interaction where configuration creates the wanted flexibility.

Is this a valid view ? and a correct way to explain it to managers ?

Now your proposal's main point is we might not be able to share frameworksn based on these 2 models and we might not even implement the components made for these frameworks in the same way but by adding a few interface concepts we can atleast demand they are shareable  and if we make them configurable very useable in all the frameworks.

Is this a fair view ?

Daniel.
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers

Reply via email to