Planned VersoView APIs

[Legend-Master]

One way commands

• Navigate Initial effort to use IPC calls to control verso #207
• Resize and change the position of the window Expand VersoView to include more APIs #275
• Other commonly used window methods (e.g. set maximized, is minimized, ...) Expand VersoView to include more APIs #275
• Focus the window Add focus() and reload() to Versoview API #302 (moved to https://gitlab.com/verso-browser/verso/-/merge_requests/329)
• Change the zoom factor
• Reload the page Add focus() and reload() to Versoview API #302 (moved to https://gitlab.com/verso-browser/verso/-/merge_requests/329)

Listeners and handlers

• Navigation events
  • Navigation starting, also allow controlling whether or not the navigation is allowed Allow using IPC to handle navigations #222
  • Navigation completed
  • History changed
• Allow registering custom protocols? Expand VersoView to include more APIs #275 (implemented with on_web_resource_requested)
• Gain and loose focus events?
• Zoom factor changed?
• Document title changed?

Other related PRs:

• Expand VersoView to include more APIs #275
• Refactor config to allow setting it through IPC #290
• Support running getters on multiple threads at the same time #297
• Introduce VersoBuilder for more stable controller creation #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