comparison codeDoc/ideas.txt @ 151:e785e98d3b78

Updated for compatibility with tango 0.99.8.
author Diggory Hardy <diggory.hardy@gmail.com>
date Sat, 04 Apr 2009 17:32:18 +0200
parents 1125ba603af6
children b06b04c75e86
comparison
equal deleted inserted replaced
150:42fb97d9ff9e 151:e785e98d3b78
27 -> all widgets need a highlighted state to show focus 27 -> all widgets need a highlighted state to show focus
28 -> may require moving through a lot of widgets 28 -> may require moving through a lot of widgets
29 -> with complicated substructures, may not be very intuitive 29 -> with complicated substructures, may not be very intuitive
30 -> limit to popup menus? 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 31 -> these keyboard events only passed if activated by code outside the WidgetManager and no text input callback is active
32 > Drawing windows/popups (to draw a back):
33 -> Use the same renderer & manager:
34 -> Make all widgets draw a back?
35 -> bad for transparancy and performance
36 -> Force first widget to draw a back
37 -> extra parameter to pass in special cases
38 > Use a sub-renderer
39 -> extra parameter to pass
40 -> or some kind of lookup by mgr
41 +> enables nice transparancy
42 +> Use a sub-manager
43 +> holds a sub-renderer or something
44 +> enables nice transparancy
45 ?> integrates with popup support? will this work?
46 > each floating/popup widget has its own renderer (last two above)
47 +> combined rendering (to texture?) of each "layer" to enable nice transparancy
48 > lower performance?
49
32 50
33 Content: 51 Content:
34 -> Per-content undo support? 52 -> Per-content undo support?
35 > Services: 53 > Services:
36 > All content: 54 > All content: