Closed danschwarz closed 1 year ago
Thanks for the request.
As i mentioned here, it will take one or two releases before this happens.
It's not that I can't release the widget now but for the following reason, I don't want to.
In my TUI, I implemented mechanisms to render images asynchronously (using a mixture of multithreading and multiprocessing). I plan to implement these mechanisms as classes in the library first.
Without asynchronous rendering, the widget will be of little or no use... rendering images will delay UI updates, input processing, etc.
What do you think?
Thinking about it again... it wouldn't actually do any harm releasing the widget now and then releasing the asynchronous rendering as an improvement later on.
This, I can do before the next release.
I forgot to mention that SIXEL support isn't available yet... I intend to work on it towards the release after the next.
I just checked back here now and noticed you mentioned the GridListBox
widget. Thinking about it now, I have a few concerns:
GridFlow
widget and purges out the contents of its underlying pile into a ListBox
, using some of the private interface of the widgets. The square-shaped LineBox
you see within the grid is another widget LineSquare
which monkey-patches the wrapped widget of a LineBox
with another widget LineSquareMiddleColumns
.You're free to reuse and modify the code in another project if needed but I should note that if I were to re-implement the widget(s) today, I'd do them differently.
I think several widgets would be helpful to have available for reuse elsewhere: