| Line | |
|---|
| 1 | gui api design 22.02.2007 -- thu |
|---|
| 2 | |
|---|
| 3 | Tony Sidaway made a uniform gui, level-based proposal. Here are some thought |
|---|
| 4 | about it. |
|---|
| 5 | |
|---|
| 6 | When issuing a widget, it must be possible to make it live in its own top-level |
|---|
| 7 | window or in a sub-window of the current window. |
|---|
| 8 | |
|---|
| 9 | When issuing a widget, it must be possible to have a blocking behaviour or not. |
|---|
| 10 | The non-blocking behaviour needs some kind of callbacks to be passed. |
|---|
| 11 | |
|---|
| 12 | Does the underlying gui code has to be initialized for each widget-issuing |
|---|
| 13 | command or do we provide a 'gui-init' function ? Is it state-based or do we |
|---|
| 14 | pass arguments around ? |
|---|
| 15 | |
|---|
Note: See
TracBrowser
for help on using the repository browser.
