tbalouet / aframe-slideshow Goto Github PK

For now transitions are limited to camera motion, it might be good to provider more than a bezier curve path e.g. previous to next slide blending, sound, etc.

Creating a missing #loaderDiv or #camParent errors

Serve the presentation in two different forms: one for the presenter and one for the public.

There should be only one presenter, with all the powers, and the app should supply a link for the public to connect to the presentation, with limited powers.

The public should have real time updates of the scene as the presenter goes through his presentation. It goes for scene updates as well as current slide presented (and therefore the camera position)

As of now the slides are hard links, might be better to have a more dynamic way to link them e.g. passing by URL

• the path (absolute or relative),
• number of slides and
• type of slides (image vs video)

and eventually generate those options by provider only the path (but would require server side processing).

It might be good to consider making a component that doesn't require apainter.

If that's the case it would still be important to at least document the problem we encountered and partly solved namely

• handling the cameras
• conflict with json-model from aframe-extras
• having to include the brush models and thumbnails
• models of the controller relatively linked from the apainter build
• apainter relying on a master build of aframe (0.5.0 of May)

As of now moving from one slide to the next is managed via keyboard (arrow keys) and/or Rift controllers and/or gamepad. It could be good to document that then consider the newer laser-controls

A-Painter shouldn't be part of the main slideshow presentation repo, but should be included in the future for people willing to paint in their presentations.

Therefore we should remove it from the main project. That would also increase readability of the project itself

Enable the presenter to alter the scene in real time:

• through the inspector (already doable)
• by injecting components in the scene (see https://github.com/AdaRoseEdwards work on that) ii
• by integrating CodePen to the scene (embed?)

Currently not defining vidSlidesIndex creates a this.data.vidSlidesIndex is undefined error.

Offline the inspector and the mesh of the controllers for Apainter are not available.

This should either be solved or at least explicit to avoid surprises for future presentations.

When the presenter shares the presentation with the public, this one should be able to interact with the slides.

It could be in the form of 3D models popping in front of the slides when the user tap long on it.

Such limitations should be limited to prevent spam.

Make a feature when adding to the URL "...#X..." would make the camera go directly to said slide