John Anderson wrote:
I'm planning on getting rid of redirect attributes to handle the Who,
About and Date attributes in the Summary Table. Instead I plan to add
an explicit Who, About and Date attribute. By noticing when attributes
that affect the value of Who, About or Date change (using
onValueChanged), I'll update Who, About and Date as necessary.
This is simple to implement and eliminates the current problem where
Who, About and Date sometimes doesn't display the correct value. It
also doesn't require a special "computed attribute" that isn't stored
in the repository, so you can always search for Who, About and Date
like any other attribute. Finally, it allows Andi to get rid of
redirect, which simplifies the repository design.
I think we need to take a step back here and really nail down how the
end-user design ought to work. Then we can figure out what the right
thing to do at the implementation level(s) ought to be.
Ted
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
