The target device of my experiments is the openmoko. For this reason I put the openmoko-dev list to cc, maybe somebody is interested there.<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
oddd. lossy uses libjpeg. BOTH use eet. eet uses jpeg compression for lossy and<br>
zlib for comp. there is also raw that doesnt compress at all.<br>
<div><br>
</div></blockquote>well.. then I do not understand why it crashes.... I use libjpeg.7 .. Anyway it is not the main point now. I changed to COMP and it works.<br></div><br><br>anyway ... my experiment was not really successful... support for sdl and directfb seems to be "broken" at elementary lib level... tried to add myself the different cases in elm_wind_add and brohters, but did not work, I found a a patch on a a thread here to make directfb working, but it did not. <br>
<br>The intention of my experience was to see if evas/ecore would behave better on top of a potentially accelerated directfb backend. However as far I understood from the code evas/ecore would have zero benefit from a 2d accelerated directfb driver. <br>
<br>My question is:<br><br> 1. as was reading on some other threads that one wants to get rid of Xrender. Would however efl be able to use some 2d acceleration (blit from videa ram to videa ram, draw/fill rectangle etc.) <br>
<br>2. is there any "interface" to inject some 2d accelerated code into the fb driver?<br><br><br>For example the most annoying on openmoko freerunner is slow scrolling. For example your map example becomes the same sluggish. This could be probably solved by scrolling through a temp invisible video memory buffer. <br>
<br><br clear="all"><br>-- <br>rgrds,<br>
mobi phil<br><br>being mobile, but including technology<br><a href="http://mobiphil.com" target="_blank">http://mobiphil.com</a><br>