forked from joejulian/gio
8af4472672772c3b779c050d3830ec6424b01fa9
The majority of scrolling happens by manipulating the index of the first displayed item instead of by just manipulating the offset. This lets us avoid having to render all items that were scrolled past. Instead of numbers of items we could've accepted a ratio in [0, 1] to scroll by or to, to match the data we get from scrollbars. However, there are more use cases for scrolling by items, such as keyboard shortcuts, go-to dialogs, etc. And converting from [0, 1] to items is trivial for the user as long as they know the number of items, and will usually be handled for them by a theme. Signed-off-by: Dominik Honnef <dominik@honnef.co>
Gio - https://gioui.org
Immediate mode GUI programs in Go for Android, iOS, macOS, Linux, FreeBSD, OpenBSD, Windows, and WebAssembly (experimental).
Installation, examples, documentation
Go to gioui.org.
Issues
File bugs and TODOs through the issue tracker or send an email to ~eliasnaur/gio@todo.sr.ht. For general discussion, use the mailing list: ~eliasnaur/gio@lists.sr.ht.
Contributing
Post discussion to the mailing list and patches to gio-patches. No Sourcehut account is required and you can post without being subscribed.
See the contribution guide for more details.
An official GitHub mirror is available.
Description
Languages
Go
89.6%
C
7%
Java
1.7%
Objective-C
1.6%