On Thu, 30 Sep 2004 13:48:07 +0200, Michiel Meeuwissen <[EMAIL PROTECTED]> wrote: > Kees Jongenburger wrote: > > > > The biggest problem IMHO at current time is that it's not possible to > > create a class that "implements" a function and register it in mmbase > > Yes, I agree. In my opinion that is not a problem of the frame-work 'an > sich', but of the (6) possible implementation. E.g. you may want to desire > this of 'SetFunction' (which is the most 'simple' one). No , that is not what I mean. the 6 types define way's of defining functions based on where the function is located. I was hoping on types that define how the functions are used -generic function executeFunction(Parameters[]) -function on a node executeFunction(Node,Parameters) -function on a module etc .. -function on a nodetype -function on a fieldtype
Here is examples where a node function should not be implemented in the builder ,email We want to have a function on email to send the email send(oneshot) that function should be implemented in a sendmail modules (we currently have plenty choice) the module once stated should register is't function to the email builder so that i'ts possible to send an email. I think the same story goes for image convert (where we have 2 implementation). and even worse goes for fieldtype , do you want to use delegation for functions like html() or extend fields types form each other?
