I have a script working to generate a basic slideshow from a document of SVG slides (see my converter branch) , but the resulting presentation has meaningless time codes, the demo audio, no transcript and no sub-slides.
There should be some way to add these without using a hypothetical Butter plugin/template.
Sub-slides may be difficult to specify without an interface*, but the others aren't too bad. A command-line tool could import and export time, transcript and audio information between the HTML presentation and a JSON document; an extension of the time code tool I wrote.
After the user made minor changes to a completed presentation they could export the new slides, copy the transcript/times/audio from a previously-completed one and almost be finished.
I'll probably start working on a patch for this.
* Well, I have a thought about how sub-slides could be handled but it's messy and inflexible: allow the user to specify sub-slide-elements based on their text, matched in a case- and whitespace-insensitive manner:
{ "time": 50,
"transcript": "blah blah blah",
"subslides": [
{
"text": "but 95% or more are primarily self-taught",
"time": 53,
"transcript": "...reinvent a lot of wheels... "
}, ...
]
}, ...
This seems likely to break more often than specified by slide index.
I have a script working to generate a basic slideshow from a document of SVG slides (see my
converter
branch) , but the resulting presentation has meaningless time codes, the demo audio, no transcript and no sub-slides.There should be some way to add these without using a hypothetical Butter plugin/template.
Sub-slides may be difficult to specify without an interface*, but the others aren't too bad. A command-line tool could import and export time, transcript and audio information between the HTML presentation and a JSON document; an extension of the time code tool I wrote.
After the user made minor changes to a completed presentation they could export the new slides, copy the transcript/times/audio from a previously-completed one and almost be finished.
I'll probably start working on a patch for this.
* Well, I have a thought about how sub-slides could be handled but it's messy and inflexible: allow the user to specify sub-slide-elements based on their text, matched in a case- and whitespace-insensitive manner:
This seems likely to break more often than specified by slide index.