honestly i don't know how complex you want to make this. But if we can use the function set code all over the place maybe it's better to use the same code everywere. The problem for me is that i don't know how to use the function set software. Could you provide an example so I can look into loading them from MMObjectBuilder. If this seems to work good we can ask for a vote to get this code into MMBase 1.7.1
Rob
Just to explain my comment to Rob about that there maybe a possible overlap between these 2 ways of defining functions. I look at it from a pragmatic way. In the future we want to be able to 'add' software/functions/actions to several parts of mmbase. This can range from filters to encoders to functions on managers and even instanties of objects. Sofar i have been working with functions as 'sets' because they are somewhat seperated from 1 builder (more model/view/control) so for example the MMBob forum we showed at the last meeting has a 'set' of functions that go with the datamodel (defined in objects and relations). We can see this function set as partof the applications instead of just one builder. It could be a idea to allow these sets to be attached to things. For example function sets we want to use over the whole a whole cloud could be attached to the cloud, functions we want to attach to a applications for general support with a application, functions attached to a builder to solve the above problem and even attach a function in the future to more things like objects themself.
This is a lazy way of adding functions in that it allows someone who didn't make a builder/applications etc etc to add functions anyway without changing the software (that is maintained by someone else) and that _can be_ nice. ofcourse in other cases they should/could just be defined as part of the thing itself (say in this case a builder.xml) since its seen as part of the product not something added by the 'user' of the product at runtime.
To research/allow this all that is needed is that we add hooks toi n this case MMObjectBuilder that allow us to 'load' in with functions at runtime so the place/type where we loaded it from is abstracted.
Hope this makes sense. This italk s all post 1.7.0 related.
Daniel.
