Regarding the conversion from OpenOffice sxi files (and PPT via Open Office), I’ve already started work on some XSLT which does a basic job of this.

Any improvements and suggestions are welcome (you can add them to the wiki page).

cheers,

Luke.

It would be nice to resolve this, if this is indeed an issue.

It is ok with IE 6 (XP SP2)

1. Lets the user type a number (multi-digit is allowed), and stores the number typed. Typing any non-number key clears the entered number.
2. If the user hits Enter/Return while there is a number stored, they jump to that slide. Jumping clips at the end of the slideshow.
3. If the user hits any of the “Next” or “Previous” keys while there is a number entered, they skip the number entered (e.g. typing “5″, then hitting the spacebar would skip 5 slides forward)

All changes were made to the version of slides.js included in the v11b2.zip file. The modified slides.js file is located at http://www.liggitt.net/s5/v11b2/default/slides.js, and all changed lines are flagged with

// Numeric support change


To try it out, see these files:
http://www.liggitt.net/s5/index.html (original example slideshow)
http://www.liggitt.net/s5/index2.html (slideshow with 130 pages)

I wished I was using your current version!! Thanks again!

-Ryan

P.S. UP was very impressed with my slideshow presentation being projected on a large screen. Only problem I see with the slide show is the limitation on resolution. They had low (1024×768 or lower) resolution and the bottom of my slide show was cut off. I wish it could resize properly. Plus, IE has a problem of carring up when scrolling. All in all it turned out very impressive.

Had two suggestions:

1) While the idea of using different <div class=”slide”> is quite nice, I wonder if you could support the <link> element a bit more?

E.g. <link rel=”prev” href=”" /> and rel=”next” etc. There are quite a lot of inbuilt navigation features in the link element that would be quite useful.

Right now, the way I am thinking of using this is in such a way that a course I create will have 10 or so large chapters, each one with tons of slides in it. Those 10 chapters will be different HTML pages, while all the slides will of course be different divs. Each chapter will make use of appropriate link tags to link to the next, previous, and main ones for example.

One potential draw back to making each page into its own page and linking them via the link tags could be printability. One would have to go to each page and print it out, which would be combersome, if each page is a slide (or smaller subset of slides).

But, perhaps linking chapters could be useful? For now, I simply create a final slide in each chapter that links to the next chapter. In addition, I use a Firefox extension called Link Toolbar that will create the previous and next links etc. There is something like this for IE as well, but I forget what it is called. I find this quite useful for navigating between chapters in a presentation.

2) For the author type information that you present in the first slide in your examples, would meta tags be more useful?

In both these cases, the (X)HTML standards provide these features I and I think you would be able to access them at least using document.getElementByTagName(), I believe.

This could possibly help encourage people to think a bit more about the tags that are already there which may be useful and relevant. I think there may also be some reasonable drawbacks to relying on this only however.

Just some thoughts.

Oh yeah, this is very cool though, nonetheless ;)

Maybe I’ll (or someone else) work on some extended (though less compatibile) derivate in the future (hmm… maybe some XBL bindings come to my mind ^_~)

Oh, and just a moment ago, I thought about styling OpenOffice.org presentations, since they are actually compressed XML (at least in the development versin; European Union wants to accept it as an official format for data exchange). I haven’t seen the structure yet, but maybe using XSLT one could transform it to some usable document.

Yesterday I created my first S5 presentation for career day at my wife’s school. Wow! I am blown away by how damn easy it is to use and how cool the presentation is.

And, since it uses standards, I could easily demonstrate seperating content from style. In the middle of my presentation I opened up NotePad, changed the css link to a new path, reloaded and presto! the same presentation with a new look!

You keep making me look good, thanks Eric. (If I was thinking I should have labeled my presentation “Working Man” in your honor. Doh!)

[1] You may want to drop by PNG in Internet Explorer for further details.


/*@cc_on
@if (@_win16 != @_win16)
@set @_win16 = false
@end
@if (@_win32 != @_win32)
@set @_win32 = false
@end
@if (@_jscript_version >= 5.5 && (@_win32 || @_win16))
window.attachEvent(
'onload'
, function() {
for (var i = 0; i var img = document.images[i];
var len = img.src.length;
if ('.PNG' == img.src.substring(len - 4, len).toUpperCase()) {
var span = {
id: img.id
,className: img.className
,title: (img.title) ? img.title : img.alt
,style: 'display:inline-block;width:'
+ img.width + 'px;height:' + img.height + 'px;'
+ 'filter:progid:DXImageTransform.Microsoft.AlphaImageLoader(src=''
+ img.src + '',sizingMethod='scale');'
,toString: function() {
return ' + ((this.id) ? 'id="' + this.id + '" ' : '')
+ ((this.className) ? 'class="' + this.className + '" ' : '')
+ 'title="' + this.title + '" '
+ 'style="' + this.style + '">< \/span>';
}
}
if ('left' == img.align)
span.style += 'float:left;';
if ('right' == img.align)
span.style += 'float:right;';
if (img.parentElement.href)
span.style += 'cursor:hand;';
if (0 != img.style.cssText.length)
span.style = img.style.cssText.toLowerCase() + ';' + span.style;
img.outerHTML = span + '';
i--;
}
}
}
);
@end @*/

to drop by PNG in Internet Explorer for further details.

You want to build S5 support into your $49.95 fully copyrighted and licensed editor? Fine, no problem. You want to extend S5 to do more cool stuff? Also fine, but freely contribute the changes back to the place you got the code in the first place.

These two are contradictory. The scenarios are both a case of extending S5 (in the first case, extending it with editor functionality; in the second case, with “more cool stuff”). What is your policy: copyleft (share-alike, GPL) or non-copyleft (Expat license)?

Note that none of the existing free software licenses require someone to “contribute the changes back to the place you got the code”, because that’s an unreasonable requirement. It sets up “the place you got the code” as a central gatekeeper. It’s quite plausible that the “place you got the code” is not available at the time you want to distribute your changes to a third party — it may be years later, or you may be in an Internet-poor area, or any of a number of other circumstances.

More reasonable (and this is all that a copyleft actually requires) is to require that modifications to the original code should be available *to the recipient* when you give them the modified code, under the same license terms as the original. This way, you ensure that changes add to the common pool of S5 “cool stuff”, but there’s no particular gatekeeper to whom the changes must be submitted.