Happy New Year, and v1 roadmap
# webview design proposal and roadmap TLDR: modern C++ as a primary language, no IE, JSON RPC for native function bindings, prebuilt DLLs for Windows, plans for webview org. The goal of the webview project is to create a common HTML5 UI abstraction layer for the most widely used platforms. ## Platforms Supported platforms must include, but not limited to: * Currently supported Ubuntu LTS * Currently supported macOS * Currently supported Windows Support for Android or iOS is still unclear, but might be possible and is highly desirable. The library can be seen as a collection of three types of API: * application (app process and main UI loop) * native window (create/resize/set title/set color/...) * browser engine (open URL, execute JS, call native code JS). For the sake of simplicity and forward-compatibility with mobile platforms, only a single native window per app process is supported. For those, who have more complex use cases and the need of multiple windows there are two options: spawn a process per window and let them talk to each other via IPC, or create an external app loop on your own, then create as many native windows as you need and pass them into webview constructor. Passing a native window handle into webview constructor allows infinite customizations of the window without bloating an API. However, in this the developer is in charge of managing such native windows. The library will only provide an embedded webview widget. With this in mind, the follow
Posted by zserge on Jan 6, 2020, 9:47 AM
Tags
Related issues
- In the UK Amazon have now raised the price of general shipping to be 2/3 the price of a months prime subscription.
- Credit where credit is due, critics claiming "[Apple device] is too expensive for something that just does [basic function]" have been pr...
- I like to buy music.
- Meet K-Claw.
- Fable is way too expensive for basic software stuff.
- [Meta] Abnormal Codex usage/quota depletion and usage-accounting inconsistencies — cross-report tracker
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
pricing (SaaS)
In the UK Amazon have now raised the price of general shipping to be 2/3 the price of a months prime subscription.
Credit where credit is due, critics claiming "[Apple device] is too expensive for something that just does [basic function]" have been pr...
I like to buy music.
Meet K-Claw.
Fable is way too expensive for basic software stuff.
[Meta] Abnormal Codex usage/quota depletion and usage-accounting inconsistencies — cross-report tracker
[FEATURE] Passkey (WebAuthn) sign-in for Claude accounts, across every surface
> How are Chinese companies financing their buildouts of AI infrastructure?
Happy New Year, and v1 roadmap
# webview design proposal and roadmap TLDR: modern C++ as a primary language, no IE, JSON RPC for native function bindings, prebuilt DLLs for Windows, plans for webview org. The goal of the webview project is to create a common HTML5 UI abstraction layer for the most widely used platforms. ## Platforms Supported platforms must include, but not limited to: * Currently supported Ubuntu LTS * Currently supported macOS * Currently supported Windows Support for Android or iOS is still unclear, but might be possible and is highly desirable. The library can be seen as a collection of three types of API: * application (app process and main UI loop) * native window (create/resize/set title/set color/...) * browser engine (open URL, execute JS, call native code JS). For the sake of simplicity and forward-compatibility with mobile platforms, only a single native window per app process is supported. For those, who have more complex use cases and the need of multiple windows there are two options: spawn a process per window and let them talk to each other via IPC, or create an external app loop on your own, then create as many native windows as you need and pass them into webview constructor. Passing a native window handle into webview constructor allows infinite customizations of the window without bloating an API. However, in this the developer is in charge of managing such native windows. The library will only provide an embedded webview widget. With this in mind, the follow
Comments (0)
No comments yet. Start the discussion.