17 Jun
2008
17 Jun
'08
3:45 p.m.
Hi,
Sorry for the late reply. See below:
I agree, and ideally I think the presentation (or "slide management") part
of the application (create slides, move/organize slides in a presentation,
etc.) should be isolated from any slide implementation (and even slide
interface) so that we can manage virtually any type of slide, amongst
which
* Javascript (typically Slidy or S5) slides
* Wiki content slides
* Images slides
* Flash slides
* etc.
This will be the very "XWiki" part of the application which will require
the definition of a slide XWiki class, and implementing presentations as
collections of wiki documents that contains slide objects (+ one of the
many possible implementation of a slide).
WDYT ?
Jérôme.
I think Slidy
and S5 are our best bet and we should choose one of
them and
start working. And they contain most of the features that a "Simple"
presentation requires.
Also, both of them use similar markups, therefore, modifying the Slide
Generator code(which I would be writing) for the other one won't be
that
difficult.
What say?
Yes, we should have an interface to isolate us from either S5 or Slidy
so that we don't don't have a single dependency on it in our code
(beyond the interface implementation).
It would be cool if this interface could also be implemented using
Google Presentation API for example.
Thanks
-Vincent