Planned VersoView APIs

[Legend-Master]

One way commands

• [x] Navigate #207
• [x] Resize and change the position of the window #275
• [x] Other commonly used window methods (e.g. set maximized, is minimized, ...) #275
• [x] Focus the window #302 (moved to https://gitlab.com/verso-browser/verso/-/merge_requests/329)
• [ ] Change the zoom factor
• [x] Reload the page #302 (moved to https://gitlab.com/verso-browser/verso/-/merge_requests/329)

Listeners and handlers

• [ ] Navigation events
  • [x] Navigation starting, also allow controlling whether or not the navigation is allowed #222
  • [ ] Navigation completed
  • [ ] History changed
• [x] Allow registering custom protocols? #275 (implemented with on_web_resource_requested)
• [ ] Gain and loose focus events?
• [ ] Zoom factor changed?
• [ ] Document title changed?

Other related PRs:

• [x] #275
• [x] #290
• [x] #297
• [x] #298

[niutech]

How does VersoView API relate to servo's WebView API and another Embedding API?

[Legend-Master]

Biggest difference is verso APIs are way easier to use, and the hope is to make things easier so people will actually start using it

You can see the difference immediately from the minimal examples (also please note that the servo example isn't even fully functional)

https://github.com/servo/servo/blob/main/components/servo/examples/winit_minimal.rs https://github.com/versotile-org/verso/blob/main/verso/src/main.rs