Tutorial Maker updates

[Cthomp7]

Below is a list of issues/ideas after our live demo meeting:

• If people have a webm video have an easy place to learn how they can convert that to an mp4. Maybe through the new docs their can be a link to that specific section or is their a document online that we can reference?

• Have it where when a widget is updated it also updates it's size and placement so everything about the widget is saved not just it's content and data.

• A way to notify users that they have unsaved changes and that they should update their keyframe. Maybe a small popup next to the update button like "unsaved changes".

  • Similar to this, it might be helpful to detect when there has been changes made to the netnet code editor and make sure users don't forgot to check the "include code" checkbox. Both of these seem easily forgotten when you are in the flow of tutorial making.

• It would be nice if we could have it autocomplete filenames/directories.

• Chris asked if there was a way in which people could just upload an audio file. I think this brings up a good point since not everyone always wants to film themselves. Audio files still have a duration the only thing is we would probably still want HVP for the audio to be played back and forth and also potentially display subtitles for accessibility.

• Allowing people to upload subtitles to tutorials (STL files)

• Allowing users to be able to move their existing keyframes. We could re-implement the physical inputs of the keyframes timestamp. However, maybe this can be opened up and not always in the view?

• A way to slow down the video's playback speed so that people can easily place their keyframes down.

Overall, I think there are aspects of the tutorial maker that make it feel like the user is fighting against the widget rather than working fluidly with it to create a tutorial. I also don't feel like a user should have to become knowledgeable about the inner-workings of the widgets to understand how to use it. For example, the difference between saving a widgets content and it's placement/size. However for users trying to get into the more complicated things like the init functionality then I think this is fine to be less intuitive