>
>
> MMObjectBuilder being the base class of all objects does in the current
> situation already get a signal for all node changes. If a people node is
> changed, MMObjectBuilder, being the parent of the People builder,
> does already gets a notification. Your proposal would mean it would get
> it twice, once with builder param People and once with builder Param
> MMObject?
>
Nope, this is not the problem.
If an audiofragment changes the MMObjectBuilder of the audiofragment
builder gets a signal. That is how it is currently working and that is
good. But if the an audiofragment builder is extending a mediafragment
builder the mediafragment builder should also get a signal.
e.g. If you use an addObserver("mediafragment", this), you want to
receive signals if audiofragments are changing, because an audiofragment
is a mediafragment. This also counts for listings, if you create a list
for all mediafragments you also want to see all audiofragments. The
builder that is receiving the signal (what is currently working
correctly) should pass the signal also to its parentBuilders
(parentBuilder is MMBase1.6).
If you disagree i will invite you on irc, otherwise we will keep on
mailing.
greetings Rob
