Skip to main content

ActionScript: JavaScript Event Handlers for JW Player

JW Player has a rich JavaScript API. One of the things you can do is to create JavaScript event handlers for ActionScript events. However, there are a few things that can bite you in the butt if you don't keep them in mind.

First of all, as the documentation points out, you can't set an event handler until JW Player is ready for it. If you set it too early, it won't work, and you won't even get an error message. If you have a function called playerReady, it'll automatically be called by JW Player. That's a great place to setup your handlers.

Next, when JW Player calls playerReady, it's supposed to pass an obj containing the ID for the HTML DOM object. In my experience, it doesn't. Hence, you have to lookup the object manually. See my previous post about the fact that you can't use jQuery's $() to lookup the object, but should instead stick with document.getElementById.

Last of all, remember that when you give JW Player your JavaScript callback, you have to pass the function's name as a string. It feels natural to pass a function pointer or even to have an inline function, but that doesn't work (nor will you get an error message).

In summary, here's the code:
function playerReady(obj) {
"TIME", "handleTimeEvent");

function handleTimeEvent(e) {


Jeroen Wijering said…
Thanks for your posting. You totally confirm what we feel to be the "pain points" in our current API. Unfortunately, these issues directly relate to communication restrictions on a lower level, between actionscript and javascript.

For the next release of the Flash version of our player (5.3), we are working on a dedicated javascript wrapper (something like SWFObject) that will work around these issues:

*) Listeners assigned before the player is "ready" will be queued up by the wrapper.
*) Support for jQuery will be added.
*) Function references will be translated to strings inside the library.

Would love to hear any other suggestions people have for improving our javascript API!
Unknown said…
hmm, can't an error message be generated that is kept as an internal string if you try to set an event handler too early and then when the player is all set up it get then log the internal string?
jjinux said…
Hi, Jeroen, thanks for your response!

I'm not actually complaining ;) I've had a much harder time coping with Boxee than I have coping with JW Player. About the only thing that really sticks out to me about JW Player's JavaScript API is that obj["id"] doesn't work as promised in playerReady.

> Unfortunately, these issues directly relate to communication restrictions on a lower level, between actionscript and javascript.

Yep, that's what I figured.
Anonymous said…
This comment has been removed by the author.
Unknown said…
Hi, I have a BIG QUESTION: ¿How do I "execute" an actionscript function? I have to execute it in order to get a decrypted URL by changing some variables... the thing is:

1) You have an URL

2) Somehow it pass trough a function
and it returns it a different result in base of the function's work. BUT I DON'T KNOW HOW TO EXECUTE IT!! ¿Can you help me?
jjinux said…
You're going to have to modify the source code for JW Player itself. Take a look at the file named, especially the calls to ExternalInterface.addCallback.

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p