Skip to main content

Changing background color in SMIL


I've been working on a gateway system that will help a WASP to accept MMS requests and pass them on to the network for delivery to a mobile handset. For some reason the original designers of the gateway decided not to allow service consumers the ability to upload SMIL directly. Rather, an XML is POSTed to a webservice. The XML is then parsed into SMIL and handed to the network provider in a nice SOAP wrapper.

Why is this a problem? Well it means that only the gateway only supports a subset of SMIL. So in order to make a slide look the way that our client wants it to look we have to modify the gateway code to allow text colours and backgrounds to change.

Another problem I've had is that there seem to be very few SMIL tutorials online. When I'm learning a new language I usually pick up what I need by asking Google. Unfortunately even the mighty search engine draws a blank, provides hopelessly outdated pages, or documents like the technical specifications which I don't have time to wade through.

One useful SMIL tutorial I found was the one provided by the folks who bring you Real player. They were one of the early adopters of SMIL technology and seem to be fairly heavily invested in providing Real Player for the mobile market. Their SMIL tutorial is at least up to date, easy to read, and transfer well to open source development. Of course their player is proprietary and so isn't supported by Ambulant player (an open source SMIL 3.0 compliant player).

The MMS gateway that I'm working on was written in C# about a year and a half ago (I'm guessing). The SMIL code it produces is definitely version 1.0, which wasn't even a full W3C standard. It was only since the release of SMIL 2.0 that it has become a recommendation, which has now been superceded by SMIL 3.0. I found a useful summary of changes between two of these versions (here), but can't find a cheat sheet for version 3.0. As soon as I do I will update this post with it.

I worked out that although the gateway is sending a version 2.0 header it is parsing incoming XML into version 1.0 tags. Instead of properly parsing the incoming color parameters it had a hardcoded value setting all slides to black and white. Since the project is due immediately I decided to rather "cheat" instead of fixing the gateway to parse correctly. I wrote a small PHP image editing class that simply writes whatever text I send it on top of a background image. I then base64_encode the image and send that as normal jpeg image content in my slide. This worked first time.

SMIL defaults the and areas to a uniform black, while regions and subregions are set to be transparent. To change the background colour in SMIL 2.0 you set the backgroundColor attribute (in SMIL 1.0 you would use background-color ).
Labels:

Comments

Post a Comment

Popular posts from this blog

Separating business logic from persistence layer in Laravel

There are several reasons to separate business logic from your persistence layer.  Perhaps the biggest advantage is that the parts of your application which are unique are not coupled to how data are persisted.  This makes the code easier to port and maintain. I'm going to use Doctrine to replace the Eloquent ORM in Laravel.  A thorough comparison of the patterns is available  here . By using Doctrine I am also hoping to mitigate the risk of a major version upgrade on the underlying framework.  It can be expected for the ORM to change between major versions of a framework and upgrading to a new release can be quite costly. Another advantage to this approach is to limit the access that objects have to the database.  Unless a developer is aware of the business rules in place on an Eloquent model there is a chance they will mistakenly ignore them by calling the ActiveRecord save method directly. I'm not implementing the repository pattern in all its ...
Post a Comment
Read more

Using Azure Active directory as an OAuth2 provider for Django

Azure Active Directory is a great product and is invaluable in the enterprise space. In this article we'll be setting it up to provide tokens for the OAuth2 client credentials grant. This authorization flow is useful when you want to authorize server-to-server communication that might not be on behalf of a user. This diagram, by Microsoft, shows the client credentials grant flow. From Microsoft documentation  The flow goes like this: The client sends a request to Azure AD for a token Azure AD verifies the attached authentication information and issues an access token The client calls the API with the access token. The API server is able to verify the validity of the token and therefore the identity of the client. The API responds to the client Setting up Azure AD as an OAuth2 identity provider The first step is to create applications in your AD for both your API server and the client. You can find step-by-step instructions on how to register the applications o...
Post a Comment
Read more

"Word of the Day" PHP script (with word list)

I was looking around for a way to generate a word of the day on the web and didn't find anything. So I coded a quick and dirty script to do it. Just in case anybody does a Google search and manages to find my blog: here is my Word of the Day PHP script : Copy this code snippet into a wordoftheday.php file: $file = fopen("interesting_words.txt","r"); $raw_string = fread($file,filesize("interesting_words.txt")); fclose($file); $words_array = explode("|",$raw_string); echo $words_array[array_rand($words_array)]; Of course the real issue I had was finding a list of interesting words in the right format. Here is the list of interesting words that I used: Copy this into a file called interesting_words.txt : ubiquitous : being or seeming to be everywhere at the same time; omnipresent| ecdysiast : a striptease artist| eleemosynary : of, relating to, or dependent on charity| gregious : c...
Post a Comment
Read more