Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid server-side file processing #1

Open
Utopiah opened this issue Sep 8, 2017 · 1 comment
Open

Avoid server-side file processing #1

Utopiah opened this issue Sep 8, 2017 · 1 comment
Assignees

Comments

@Utopiah
Copy link
Collaborator

Utopiah commented Sep 8, 2017

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.

@tbalouet
Copy link
Owner

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants