Both S5 and Slidy presentation is a single XHTML file and they have a set of markups which is then used by the javascript to show the presentation. If we decide on one of the markup, converting to other won't be a problem by a simple script.
And later, if Google Presentation API allows XHTML conversions(Save as HTML), which I kind-of think they will, we would be able to use our code for it also just with few additions. Or we could generate code in WIKI markup from the GUI interface which can then be used to convert in S5 or Slidy's format. On Fri, Jun 6, 2008 at 12:35 PM, Vincent Massol <[EMAIL PROTECTED]> wrote: > > On Jun 6, 2008, at 7:04 AM, Arpit Jain wrote: > > [snip] > >>> > >> 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. > > > > > > I looked for Google Presentation API and I couldn't find them. > > Google have > > APIs for spreadsheets and for Google Data in general, but I couldn't > > find > > anything related to Presentation. Can you please help me on that? > > They probably don't exist then...(I couldn't find them in > http://code.google.com/more/#products-apis-documents) > They probably will exist in some future. > > The point remains valid though. > > Thanks > -Vincent > > > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > -- Arpit Jain Senior Undergraduate Student Department of Computer Science & Engineering Indian Institute of Technology, Kharagpur, India. Web: http://www.arpitjain.com _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
