Category Archives: AOS Web Player

AOS Web Player is the main player of the project and let you play digital sequences inside a web page.

Focus in 2013 (part 1): Communication

As explained in the previous post, communication about the project is, on all sides, a failure. Most people don’t understand the problem that is being fixed, the need nor the solution or how to participate to help. This really needs to be fixed as lack of participation on the development effort is the only bottleneck of the AOS projects. Here is what I plan to do in the coming weeks to fix this.

IMAG0194

The main information source on Art Of Sequence is this very website. In it’s current state, it have several problems:

  1. Text wallsTL;DR - any non-academic or already interested in the subject people will stop after a few lines of the text walls I put in each pages of this website.
  2. It don’t state clearly what is the problem being solved.
  3. It is not clear what exactly is the Art Of Sequence project. I mean, it does have some explanations about what it is but it is not clear enough how the AOS projects solve the unclear problem.
  4. The Web Player Demo isn’t clear enough what it is about, what is demonstrated.

That’s basically it.
The following is what I’m working on to fix all this.

New Website Front & Content

I started designing a new front page for the website that would be a simple static page that would look like a comics page. It would contain big sized texts with very short, succinct and concise explanations. Part of the page, in the biggest panel, there would be the AOS Web Player demo running, with a quick description of what the hell it is.
This front page should be done and public in the beginning of the year.

In the mean time I plan to radically rewrite each page describing AOS projects. The goal will be to make simpler explanations with more obvious examples of what it is about. I started writing and working these texts and I am confident it will be far better this way.

What is AOS

One of the first things I already changed in several places (including the project’s Twitter account description) is the quick summary of what AOS is.

Art Of Sequence is a set of “digital story-telling technologies”. No more, no less. This is a bit less precise than previous descriptions (which were different depending on where you look at…) but the specific technologies are different depending on what project you’re interested in, if you are an author or a programmer, if you are a reader or a digital comics enthusiast. Each project have a specific purpose, a problem to solve, but it’s only when all projects are put together that they shine.

I’m preparing a special intro to AOS that should be efficient enough to get the point of what are the problems and how each project solve a part of it.

Another important change in the way I will present the projects is what is AOSL. So far I often talk about AOSL as a “language”, but it’s actually a meta-format specification. It could be based on something else than XML, and it’s supposed to be used to create other more specific formats for specific platforms. So basically, I’m changing my discourse about AOSL this way: AOSL is an intermediate data format meant to allow different digital-storytelling tools and reader applications to work together. The AOSL page will be simplified and will clarify things by stating that not only it’s a potential standard for work files for different tools targeted at digital storytelling, for players and converters; it is also the base of future different file formats. More on that in the next article.

Clarifying the Demo

Originally, I planned to add clarification tooltips and other quick info in the AOS Web Player demo page, to make sure it’s clear what it was a demo about. Unfortunately I was short on time so I released the demo page as it is still today. Most people assumed it was an attempt at replacing Flash, which it is not. This is the hardest part to clarify as the demo don’t say what it’s showing exactly and most people will obviously say you can do the same in Flash. I know, that’s part of the point.

AOSWP demo is meant to show how the AOSL language works with a player implementation. This means even if I add clarifications in the AOSWP demo page, there will still be a need to explain better what AOSL is. The ideal demo would be to have both a Flash implementation and a JavaScript implementation of the same story in the same page. This way the reader would start to understand that the same story, defined using AOSL, can be converted to different platforms (HTML5, Flash, NACL, etc.) with almost no difference.

But writing a Flash implementation of a player, even if in my plans, isn’t a priority at the moment. I will not focus on this but I will make sure at least that the demo page is clarified.

Presentation (PowerPoint)

In the first half of this year I was working in Japan in a creative company which was interested in the kind of technologies AOS was, in particular as it is theoretically possible to build a digital manga editor business over these technologies. We couldn’t continue working together in the end, but when I was there I was allowed to take the time to setup a presentation about what AOS is. I have a copy here and with some modifications, I could publish it. I think it was a good intro on what is AOS.

However, I am a bit annoyed that it’s a PowerPoint. You see, the best way to present a technology that allow (or focus on) narration is to use this technology to make a presentation. Lacking an edition tool, as AOS Designer is far from being usable yet, I would have a very hard time today making the same presentation with only AOSL code. I hope to be able to do this in a few months -more on that in the next article- but clearly it’s not a possibility today. Is it tolerable to publish a PowerPoint for now? I have some doubt but I think publishing something OK today have more value than publishing something perfect in 6 months.

To Be Continued…

In the next article, I will present the development, purely technical points on which I need to focus my efforts on to both make the project going forward and attract contributors to help on the project.

If you have suggestions of improvements on the communication of AOS projects, or any other feedback, please comment here!

AOS Web Player v0.1 – Online Demo

Take a look: http://demo.artofsequence.org/
(use arrows or space key after having clicked in the image if you want to use the keyboard).

This is the public demo of the Art Of Sequence Web Player (AOSWP) implementation, version 0.1. It’s fully implemented in JavaScript and can read the basics of AOSL (the xml-based language on which every AOS tools relies on) in it’s version 1.0-draft-3.

As always, the source code can be found at http://dev.artofsequence.org but please read the following before trying to use it.

Continue reading

AOS Web Player – Progress!

Being able to work almost full time on Art Of Sequence in the last weeks is paying off. As evoked in the precedent post, I recently started work on the implementation of the web player, AOS Web Player or AOSWP.

The basic idea is to have a simple JavaScript library that would just take the url of an AOSL file as input and an HTML div to fill in with the player, then load and interpret the sequence file, load the resources used and display the sequence in the web page. Simple in theory, yet AOSL is made in a way to unleash a lot of possibilities that are specific to digital platforms thus making the implementation having to manage a general case that is a bit more complex than with a timeline.

After some heavy hackery-hacks, I managed to get the player to read a very simple sequence that only show and hide a simple image. The sequence can have branches or loops, it just work. Still a lot to do before making it useful, but the basic concept of AOSL is now proven to work.

I am very far from being a JavaScript expert, so the code is a badly organized (to me at least) and it lacks a lot of features and tests. Here is a screenshot of an extremely simple demo I’m using to test features:

That…don’t look very sexy…yet.

However it works. What is needed now is to build a demo of this work, that would be a bit more “demonstrative” and sexy. Both completing the player feature and building this demo might take some time because I’m getting back to France next week and from there I will only be able to work on AOS about 1/3 of my work time.

Once a first demo will be visible online, i hope to gather some people to work on this and make it good enough for general use, in combination with AOS Designer edition tool.

For developers who want to take an early look at the code (and maybe help with patches or at least code reviews) can find my work in this repository (in the branch named ‘wip_aoswp’): http://code.google.com/r/mjklaim-aos-webplayer/ This will be merged soon in the main repository ( http://code.google.com/p/art-of-sequence/ ).

I have some ideas for the demo, including allowing the testers to change AOSL code on the fly and see the impact of their changes. However, the main feature would be to provide meaningful sequences that show the features in an efficient (and fun, and sexy) way.

Stay tuned!

Full Steam Ahead

The past months have been very slow for Art Of Sequence projects.
My move to Japan and hard work learning japanese and dayjob mad almost impossible to do more than (important) documentation to help other interested people help me.

Fortunately for me, as evoked on my personal blog, things have radically changed last week and I am now able to work on AOS as much as I want for some time. Actually, I’ve been working on fixing some problems with AOSL (with the helpful review of one of my skilled friends)  and a new draft, slightly simplified compared to the previous ones, of AOSL 1.0 is now almost ready. As I’ve been working on my laptop the whole time in an isolated repository, I didn’t upload the changes yet but it will come very soon.

I cannot promise to work on AOS full time from now on as I have other game projects I need to start or continue next month when I’ll get back to France, but I’ll spend most of my time working on AOS until then. I still plan to spend a lot of time on AOS, just less than now.

Other than fixing AOSL 1.0., the plan is as follow:

  • modify the website to present an example sequence on the front page (more on this later)
  • finish the human-readable documentation that explain how the AOSL format works
  • write AOS Web Player 0.1. that would be used in both previous points
  • continue work on AOS Designer as much as I can

I’ll make a list of documentations that need review soon and expose them here. I’ve given updates on the developer mailing list but nobody gave feedback so far, but I hope the AOSL documentation will help a lot of potential tool maker understand how to benefit from it.

Status Report #1

Today I’m exposing to you the current state of the work done on the different AOS sub-projects. Keep in mind that even if lot of code and docs have been written, this is still work in progress that should get us to something usable in a not so far future. To this day the development is a one-man-army effort but I hope that contributions will come to help soon.

Continue reading