From: Carsten H. (T. R. <ra...@ra...> - 2006-11-19 23:22:33
|
On Sun, 19 Nov 2006 18:33:20 GMT "jos...@ju..." <jos...@ju...> babbled: >=20 > Carsten writes: >=20 > > ... > > see a mail i just replied to jose with regarding this. what we need > > is a way to hook native engine drawable types (pixmaps, tectures, > > fbo's, pbuffers etc.) to evas objects. most of the rest is already > > done :) > >=20 >=20 > Subsequent emails by Rene and myself go into this a bit more.. > ie. engine specific 'buffers' set on engine specific 'image' objects. yup. i saw it heading that way :) i guess i'm agreeing :) > While one could do this for existing evas image objs, and that > has some obvious benefits, it might create conflicts and/or cause some > implementation difficulties that way. Needs more looking into... i can't think of any - that's the thing. if its now a ":native surface on= ly" the implementation could refuse to provide pixel data, for example. if you se= t the file on the object it can delete the native surface and go back to normal= image operations. that's pretty much about it. > jose. >=20 >=20 >=20 > -----------------------------------------------------------------------= -- > 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=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >=20 --=20 ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... =E8=A3=B8=E5=A5=BD=E5=A4=9A Tokyo, Japan (=E6=9D=B1=E4=BA=AC =E6=97=A5=E6=9C=AC) |