On Tue, 2002-07-02 at 09:38, Gerard van Enk wrote: > Why would you wanna move code outside of the builders? Isn't the whole > MMBase idea you can have functionality *inside* the builders? Well, maybe it is time to define what functionality should be where? My opinion is that buildersnodes are somekinda beans. This beans contain information and can do modifcations on that information. Also they can be serialized to the database(or somewhere else) An example could be a virtual field 'age' on a node that contains an birthdate. The problem with beans and image's is that they are now displaying themselve as an image and as an url(generating html code, dependend of the location where the request came from). This is media depended, and the core (read the node) has to know the media where it is working in(how will it work with imode, email? or do we simply -hack- that in later?) I think it is best to move such behaviour to places, where we know more of this information(yeah we could send the request into the core.. but then we make only hack around the problem....)
Personally i find that node's should be very simple and easy to create for everybody, just like beans. Furthermore i am aware that functionality is now in MMObjectBuilders... -- Eduard Witteveen Systeem Ontwikkelaar NOS Internet, Gateway C Kamer 107 +31(0)356772910 http://www.omroep.nl/ Sed quis custodiet ipsos custodes? : The sixth Satire from Juvenal
