exokitxr / exokit-browser Goto Github PK

Support shared WebRTC channels with synced content, and possibly voice chat as well.

Currently the URL bar will by default have https:// in it. The browsers do not do this, but have a blank url bar instead to show the autocomplete search queries. Browsers will automatically add http:// or https:// if they detect a TLD being used

The site appears a bit off on the left of the site placement.

When logging in the email check doesn't accept uppercase emails, nor does the token match handle case sensitivity.

This would be super useful to support.

https://browser.exokit.org/?u=https://swift-empress.glitch.me/

It could simply open the URL in "local" space.

We should fill in OpenGraph/meta description tabs for socials posting.

https://github.com/modulesio/exokit-browser/blob/005ed2e30d78938df5b52aa842fb37a3eedd40d9/index.html#L4

The floor and controllers seem to be about one head-height off the ground.

• remove outdated repo README
• remove api.js
• remove weba files
• remove example sites carried over from engine
• remove unused files carried over from engine/studio/exoland/etc.

Highlight the anchor currently hovered.

We should have only the right gamepad movable by default, with switchability with e.g. Z/C.

There is a flash of the blocker if you delete service worker then load, should style to not be the case

Inspired by

in fact if we make it so simple that nobody noticed the technology I consider that a success

I'm not sure what the way to do it would be, but I wonder what steps to take to make the exokit browser be more seamless/in the background. Initial thought was hiding the navbar since that is only important for:

• logging in
• logging out
• controls dropdown
• recognizing you're at the exokit browser site via the icon/title

Enter pointerlocked mode when intersecting with menu within a close radius to the menu from the front of it.

Not sure if this would make the experience easier, but interacting with the menu is easier from not-pointerlocked mode because you can select the textbox, type on irl keyboard, click between tabs without having to angle everything correctly in 3d space.

Related: exokitxr/exokit-web#88 (comment)

decentraland and google are not currently loadable as they are 2d pages

Related: exokitxr/exokit-web#11

There is already a background for the textbox and 2 buttons.

2d iframes example:

<style type="text/css">
 <!-- BODY {background:none transparent;}-->
 </style>

<iframe src="frame.htm" allowtransparency="true">

(Maybe) should have a chat widget for support calls directly in the site, or something that pipes to Discord.

It is hard to read what URL is associated with a result, I wonder what the sweet spot is between readability of the text and of the content of the URL.

Use alt /ctrl modifiers to change controller axes and sensitivity. Note that browsers hijack certain combos so we don’t get to choose what works and there is a minefiels if unusable keys.

Add GA for login tracking, as well as activity.

This occurs in Hubs and A-Painter.

Add teleport ui in menu based on pad pressing.

Currently these are not passed through the engine.

It still works as expected from the back of the menu, not sure if it should or if it matters.

Should add clickability for reality tabs HUD labels.

Related: #38

Going through GOA portals leads to a location change error:

We just need to handle the navigation of the inner frame correctly.

I'm not sure if this would be a good idea, but thought of if the menu background should be transparent instead of white.

There should be a way to view the keymapping / how to use controls.

Occasionally will be blocked out even if logged in.

Blank screen / not loading from error:

Uncaught (in promise) DOMException: Failed to execute 'define' on 'CustomElementRegistry': the name "xr-site" has already been used with this registry

We should make reality tabs have a "breathing" animation or load progress bar so it's easy to tell things are "working".

The browser xr-scene does not load everytime consistently.

Reality tabs need a HUD for labeling/pointing to where the tabs are, as well as an easy way to move/delete them from XR.

Teleport/xr-offset matrices for child subtabs should transitively apply the parent transforms; they currently do not.

Related: #33

Someone suggested during user testing to have more responsive affordances like to enlarge the rayMesh's dotMesh when intersecting with clickable menu items, etc.

Related to #36, the right controller is the only controller with selecting ability, so we should only display the ray from the right controller to not confuse users.

Uncaught TypeError: e.get(...).vertexAttribDivisorANGLE is not a function

Full log:

I think people would rather use the IRL keyboard vs the virtual keyboard when in 2d-mode. In 2d-mode, since the virtual keyboard is unused, it ends up blocking parts of the menu.

Qwertasdf tab

Should the menu billboard/always face the user?

We could display the controls like the left side HUD.

So we can copy paste from Exokit Web Viewer.

Support Ctrl-C/Ctrl-V.

The whole screen mesh rig should bob when logged out.

https://www.jorgefuentes.net/projects/halloVReen/

These buttons are not clickable unless not pointerlocked, should they be visible when pointerlocked?