<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'DejaVu Sans'; font-size:10pt; font-weight:400; font-style:normal;">Hi,<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> Well, intone - the media player in making (and it's **really** basic as<br>
> of now), uses 0% CPU (according to HTOP (all my tests are with it).<br>
> mplayer, in a separate thread uses its usual 15% or so.<br>
><br>
> I'm using anjuta and glade for development, using fifo (named pipe) to<br>
> communicate with mplayer running as slave and gtk+ for the frontend. As I<br>
> have said before - the code is ***really*** basic. It makes a lot of<br>
> assumptions, and is right now just a demonstration program - while I get<br>
> some feedback on whether I need to put in any more time in it at all.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>If it is in such an early state, you might consider switching to some EFL based GUI library, like Elementary or Edje. Besides eating less RAM than your GTK+ program, they are also easier to use on touchscreen devices.<br>
Your ideas sound really promising, so please consider the switch to a toolkit, that was designed for small screen devices.<br>
(The right tool for the right job ;-))<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>-- Fabian</p></body></html>