mod(roadmap): adding new sub-goals

2025-07-15 22:52:50 +02:00
parent 8a24f23e4d
commit 271a1e8516

@@ -63,6 +63,7 @@ The following list contains goals for certain features the library supports or i
- [x] Progressbar
- [ ] Form
- [ ] basic
- [ ] Figure out input handling (apart from mouse `Event`'s such that they do not intersect and are easy to see - i.e. which form element is currently *active*?)
- [ ] Text Input field
- [x] custom (see example)
- [x] built-in single line
@@ -77,6 +78,7 @@ The following list contains goals for certain features the library supports or i
- [ ] Dialog
- [ ] based upon `Popup`'s implementation to switch the dialog pages that are linked in an ordered list?
- [ ] use `Button`'s to make go to the next / previous dialog pages
- [ ] use internal events that are not necessary to be listed in the `App.Event`?
- [x] Scrollable Content (i.e. show long text of an except of something and other smaller `Container`)
- [x] min size
- [x] mouse scrolling aware of mouse position (i.e. through multiple different scrollable `Container`)
@@ -122,6 +124,7 @@ The following list contains goals for certain features the library supports or i
- [ ] *gap* of `Container` (i.e. by coloring the background? **later**)
- [ ] `Element` extensions:
- [x] `Element` implementations can link to a given event, tagged union variation to trigger events or listen to!
- provide a reference to the parent `Container` of a given `Element`
-> allow changing the parent's *properties* through an `Element` implementation (i.e. change the color of the border, add a new child element, etc.) if necessary! otherwise I would rather have this be very independent of its parent (and where it is used or rendered!)