Mercurial > projects > mde

comparison codeDoc/ideas.txt @ 120:46c63cb1c74f

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Ideas for keyboard selection of widgets.
author Diggory Hardy <diggory.hardy@gmail.com>
date Thu, 01 Jan 2009 15:16:00 +0000
parents 1b1e2297e2fc
children d3b2cefd46c9
comparison
equal deleted inserted replaced
119:d28aea50c6da 120:46c63cb1c74f
13 -> decent rendering/theme system 13 -> decent rendering/theme system
14 -> events: 14 -> events:
15 -> Click events: widgets only receive clickEvent for left-button press, other button events handled alternatively from WidgetManager? 15 -> Click events: widgets only receive clickEvent for left-button press, other button events handled alternatively from WidgetManager?
16 -> Click callbacks: replace with "drag callback" notifying widget of release position (and widget)? 16 -> Click callbacks: replace with "drag callback" notifying widget of release position (and widget)?
17 -> possibly better for drag-and drop support 17 -> possibly better for drag-and drop support
18 -> Keyboard widget focus/selection:
19 -> a widget is highlighted
20 -> pressing an arrow key replaces widget with widget.nextInDirection (widget, direction)
21 -> on non-parents, nextInDirection returns parent.nextInDirection (this, direction)
22 -> on parent widgets, if widget is a child and not right against relevent edge,
23 then tries to return next descendant in direction (only non-parent widgets are returned)
24 else does same as non-parent widgets
25 -> some widgets may popup a menu when activated
26 -> caveats:
27 -> all widgets need a highlighted state to show focus
28 -> may require moving through a lot of widgets
29 -> with complicated substructures, may not be very intuitive
30 -> limit to popup menus?
31 -> these keyboard events only passed if activated by code outside the WidgetManager and no text input callback is active?