User talk:Aps/GSoC 2014

From WikiEducator
Jump to: navigation, search


Thread titleRepliesLast modified
Pluggable Rendering Engines?314:38, 20 March 2014
Slide navigation119:05, 18 March 2014
Import from OpenOffice?119:01, 18 March 2014
Reveal.js717:23, 18 March 2014

Pluggable Rendering Engines?

Would it be practical to allow more than one slide rendering engine? (html5slides, reveal, shower, impress, etc.)

JimTittsler (talk)14:46, 18 March 2014

It is possible to use more than one slide rendering engine, but what would be the advantages of that?

Aps (talk)18:59, 18 March 2014

Flexibility is the obvious advantage. It would allow the author to choose their favorite rendering. A particular use case might be an institution that always used impress.js or Flowtime, this would allow a consistent look for slideshows in the wiki.

There should be a generic way of dividing wikitext pages into slides on section boundaries (and failing that, on div boundaries), then each of those "slides" would be rendered as a sequence within the specified engine.

JimTittsler (talk)14:07, 20 March 2014

Ah, I get that. I can do that but what all rendering engines should I include in your opinion?

Thanks for replying.

Aps (talk)14:38, 20 March 2014

Slide navigation

For slides with synchronized audio tracks it must be possible to:

  • advance the slides and have the audio skip to the correct location
  • scrub the audio position, and have the slides resync to the new position
JimTittsler (talk)17:25, 18 March 2014

Yes, these features will be available. They are not currently in the demo, but I will be implementing these during the summer.

Aps (talk)19:05, 18 March 2014

Import from OpenOffice?

Would it be practical to include a way to import an existing slide presentation? Providing at least a "rough draft" import from an open file format (like Open Office) might provide a good authoring starting point for educators that already have presentations in other formats.

JimTittsler (talk)14:48, 18 March 2014

It would be possible to import an existing Open Office presentation but authors would need to save their presentation as HTML. Then it could be parsed to get a draft starting point for the widget.

Aps (talk)19:01, 18 March 2014

I'm curious why you picked Reveal.js for the slide framework.

I've never used Reveal. Does it already have support for an audio track? (And if so, can you advance slides either by clicking the slide or by "scrubbing" the audio position?)

JimTittsler (talk)21:41, 12 March 2014

Reveal.js has a wide range of useful features which include

  • nested slides
  • nice slide tansition customization
  • markdown contents
  • PDF export
  • speaker notes(useful if author is giving a live presentation)
  • a nice API to do things easily

It does have automatic slide transitions at specific interval of time. For linking it with audio position, I'd be using Popcorn.js similar to way its being done in the prototype, but with easy authoring of course.

Aps (talk)21:54, 12 March 2014

Markdown could actually be a disadvantage, since WikiEducator authors are familiar with wikitext.

JimTittsler (talk)22:25, 12 March 2014

Wiki authors don't need to write/read markdown. They would just be using the UI. Reveal.js would be storing the content in markdown format in sub-pages.

Aps (talk)22:29, 12 March 2014

If it is in Markdown format, it won't render correctly on the subpages.

JimTittsler (talk)01:18, 13 March 2014

That's why I said that users won't need to read these subpages. Is there a way we can hide the pages? Or do you know a better way to store this data?

I'm thinking of trying to convert the main page only to a slideshow, but I guess parsing wiki text won't be that easy.

Aps (talk)02:00, 13 March 2014