On Thu, 2006-01-05 at 22:06 +0000, Karl Lattimer wrote: > > But I'm not sure I can handle all events in the engine. The engine has > > no idea what what possible events can happen (like cdrom disc > > change). So I guess it will be abstracter. > > Why not just tell the engine when an event occurs and which event, we'd > need to come up with a list of events. If we have a comprehensive list, > then all we need do is hook up those which apply in the theme.
dischi, certainly for things like CD changes, we can use the Event class? It might make sense to use a dotted-style hierarchy for event names (like freevo.device.cd.change or something?) and raise post events when things like this occur. > I see a GUI rendering thread, an event thread and a GUI event handler > thread running concurrently. I'm not sure what benefit using threads would give us here. There would certainly have to be a big payoff, because the increase in complexity is high. > > It could be possible, but do you want to start a video player for each > > item? > > Maybe not?! could it be done by pre-rendering a png sequence, for > simplicity sake? Say as part of the freevo cache process? Nah, it's perfectly feasible to use kaa.canvas.Movie for this. Say if the cursor stays selected on a file for more than 2 seconds, a preview begins to play. This is trivial to code now. It could be one of those "if you have a fast computer, this is for you!" features. :) Jason.
signature.asc
Description: This is a digitally signed message part
