Incremental update released: Added "Start presentation" and "End presentation" buttons to make it more obvious that there is a different view mode; added %SLIDENAVFIRST%, %SLIDENAVPREV%, %SLIDENAVNEXT% template keywords.

Excellent work and fully in the sense of wikiwiki ! I would recommend to add the parameter ?skin=print&... as first one to the Button rendering in sub renderSlideNav to enforce the slide effect also for sites using FlexibleSkin (or other skins)

Very nice.Could it be arranged for each slide to be exactly one screen away from the previous one, so presenters can use Page Up/Page Down to navigate? That would make it about as easy to use as PPT when presenting. Not sure how, I guess that needs some CSS?

I do a fair number of lunch and learns, and I always hated typing comments into the powerpoint presentation (have to go to another screen etc). Because of this people trying to use my on-line lunch and learn slides (hosted in twiki of course), missed out on a lot of supporting/clarifying talk that wasn't present in the powerpoint presentation.

One thing I would like to see in the slide show plugin is a way to start/end commentary between slides. It wouldn't show during the presentation (or maybe it would if a urlparam show commentary was set). This would let me write my slides and commentary in line with the slides where the commentary will do the most good.

Also I noticed that the table definition use 720 as the width. Is there a problem with letting the slide use 100% of the width of the screen (useful for full screen presentations). Using 100% of the height would be great too, but I am not sure what the HTML would be to do that.

A comment section starts now with a ---+++ Comments heading, and ends where the next slide starts. The heading level should be one or more level lower then the slide heading level. There is a HIDECOMMENTS setting where you can define if comments are shown in the slides or not.

I was trying to promote Twiki some more as a tool for collaboration on presentations. I tried to save presentation from page SlideShowPlugin as a local HTML page to be able to view/present it off-line. I found out that previous/next links in anchors are not relative, and I'll get to online version again. Is it possible to create relative links, and be able to save presentation as a page? It will be really cool!

...I added a table around the TEXTAREA which is height=80% width=99%, and then the textarea is set to height:100%;width:100% in a style. ...

In order to do any of this, you need to REMOVE the XHTML DTD specification from the htmldoctype macro in twiki.tmpl. It seems that HTML-3/4 changed the rules for percentage based heights. In order to get reasonable behavior, you have to let the browser stay in "compatibility" rendering mode by leaving out the DTD specification.

Can the removal of the XHTML DTD be done by using a specific template/skin for viewing the slide show?

After looking at http://www.siteexperts.com/tips/html/ts07/page1.asp I came up with this HTML that when refered to using the #top link will display the table filing the display area size (even with the browser in fullscreen mode) and not show the lines of text before or after the table. I used the following browsers:

opera 7

worked, but had to refresh the display when switching from regular to full screen mode.

opera 6

worked

mozilla 1.4b

worked

IE 5.5

worked

slimbrowser 3.53

worked

amaya 7.2

didn't work. Not even when I told amaya to interpret as html 4 transitional.

Problem Statement

You would like to include a Start Slideshow button in a topic page, but don't want that page to include the actual slideshow contents. Personally I think the raw slideshow content looks ugly on the page where it's to be viewed. I'd much rather have the content off on some other page, and just have a button on the kick-off page. In addition, it would be nice if the slideshow is presented in its own little window - kind of like its own application.

Solution

Embed a little bit of Javascript and a form in your page to reference slideshow content from another page.

I think skin=slideshow is more logical for something mostly used on screen. And I need to put the css somewhere. I will attach my template as soon as I have ironed out the formatting.

This makes it impossible to use a skin: if I have a template file the skin is simply ignored. I propose to use the SKIN variable when skin=slideshow is called. So if I have set SKIN to 'pattern', skin=pattern.slideshow is called. See attached patch.

Analogous to pattern skin, the css can be set to a topic. This makes it easy to change width and height.

Line 141, $slideText =~ s/%SLIDETEXT%/$slideBody/go; needs an extra newline: $slideText =~ s/%SLIDETEXT%/$slideBody\n/go;, otherwise bullet lists are not closed properly. Of course I can add an empty line to the template, but this is not neat.

For a css layout, it is easier to also have a SLIDECOMMENT variable. So line 151 changes from $text .= "\n$slideComment\n\n" if( $slideComment ); to $text =~ s/%SLIDECOMMENT%/\n$slideComment\n/go;

Skin support: I need to investigate. Looks like it should be done conditionally, enabled with a Plugin setting.

Extra line in $slideBody: I do not think this is needed; the rendering could introduce an extra p tag. The example slideshow with bullets works. Make sure to have now leading spaces following %SLIDETEXT%

I created a Opera Show CSS style for use with our Cairo Wiki. In contrast to Eric Myer's solution it is not portable to the other browsers of course but it still saves me from having to create content both for the wiki and powerpoint.

I've attached a tarred/gzipped collection of all the files (S5.tgz). Use at your own risk. I've never done this before, so it would be good if someone could sanity check the files. Note that it overwrites SlideShowPlugin.pm (so make a backup of the old version).

Has the S5 stuff been updated for TWiki4? Or rather, has someone or is there another area for it? I really like the S5 slideshow, but it almost seems as if it should be its own plugin, rather an an add on here.

Bug: When transitioning between slides, and when starting up the slide show, the plugin ignores any URL parameters that might have been applied. If that parameter is essential in making the slide show work, you are out of luck.

Here is an example use case: I have a generic presentation for project reviews. It consists of a set of standard slides, which are instantiated by specific project data based on a URL parameter which gives the name of the project. But this parameter is lost.

This is the same issue that I fixed a little while ago with the printable mode which also lost all the URL parameters passed.

I use this style a lot: Generate a generic topic that pulls information together based on a passed URL parameter and then renders it in a nice way. Using slide show was a step to further enhance this.

This is not a hard enhancement. You can just copy how I did the printview URL parameters.

While you are at it, the pattern skin uses ?template=viewprint to get the printable mode. Using ?skin=print results in font that is different from the TWiki if pattern skin was used.

However, there appears to be a problem with pattern skin in that if I force the viewprint template in your plugin, the title line is cut (it is as if the table is limited to grow only to a certain font size, and does not allow fonts larger than +2).

Although I agree with Peter that using template=viewprint is not the best answer, I am also trying to resolve the problem that SlideShow does not use the expected TWiki font. I tried forcing the font with a some local CSS file; that isn't working either. I assume I'm missing something.

Can someone give me a clue for a way ensure that I use the expected TWiki fonts in my slides?

You can define your own slideshow template that defines your preferred style (font, color) and layout. Copy the existing template from the SlideShowPlugin page to your own page, modify as needed, and point to it in your presentations.

Like AlexanderSeith, we have the problem here that the rendering is broken. It only happens for authenticated users (!), in the sandbox it is OK. What we do so far is to get the rendered HTML code from the sandbox and put it where we want to have it. Awkward, but works...

There are apparently three solutions for this topic: SlideShowPlugin, SlidyPlugin, and SlideShowPlugin with S5 extensions. Time for some convergence? Does anybody know whether all of them work? I like the configurability of SlideShowPlugin and the navigation and usage mode of the SlidyPlugin. Before I integrate them, any advice from anybody who has looked at this?

Keep in mind that the SlideShowPlugin is a standard release component, e.g. we have to watch out to not complicate the installation by requiring too many additional modules. I have not checked, does the SlidyPlugin contain all additional modules?

Later... This plugin ships with all required files. It does seem to require headings to be a level 1. If folded into SlideShowPlugin it should support any heading level, taking level of first heading after SLIDESHOWSTART as reference. I just updated the SlidyPlugin for TWiki-5.0.

There is also an integration of S5 into SlideShowPlugin. On SlidyPluginDev there is a comment that this is only for TWiki 3.x, but I am not sure whether that only refers to the integration or S5 in general. Plowing around on the WC3 web site I found several more slide show utilities based on Javascript.

Another thing I want to add that I like about SlideShowPlugin over the others (at least as an option) is that one can have a page extending vertically more than the browser window or screen window. While this requires scrolling, it works better when the data is generated (e.g., a data base driven presentation) and the size is less predictable.

It would be neat if one could have the navigation capabilities of the WC3 slides and the and much from SlideShowPlugin otherwise.

By the way, I looked at SlidyPlugin, and I guess you did to. It basically is a copy of SlideShowPlugin, but leverages a bunch of includes to do the formatting. It really should be changed not to require a template from the template location, but grab that just as SlideShowPlugin does for ease of customizability...

To be honest, I don't know much about Javascript. I can combine the plugins, but for the interesting aspect of allowing the Javascript based slides with the extension towards the bottom I need some help.

Adding key navigation was easier than expected. It is now in SVN trunk and 5.0 branch, as well as published at SlideShowPlugin. Supported keys: Home, Left-arrow, Page-up, Right-arrow, Page-down, End and Esc.

Known issue: Those keys are eaten also if the focus is on HTML input fields. Any JavaScript expert can help fixing this?