On Oct 5, 2005, at 08:57, Alec Flett wrote:
...
For example, Jeffrey's recurrence dialog has to be hooked up when
we change attributes of an item. So to use the delegate, it seems
like we'd have to add code to Table to delegate attribute setting,
and then add code tot he chandler-specific delegate to hook up the
recurrence dialog. If we just derive from Table (or contain it)
then the complexity falls almost entirely to the subclass of Table.
One way to remove this dependency is to add a getEditingItem() method
to Item (which would return self), override it in CalendarEventMixin
to return the proxy, and have the Table code call the method.
As an aside, it's unclear to me why we need the proxy in
GridCellAttributeRenderer.Draw. Are we really about to change an
event's attributes just by drawing it?
--Grant
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
