Jason Tackaberry wrote:
> I was originally going to type a big long email update, but I figured
> the best use of that time would be spent writing some manner of
> documentation.  So I've done that, and you can see my working copy here:
>
>    http://sault.org/mebox/canvas/

Nice! Very nice! :)

Maybe you could move that to the Wiki as canvas doc? OK, first some
comments on your mail and after that some on the doc.

> On the TODO list is a "transition engine," so you can specify transition
> effects such as scaling, fading, sliding, etc.  

That would be nice. We need some kind of fade list of objects out and
another one in. And delete the objects after fading out. Maybe I can
set a switch to the engine, delete objects and add new once, turn the
switch again and calling update will to the fading between deleted and
new objects.

> Also, dischi has requested some kind of support for animation like
> MNG or possibly APNG.  This is possible, but just needs doing.
> Alternatively, if parsing MNG is complicated, a simple, custom
> approach could be devised, like a tarball of png files that specify
> frames in the animated sequence. 

Something like that. I only want to make it easy to define small
animations and (A)MNG sounds like an easy way to do that.

> The code is rather scarce of comments. :)

I saw that.

> Review the docs at the URL above and let's hear your comments.  If you
> have ideas and requirements speak up sooner rather than later. :)

OK, here some comments:

| (We need a more clever name – how's kaanvas?)

Maybe. But import kaa.kaanvas? Looks strange to me. Maybe kanvas? Or
something completly different.

| <canvas class="hello">
|     <image file="background.png" />
|     <text hcenter="50%" vcenter="50%">Hello world!</text>
| </canvas>

Can I define my own types? I mean, I could define a listing canvas to
show the Freevo listing and connect it to canvas with the <listing>
tag. Maybe not, I'm not sure if the basic xml stuff you wrote works
for Freevo. I mean, we need some sort of conditions, too, so I guess
we need to rewrite this in a special way for Freevo.

| canvas = kaa.canvas.X11Canvas((640, 480))

I guess a next major step would be to support other displays like fb
and dfb. We will need this to integrate it into Freevo. 

| canvas.add_child(kaa.canvas.Image("background.png"))
| canvas.add_child(kaa.canvas.Text("Now playing: " + 
os.path.split(sys.argv[1])[1]))
| movie = kaa.canvas.Movie(sys.argv[1])
| canvas.add_child(movie, width="70%", aspect="preserve", hcenter="50%", 
vcenter="50%")
| movie.set_color(a = 100)
| movie.play()

That looks nice. And I can detach the movie later to be played
fullscreen using xv and other possible extentions?


Keep up the good work.


Dischi

-- 
-----------------------------------------------------------------------------
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
-----------------------------------------------------------------------------

Attachment: pgp6Akpz0VSoG.pgp
Description: PGP signature

Reply via email to