On Mon, 02 Nov 2015 11:21:47 +1000 Peter <[email protected]> wrote: > On 2/11/2015 9:41 AM, Carsten Haitzler wrote: > > On Mon, 02 Nov 2015 09:24:23 +1000 > > Peter<[email protected]> wrote: > > > >> Is there a platform independant way of obtaining a Window and > >> binding the EGL display to it without using EFL on Tizen? > >> > >> Is there a possiblity of Tizen supporting OpenKODE from Khronos in > >> the future? > > no. evas_gl replaces egl. it's done this way because there are so > > many other things you want to use the widget infrastructure for like > > indicator, kbd handling (eg sizing content to move out of the way of > > the kbd) etc. and if you use evas_gl you can merge both ui, widgets > > gl api. > > > > you simply need to change the egl parts (it's actually less work > > using elm_glview than using egl - by far) and ensure your rendering > > all happens in the render callback. > > > Carsten, > > Sounds good for creating a new application. > > I was investigating the work required to port an existing application. > > I noticed the EGL and GLES libraries exist on the tizen platform > emulator.
yes - but you can't use them if you ever want to ship/distribute your app. platform components only as they can change to move display systems. > I was thinking of writing a wrapper library, that implements GLES2.0 > around evas_gl. A Tizen application has it's own lib directory, if > I install the wrapper library into this directory, will it be > resolved instead of the system GLES libraries? i ... don't know actually. i do know that evas_gl and egl are not an exact 1:1 match and there are other things like NO swapbuffers so you structure code differently. you are best off restructuring the egl code and isolating it in a porting layer etc. > Thanks, > > Peter. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
