S5 1.1rc1
Published 19 years, 5 months pastOkay, so it’s been almost three months since the last time I updated S5. During that interval, I’ve been quite busy, but I still feel disappointed that I haven’t put more energy into the project.
As a partial salve, I’ve made a few changes to the S5 information pages. The main page now has links to the latest official version and latest revision, as well as quick links to useful information. I updated the FAQ a bit as well, to clarify the licensing situation. At some point, I hope to create a separate page that contains a feature list, but that’s on a back burner right now.
What I really want to do is finally make S5 1.1 a full, final reality. Therefore, I’m pushing it to version 1.1rc1 with the knowledge that there’s a new bug to be addressed. In Safari 1.3 (and I assume 2.0 as well, though I haven’t had a chance to install Tiger yet to find out) the arrow keys double-advance, or even more. So if you hit the “right” or “down” arrow keys, you’ll jump forward two slides; “up” or “left” moves you back two slides. On incremental slides, you’ll advance to the end of the slide, or the next incremental element. The space bar doesn’t evince the same problem.
I assume this is a keystroke handling problem, but I’m not entirely sure—the behavior of incremental slides makes me wonder if maybe it’s something else. Either way, if we can get that fixed and don’t uncover any other major problems, I’d be happy to call this bad boy done. Help, as always, is welcomed and appreciated.
Update: Pritt left a comment on another post providing a solution for the Safari bug. Look for 1.1rc2 shortly!
Comments (9)
Just FYI, but the double-advance problem is still present in Safari 2.0.
This is a silly thing of me to say, but we need to rally people to create more S5 skins. :)
Milan, are you saying my themes aren’t so beautiful that they eliminate any need for other skins? Why, I’m shocked!
Actually, I agree with you. The changes in structure between 1.0 and 1.1 probably cooled some enthusiasm there—which is another reason to get this thing fixed and finalized, so people can use it and theme it and what-have-you.
Eric, by any chance can the next iteration of S5 (say 1.2, it’s probably a bad idea to add a new feature in the rc phase) have a class set on the body tag to let developers style for the toggled/disabled JavaScript version? Looking at the code makes it look like this would be a trivial change and would be helpful IMHO.
I’m not certain I understand, Brian. Are you asking to have the JS add a class to the ‘body’, or to remove it? A concrete example of what should happen, and how it would be useful, would help me a lot.
Hmmm… I would take a look at the key handling code, but the 1.1rc1 zip link seems to be dead. Anyone else noticing this?
The 1.1rc1 link works. It has always worked. You know this because the computer tells you so. The computer is your friend.
On a totally unrelated note, ever notice that when you’re trying to reconcile two versions of a site, something inevitably gets missed?
<whistle type="nonchalant" />Am I correct in understanding then that to create a new theme for S% the only file you would really need to work with is pretty.css, which pretty much does what it says, makes the presentation pretty? And if we did create more S5 themes where would we post them? Do we send you a link to them to be bundled in the download or what?
Actually, I agree with you. The changes in structure between 1.0 and 1.1 probably cooled some enthusiasm there—which is another reason to get this thing fixed and finalized, so people can use it and theme it and what-have-you.