|
02:03
japhb left
02:20
japhb joined
|
|||
| patrickb | Architectural question: I need a static rich text widget. I.e. non-focusable, non-scrollable. Pretty much what PlainText does, but with RichText support. | 13:08 | |
| I tried stripping down Viewer::RichText, but that gets ugly when trying to disable scrolling and focusing. | 13:09 | ||
| I tried adding rich text support to the PlainText widget (or create a copy named "RichText"). But PlainText does have support for wrapping, replicating that would duplicate the better part of WrappableBuffer. | 13:11 | ||
| I then tried to have PlainText inherit from WrappableBuffer. That is difficult, as WrappableBuffer not only provides Wrapping, but also the concept of a cursor. I'm unsure how difficult it would be to pull the concepts of "put wrapped rich text on the screen" and "maintain a cursor including highlighting on some text" apart. | 13:15 | ||
| My feeling is that ideally we should have rich text support everywhere. If so, then having the ability to easily wrap a piece of rich text is valuable to have. Thus we should indeed separate RichText processing and cursor management. | 13:18 | ||
| But ugh, that will be a chunk of work... | |||
| Geth | Terminal-Widgets: patrickbkr++ created pull request #58: Input::Text: Implement &process-change to allow reacting to text changes |
14:14 | |
| Terminal-Widgets: patrickbkr++ created pull request #59: Implement TW::RichText |
14:17 | ||