Hi John, > 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.
Andi and I discussed a "bequeathTo" mechanism which would be a more declarative (and hopefully less error prone) way of achieving what I think you're looking for in your onValueChanged code. I'm not sure if and where this is on Andi's plate, but if you can use this, that might save you some time. > 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. There's theoretical usefulness to redirect for reminders. I think we backed off from using this in the current reminder code, but it's worth noting that the summary table isn't the only possible consumer of redirect. Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
