|
Hello Daniel, The thing I don't want is limiting the versatile and flexible nature of MMbase. This is a reason we chose MMbase in the first place. We have done many mmbase projects now and asked ourself where the issues in these projects are which limit our productivity. We came to the conclusion that project startup time and re-implementation of functionality are among these issues. We always 'clone' a project which is similar to the new one and bend it until it fits. We don't wamt that. because it always gives a problem later in the process. MMbase is the starting point of our projects. With application functionality you can work on top of MMbase, but this is not an application issue we are dealing with. These are project issues and MMbase does not yet help to solve them. The proposal changes this situation. When only half of what is in the proposal is implemented then we will be a step closer to the solution. The proposal also tries to fill the gaps between several applications which are build on top of MMbase. Some functionaities are re-implemented in these applications. It would be nice to extract those to get robust code, because many people use them. Johannes and I (and others) discussed this and we came to the conclusion that this extraction process could go easier when we add some thing to MMbase .Maybe, Johannes and I got carried away by the idea and added more then is required, but on the other hand it shows how realistic we think it is. I don't think there are 2 views on MMBase. It is more a question: when do you use what in the implementation of an application. In several cases scripting is better suited then java code, but in other cases it is the other way around. I like to use the taglib and jsp to present the content. I don't have to write a lot of custom tags to get it done. Most custom tags are just a replacement when I have to write many lines of jsp code over and over again (jsp tag files are also great for this). When I write business process logic then I like java code more, because you can explain with method names and class structures what you are trying to do. For me it is very important how easy it is to read and understand what code does. Maintainability heavily depends on this. Writing maintainable code in a scripting language is much harder, but not impossible. Nico Daniel Ockeloen wrote:
|
_______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
