[EMAIL PROTECTED] wrote: > Now that it seems to be stabilizing, I'd like to start testing it and > hopefully > be able to at least help finding possible problems with it. But since I'm > using > the DirectFB output, it's not clear to me how this will be implemented. That > is, > I know that at least prior to the plans to utilize evas, Rob was implementing > a > native DFB based graphics engine. But since as I understand, evas has a DFB > backend as well, which will be the supported/preferred setup: > > freevo -> kaa -> evas -> DFB > > or > > freevo -> (kaa?) -> DFB > > Would the latter be functionally equivalent to the evas based (i'm dreaming > animations etc. ;)) if implemented?
The future would be that Freevo uses kaa.canvas for all the gui related stuff. And kaa.canvas works using evas (wrapped through kaa.evas) and evas works on dfb. But right now the evas support is not in Freevo, we still use mevas (confused about all the *vas?). You can use mevas with pygame which works on dfb, but I never tested it. > Also, while I'm at it, is there a more recent doc for installing the > cvs version of freevo than the one in freevo2 wiki? That one seems > to be from the pre-kaa era... You install kaa and run freevo. So no, no newer docs. Maybe someone using cvs can upate the doc so we can spend more time hacking :) Dischi -- Those that make the rules don't play the game!
pgpZyORjqXDPZ.pgp
Description: PGP signature
