Jason Tackaberry wrote: > On Fri, 2005-12-23 at 14:04 +0100, Dirk Meyer wrote: >> 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. > > I don't really want to recode all that to use wiki's syntax. Can we put > it somewhere on the site and just link to it from the wiki?
OK, maybe someone else wants to help by doing it. *hint* *hint*
>> That would be nice. We need some kind of fade list of objects out and
>> another one in.
>
> Crossfade would be one of the transition effects.
>
>> 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.
>
> I'm not sure what you mean by deleted. If the objects are deleted from
> the canvas, how can you fade between them once they are deleted?
>
> I don't think the canvas should be responsible for automatically
> removing objects. Objects can have transition_begin and transition_end
> signals and you can just connect to transition_end for the objects you
> want to be deleted, and have them unparented.
That's ok, too
>> Maybe. But import kaa.kaanvas? Looks strange to me. Maybe kanvas? Or
>> something completly different.
>
> Well, yes. kaa.kaanvas doesn't look right. kanvas makes it look like
> it's a KDE library. But I think it should be something other than
> "canvas" because that's far too generic. :)
And we have a name problem again. :(
The keywords are kaa, python, canvas, graphic
Any suggestions?
>> | <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.
>
> It's not extensible right now, but I plan to change it so that you can
> extend it to add new elements. But for Freevo's requirements, it may be
> necessary to implement your own parser. I mainly added the xml stuff
> because I could, and because it's very easy to test different kinds of
> layouts. It's helped me find a lot of bugs.
>
> What kind of conditions do you need?
I guess to much for your generic code. I need something like "if item
has image, draw rectangle and image" or "if item has length, write
item.length + '.min'"
> Yes, it uses xv when it's detached. I'm not quite sure how it will
> work with other VOs. With x11 it creates a subwindow of the main app
> window, and tells mplayer to display there using -wid. With framebuffer
> vo I suppose it's just a matter of which process is drawing is the one
> that's visible. (When a movie is being drawn on the canvas, it is not
> being drawn to its vo, so this should work fine with fb).
I will play with canvas + fb the next week if I have some time.
Dischi
--
panic ("No CPUs found. System halted.\n");
2.4.3 linux/arch/parisc/kernel/setup.c
pgps0rnzWxbHA.pgp
Description: PGP signature
