I've been kicking this idea around in my head, and looking at the 0.7
summary-table spec has prompted me to send it to the list...
We've currently got a summary Table implementation based on wx's Grid
mechanism; it provides a framework for presenting a list of items in
rows & columns, with scrolling support, hit testing, etc. It also comes
with some architectural structure (most in my face, the editor/renderer
mechanism) that constrains our implementation a little; our thinking
occasionally stumbles over UI issues like sections, etc, that don't
naturally fall out of using the wx Grid.
In thinking about future needs for the table, it occurred to me that
we've already got the CollectionCanvas that knows how to present items
of varying geometry on a variably-sized canvas with scrolling, dragging,
and hit-testing. It seems like it'd give us more flexibility in evolving
the summary view in the future. (As a bonus, it already uses David's
header widget.)
So: should we think about building the 0.7 summary table on top of
CollectionCanvas instead of the Grid?
...Bryan
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
