Here's an idea: we actually pass around self.selection in
event.arguments, (or the selection you'll be managing in the new
indexed collections you're talking about) rather than creating a
separate list?
Alec
John Anderson wrote:
I'm not sure this will scale to the selection in the All collection
when you select all.
Alec Flett wrote:
In the interest of supporting multiple selection in the calendar, I'd
like to change the SelectItemBroadcast CPIA event to pass around a list
of items, rather than just a single item.
Here are a few implications I can see right now:
1) all of the onSelectItemEvent implementations, the method typically
called when this event fires, will have to deal with an updated version
of event.arguments['item'] - I figured I would actually change this
method name to onSelectItemsEvent, and make the argument
event.arguments['items']
2) there seems to be some tie to onModifyContentsEvent, that will have
to be untangled
3) The detail view will have to know that when it gets called with
multiple items, that this is equivalent to dealing with no items, at
least for 0.6
4) Instead of allowing "None" to be passed as event.arguments['items'],
I'd change the policy so that you pass around an empty list if there is
no selection
I'll take care of all the above, but I wanted to know if anyone had any
specific issues with the above, or have any other issues with this
change...
Alec
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
|
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
