feat(scrollable): make Container scrollable through Element Scrollable
All checks were successful
Zig Project Action / Lint, Spell-check and test zig project (push) Successful in 1m35s
All checks were successful
Zig Project Action / Lint, Spell-check and test zig project (push) Successful in 1m35s
This commit is contained in:
25
README.md
25
README.md
@@ -93,22 +93,25 @@ the primary use-case for myself to create this library in the first place.
|
||||
- [x] separators
|
||||
- [x] Rectangle
|
||||
- [ ] User control
|
||||
- [x] event handling
|
||||
- [x] event loop handling
|
||||
- [x] mouse support
|
||||
- [x] user content
|
||||
- [ ] Default `Element` implementations
|
||||
- [ ] Scrollable
|
||||
- [ ] user input handling
|
||||
- [ ] vertical
|
||||
- [ ] horizontal
|
||||
- [x] user input handling
|
||||
- [x] vertical
|
||||
- [x] horizontal
|
||||
- [x] mouse input
|
||||
- [ ] scroll bar(s) rendering
|
||||
- [ ] vertical
|
||||
- [ ] horizontal
|
||||
- [ ] Content alignment (i.e. standard calculations done with the provided `Size`)
|
||||
- [ ] Text display
|
||||
- [ ] User input
|
||||
- [ ] single line
|
||||
- [ ] multi line
|
||||
- [ ] min size? (I don't have access to the `.resize` `Event`..)
|
||||
- [x] User input
|
||||
- [x] single line
|
||||
- [x] multi line
|
||||
- [x] min size (provide size to use which would be a minimal size - as if the actual size is smaller then the `Container` will scroll and otherwise the contents expand to the available space instead?)
|
||||
- [ ] image support through kitty protocol
|
||||
|
||||
Decorations should respect the layout and the viewport accordingly. This means
|
||||
that scrollbars are always visible (except there is no need to have a scrollbar)
|
||||
@@ -117,6 +120,12 @@ cells of the content (and may be overwritten by child elements contents).
|
||||
The border of an element should be around independent of the scrolling of the
|
||||
contents, just like padding.
|
||||
|
||||
For most of the `Element`s a standalone implementation would not make a lot
|
||||
of sense due to the complexity of the user application states. Therefore the
|
||||
library should instead provide small examples to show how you can implement
|
||||
such user fields yourself and connect them using your own event system loops to
|
||||
communicate with other `Container`s and/or `Element`s.
|
||||
|
||||
### Scrollable contents
|
||||
|
||||
Contents that is scrollable should be done *virtually* through the contents of
|
||||
|
||||
Reference in New Issue
Block a user