> Hmm. Well, given that, what are your future goals of the GeeXboX > project, and where do they intersect and diverge from Freevo?
Let user decide. GeeXboX toolchain is modular and allows compiling the system with many features on or off. I'd like low-end system users to keep using old GeeXboX 1.x architecture (i.e using MPlayer built-in OSD Menu) and allow high-end users to use Freevo. So basically, we'll include Freevo with most of its options and plugins (at least the one that can be safely compiled in) to GeeXboX as the future UI. > If you'd > eventually like to have complete inclusion of Freevo 2 in GeeXboX, would > GeeXboX basically become a Freevo distro? Or would you retain your > existing application level stuff and offer the user a choice? As I've said, GeeXboX 2.0 will be a tuned/customized Freevo 2.0 Live-CD, unless for users who prefer keep using old UI. >> I've been playing with nearly the same toys Jason did with MeBox project >> and started using Evas for our GUI (but in C while he did in Python with >> Kaa) but after all, Freevo2 seems to be much more usable and advanced >> than our software ever will be. > > Or will be. Freevo2 still needs a fair amount of work though. :) Less fair that my current draft with EVAS ;-) But that's why we're focusing on Freevo 1.x in the first stage. > If your ultimate plan is to move to Freevo2, I don't think spending much > time with 1.6 is going to benefit you. 2 is (or will be) basically a > completely new product from 1.6, with completely new choices for its > lowest layers. That's not a big deal, it's probably the easier part to change for us. > Ultimately we'd like to see these patches in mplayer. I haven't been > pushing too strongly though because xine actually seems to be a better > player for my purposes, and these same customizations (overlay and > outbuf) can be done externally to xine and don't have to be merged in > xine-lib proper. Don't hesitate to push harder ;-) > This traceback looks a bit funky, like lines are getting cropped, so I > can't really make out what's going on. I can tell you that the problem > is that kaa.display isn't being compiled with X11 support. Freevo is > trying to use Imlib2Canvas which is an X11-based canvas. If this is > what you want (X11) then you'll need to see why kaa.display isn't being > built with X11 support. I have Xlib-dev packages in, why wouldn't kaa.display compile them then ? Ben ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel
