This is not, strictly speaking, a Perl question, but ...
In order to do a conference presentation on an aspect of Perl next
month, a colleague and I have chosen to use an HTML-based slide show
which we'll present from an iBook or PowerBook. We both customarily use
Safari as our default browser.
I've done other presentations with Apple Keynote and have used a
wireless presentation remote (Kensington model 33062) to go forward and
backward inside Keynote. I'd like to do the same with this HTML-slide
show using Safari.
My colleague knows enough Javascript to have successfully bound the 'n'
and 'p' keys to the forward and backward motion of the Safari browser
... but I'd like to be able to the same thing remotely, i.e., not have
to touch the keyboard to go to the next slide.
Does anyone know how to bind the keys on this remote to actions in Safari?
(I found this link but can't assess its relevance:
http://lists.runrev.com/pipermail/use-revolution/2004-September/044787.html)
Thanks in advance.
Jim Keenan
>This is not, strictly speaking, a Perl question, but ...
>
[quoted text clipped - 5 lines]
>
>Does anyone know how to bind the keys on this remote to actions in Safari?
Personally, I'd just use S5 (http://www.meyerweb.com/eric/tools/s5/) which has navigation bound to the forward and back arrow keys, unless you need something in your setup that S5 doesn't offer.
-C
James E Keenan - 25 May 2005 03:37 GMT
> Personally, I'd just use S5 (http://www.meyerweb.com/eric/tools/s5/) which has navigation bound to the forward and back arrow keys, unless you need something in your setup that S5 doesn't offer.
Well, my original posting was seeking advice on how to get the remote to
work with Safari -- not to solicit alternative technologies.
In any case, my colleague (fellow Phalanx hoplite), Marc Prewitt, came
up with this Javascript which we've included in the POSTAMBLE file of
Mark Jason Dominus's txt2slides.
<script><!--
document.getElementById("next").focus();
document.onkeydown = function (evt) {
var code = evt.keyCode;
switch (code) {
case 34:
case 78:
location.href = document.links["next"].href;
break;
case 33:
case 80:
location.href = document.links["prev"].href;
break;
case 72:
location.href = document.links["home"].href;
break;
case 76:
location.href = document.links["last"].href;
break;
}
return true;
};
--></script>
where we have 4 screen links, 2 of which we want to control from the
wireless remote.
jimk
I find the "can't assess its relevance" comment rather ironic.
I know Jim probably didn't mean it that way, but Hypercard was always
one of those products that was difficult to define. Trouble assessing
the relevance was probably the biggest barrier to its uptake. I see
Runtime is still strugging with that. A lot more CPU/platforms, and a
better presentation and sales strategy than two years ago when they
bought rights to Metacard, but it's still hard to assess it from a
management point of view.
Wish I could add some input beyond what Jim has already found with
using Javascript.
On 2005.5.24, at 11:41 AM, James E Keenan wrote
> This is not, strictly speaking, a Perl question, but ...
>
[quoted text clipped - 19 lines]
> http://lists.runrev.com/pipermail/use-revolution/2004-September/
> 044787.html)
(Edit the closing paranthesis to get that link to work.)
> Thanks in advance.
>
> Jim Keenan
James E Keenan - 27 May 2005 03:24 GMT
> I find the "can't assess its relevance" comment rather ironic.
While googling, I had to wade through several pages of links to
different vendors who sell that Kensington product. The link I
mentioned was the only one that gave any clue as to how to *adapt* the
Kensington wireless remote to the task at hand.
Incidentally, I contacted Kensington tech support about this and they
were absolutely clueless! I now quote the central paragraph of their
response -- *verbatim*!
"I appreciate your immense interest in Kensington products. I am sorry
to inform that the product has been designed for presentation
applications and has been sucessfully tested on powerpoint. I would
request you to try programming the buttons, however, we cannot assure
whether it would work or not."
In other words: We can't figure it out; you do it!
I e-mailed them back saying that I (or, actually, my partner) had
discovered the answer ... but that they would have to search the
Internet to find out how to do that.
But I'm very glad to have an answer because the organizers of
YAPC::NA::2005 in Toronto -- the conference at which we'll be presenting
-- have said that they want presenters to target HTML (rather than, say,
PDF) for archiving their presentations. (They also gave a plug to the
slideshow technology mentioned in another posting to this thread, but
we've already done most of our show in MJD's txt2slides.)
jim