You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browserify and server-side file processing will remove most "users" of the experiment cf attempt to import to glitch https://glitch.com/edit/#!/webvrdefender that will be required for end-user who will want to fork the project.
The text was updated successfully, but these errors were encountered:
So yeah, basically we need an architecture with simple HTML file talking to server and importing project files.
Browserify shouldn't be in the Glitch project to simplify usage, but I think we should use it to bundle the different AFrame components, to avoid having to load XXX files.
So we should end up with a glitch in which the html file would fetch the following scripts:
AFrame
WVRD (WebVRDefender) components (bundled)
WVRD script
What do you think? I'm afraid that separating components in different files, event if it simplify readability and access, might slow up load process a lot
Browserify and server-side file processing will remove most "users" of the experiment cf attempt to import to glitch https://glitch.com/edit/#!/webvrdefender that will be required for end-user who will want to fork the project.
The text was updated successfully, but these errors were encountered: