| 26 | | Each Urwid component is loosely coupled and designed to be extended by the user. It may be |
| 27 | | better to think of Urwid as a console user interface construction set than a complete UI |
| 28 | | library like GTK or Qt. |
| | 27 | Each Urwid component is loosely coupled and designed to be extended by the user. |
| | 28 | |
| | 29 | DisplayModules are responsible for accepting user input and converting escape sequences to lists |
| | 30 | of keystrokes and mouse events. They also draw the screen contents and convert attributes used in |
| | 31 | the canvases rendered to the actual colors that appear on screen. |
| | 32 | |
| | 33 | The included widgets are really just examples of what can be done with Urwid. |
| | 34 | It may be helpful to think of Urwid as a console widget construction set rather than a finished UI |
| | 35 | library like GTK or Qt. WidgetMethods describes the widget interface and |
| | 36 | WidgetLayout describes how widgets are nested and arranged on the screen. |
| | 37 | |
| | 38 | Text is the bulk of what will be displayed in any console user interface, and Urwid comes with |
| | 39 | a configurable TextLayout that handles the most of the common alignment and wrapping modes. |
| | 40 | If you need more flexibility you can also write your own text layout classes. |
| | 41 | |
| | 42 | |
| | 43 | |
