create a common base class for selection events on "list/tree" controls - the
common base class would allow access to the objects directly
------------------------------------------------------------------------------------------------------------------------------------------
Key: PIVOT-525
URL: https://issues.apache.org/jira/browse/PIVOT-525
Project: Pivot
Issue Type: Improvement
Components: wtk
Reporter: Appddevvv
I was writing a treeview adapter for the selection to broadcast it out then I
had to write the same code for the listview. I won't say all applications, but
probably a bunch of applications, would benefit from having the domain objects
directly propagated in the event itself e.g. what domain objects were added or
removed, instead of having to index back into the actual control structure. I
think a common sequence oriented interface underneath the treeview and listview
specific selection event data provides this common approach.
There does not need to be any user level API changes for existing API on this
but creating the event will require different argument parameters when creating
the event itself.
This needs more thought. We need to think about efficiency for really large
selection changes as well e.g. "select all."
This is purely about convenience for event consumers. You can ignore this issue
if you want to until I post some code thoughts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
