Skip to content

2024 Wolvic

Jump to bottom Edit New page
Manuel Rego Casasnovas edited this page Jun 11, 2024 · 1 revision

WEH 2024 Wolvic: a browser for WebXR applications

Notes

  • JaviF introduces the breakout session and presents the slides.

  • stephanie: has everybody tried a xr device here

  • room: yes

  • dietrich: how solid is the webxr spec?

  • javiF: pretty solid group, with meta, apple. quite prolific

  • dietrick: what hardware is supported

  • javiF: had a slide, but removed... many hardware. Perhaps this multi platform/hardware capability is one of the strongest point of wolvic

  • links
  • meta's one (oculus)
  • PicoXR very good device plished with good camera quality
  • a few huawei glasses, which are not quite immersive.. What you can see for the different hardware is different, but fine for AR.
  • ???? for engineering

  • alex: question about gaming. not into vr gaming at all, only tried some console in the pasy. In my understanding, the biuggest issue would be loading the content. (transmit the scene, objects, etc). Probably a challenge would be a streaming API

  • javiF: I believe also a challenge for online gaming

  • alex: different, because you've already downloaded all the content, but for webxr you'd transmit the content on the fly.

  • javiF; right now just a page, and very simple so not a challenge. Some of them are very impressive, dark house with things you fear etc but quite static, not a lot of things moving at the same time, works very well. probably the problem is the content creation

  • jacobo: equivalent would be ????

  • sergio: mentiones no man's sky as an example of a game with a data loaded on the fly

  • juanjo mentions dead secrete circle as a game ; and wonderlands as a framework

  • ????: about the weblayer

  • javiF: there used to be a layer on top of chrome, called weblayer, dealing with various stuff (logging, private mode, bookmarks, history, etc) which are just content API in this layer. but that was deprecated, so we could either fork & maintain it but chrome does not commit to maintain the lower API or alternatively implement your own API. doing the latter took more work than expected. Gecko provides all of these functionality in the engine, so easier. for chromium you had to implement much more functionality to get this browser stuff. at the end was not the webxr but the 2D part which caused the delay

  • Piyush: wondering about using webview

  • javiF: don't know exactly the chanllenge maybe, sergio?

  • sergio: need a lower level access to the web engine than any of these standard web views could provide. In wolvic, all the communication with the devices happens via wolvic. We are the ones providing all that info to the browser. He mentioned short memoriation mechanism, we need access to the content API directly. the reason we have that comes from firefox reality, problem is that wolvic is itself a webxr application, we cannot use the engine which would use new XR session, so we need wolvic to do all of that. we are injecting data from hardware to the engine, which require this low-level APIs. but we also need java API for basic things like zooming etc that traditional deskop browsers do.

  • ????: you showed 3 windows at the same time, consider people who have 20 tabs at the same time, solution?

  • javiF: we are actually working on that, providing a concept for that. there is no technical limitations at all, just to find the right concept, this is not trivial. The ones we are exploring right now are similar to traditional browsers, but also think something for the whole-world. How is it confortable for the users though? this is tricky. In meta this is just a rectangular window, so quite disappointing. we try to provide something cooler in wolvic.

  • juanjo: want to clarify that we do suppport tabs, we are working on flexible window layout. a bit complicate because based on firefox reality, will take some time but should be ready in a few years??

  • javiF: another interesting things is the feedbakc we get from our form. one thing is that they really want the browser to be integrated into the system. some better interact with other open applications. but what we provide in wolvic is something stronger / different. let's see, we try to find the right approach

https://www.webengineshackfest.org/

Add a custom sidebar
Clone this wiki locally