I read the comment about Slippy the HTML Presentation and find your comment (http://seld.be/notes/introducing-slippy-html-presentations). In fact, I used S5 quite a lot well before finding Slippy.

As S5 was released quite a long time ago, I am thinking if there is an updated version available with adoption of HTML5 and jQuery. If not, I may try to follow the S5v2Beta or Slippy and develop on top of that.

E-Mail: Matthias.Ebert@gmx.de
Tested on Version: S5.1

Recommendations:
1) ALLOW DIRECT LINKS FROM OUTSIDE
2) SLIDE-LOOP toggled on/off by variable

1) ALLOW DIRECT LINKS FROM OUTSIDE
———————————-
To allow a direct link from outside to a specific slide,
I recommend to use the usual parameters behind the URL-name,
i.e. s5-demo.html?3
This example presents slide3 in the browser.

HOWTO:
You can simply add the following javascript function to slide.js:


function getParameter()
{
var url = window.location.href;
parameter = url.split("?");
return parameter[1];
}

This function has to be called in the last row of startup()

function startup()
{
...
goTo(getParameter());
}


2) SLIDE-LOOPS controlled by the variable loop
———————————————-
Endless slide-loops are importent i.e. on fares,
where a endless presentation is going on while the crowd walks by

HOWTO:
Two new global variables are needed:

var loop = true;
var loop_timeout =10000; // im miliseconds

Then add the following javascript function to slide.js:

function nextSlide()
{
var target = snum+1;
if (target >= smax) target = 0;
var url = window.location.href;
parameter = url.split("?");
document.location.href = parameter[0] + "?" + target;
}

This function has to be called in:
- the startup(),to be used by slide0
- the last row of go(), to be used by all other slides

function startup()
{
...
if (loop) setTimeout('nextSlide()', loop_timeout);
goTo(getParameter());
}

function go()
{
...
if (loop) setTimeout('nextSlide()', loop_timeout);
}

TODO
—-
- The variables should be controlled by the user!
- The user-interaction-menu didn’t work when loop=true.
- The loop didn’t show the sub-steps

I also found that variable ‘n’ or ‘i’ is often not declared properly, and the function names could use an update (function names starting with a capital, a function called ‘showHide’….)

Has anyone come up with a fix for this?

Thanks

–Also, is there a more appropriate user’s discussion list? –

http://www.assetnow.com/anx/index.cfm/1,8,106,html

2. Also made a variation on the S5 script to allow paged content. Divide a long document into div’s with class=”page” and it display one page at a time like the slide show.

http://www.assetnow.com/anx/index.cfm/1,8,167,html

div.image {float: right;}

re: #59

Thanks for the tip. I did play around with assigning display: none to the div control tag but found the arrows and toggle switch disappeared too–I’d like those to display. I’ll fool around with it some more but if you have an idea of how to get just the linkbox to not display I’d appreciate it.

-heads

( i have hade in mind just the technical point of view )

The content of a slide must be enclosed by a div with a class=”slide” attribute and a unique id=”slide[counter]” where the [counter] is replaced by the slide number. The id is required to be able to link to specific slides in a presentation.

From Opera Show Format 1.0 documentation. In the format I’ve created, the slide IDs are dynamically assigned instead of placed in the XHTML, but they use exactly the same format (slidenn).

So taking out those divs would, in fact, make the format more incompatible with OSF 1.0.

( i think i could be possible to ‘ parse ‘ the projection css for the Fox and for ie, so that it would work with such a js module with no more additional adaptions, but perhaps a little bit to much ‘ music ‘ )

But it’s more for personal interests, your current solution is sure ok.

( and i am a Opera user, so i would never work contra my browser :) )

Mikael: That would be nice, but won’t be part of the initial release. I’ll have to look at doing that in a later version.

Christian: My original Opera Show files did exactly that, only without the JavaScript. I’ve instituted the class="slide" constructs because it’s more compatible with OSF 1.0. Okay, to be totally honest, originally I instituted them because it was easier to process the DOM structure that way, but at this point they’re staying in due to OSF 1.0 compatibility.

Heads: div#controls {display: none !important;} or a rule to that effect. Alternatively, div#controls {position: absolute; top: -1000em;}.