-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add an anchor system to SuperEditor widget #424
Comments
Another issue I'm having that would need to be addressed by this system is that my toolbar is a bit large and it prevents the user from being able to scroll the document when the mouse is on top of the toolbar. This is because the toolbar isn't actually in the scrollable widget. afaik I don't think it's possible to collect raw scroll information? Another use case is slash commands. For example in Notion, if you type "/h1" a filtered list of blocks shows up and hitting enter will create a new block of that type. |
…hor system for super_editor. (Resolves #424)
…ystem (Resolves #424) - Applied floating cursor expanded selection fix from another PR. Fixed floating cursor auto-scroll bottom boundary position bug. Also debugging a floating cursor document mapping error when moving between nodes. - iOS controls configurability from outside Super Editor - Moving complexity out of IosDocumentTouchInteractor. Currently trying to remove all possible dependencies on the shared and centralized IosDocumentGestureEditingController. All tests pass. - Removed a bunch of unneeded properties from IosDocumentTouchInteractor. All tests pass. - Refactored SuperReader to use new layer controls approach. All tests pass.
…composition (iOS)(Relates to superlistapp#424, superlistapp#893, superlistapp#1166)(Resolves superlistapp#1508) (superlistapp#1470)
It should be easier than it is to display popover toolbars and other overlay anchored items.
Currently, developers need to provide a
ScrollController
toSuperEditor
so that the developer can update the toolbar's location on every frame. This is very tedious and it's likely to fail when there's more separation betweenSuperEditor
and the rest of the app behavior.One idea that I have to deal with this is to pass a map of
DocumentSelection
->LayerLink
. TheSuperEditor
widget can maintain a set of invisibleSizedBox
widgets at the locations and sizes represented by the variousDocumentSelection
s and those boxes can be wrapped in aLinkTarget
.Then, builder widgets could be used to easily anchor other widgets in the overlay.
The text was updated successfully, but these errors were encountered: