oxide team mailing list archive
-
oxide team
-
Mailing list archive
-
Message #00152
Oxide call notes - 5 September 2016
*1. Release Roadmap*
- 1.16.10 - last stable release update with canvas2d reg. fix & SIGILL
crasher fix on Y
- 1.17.6 - next stable release build, uploaded to silo-1919 (!)
- 1.17 to become stable in about 2 weeks
- Note: amd64 build issue to to linker running out of memory; turns out
we're only getting 4G on LP builders now
*2. Features & Bugs*
- API discussion / Chris's guidelines
- Oxide should control rendering / layout / behavior "details" of the
webview, connected to a system API to update on the fly
- Apps may want to adapt as well, for example to change the UA or
force a reload; but that's a different level
- => better NOT have an API to inform Oxide, from the app, about form
factor changes
- Related bugs:
- https://bugs.launchpad.net/mir/+bug/1610929 - Implement
Screen::GetShellMode()
- https://bugs.launchpad.net/mir/+bug/1556142 - Changing scale,
formFactor or DPI in display configuration causes renderer
teardown/recreate unnecessarily
- https://bugs.launchpad.net/oxide/+bug/1545088 -
- Google search page is scaled on window resize Edit
- Next step: can probably use the new implementation in qsysteminfo to
infer the form factor and screen caps needed for that use-case
- Chris / Santosh will use inside Oxide, eg for switching the
scrollbar rendering
- Alex to try in webapp-container as well
*3. Other topics*
- Oxide in a snappy world (continued)
- Comparison w/Electron : aimed at different targets - Oxide is a
Webview and QML API, Brightray is low-level, while Electron is
for wrapping
sites into desktop apps
- How can snaps "see" the system Oxide to avoid embedding it by
default?