Re: [E-devel] Eo del/unref question

2013-01-31 Thread David Seikel
On Thu, 31 Jan 2013 21:40:56 +0100 Davide Andreoli wrote: > 2013/1/29 Tom Hacohen > > > No, custom constructor is not the old one. > > > > You need to use: > > > > #define elm_obj_win_constructor(name, type) > > ELM_OBJ_WIN_ID(ELM_OBJ_WIN_SUB_ID_WIN_CONSTRUCTOR), > > EO_TYPECHECK(const char *,

Re: [E-devel] Eo del/unref question

2013-01-31 Thread Davide Andreoli
2013/1/30 Yakov Goldberg > Hi Davide, > > The idea is to provide Eo with introspection and automatic bindings > generation. > Hi Yakov, I gave a quick look at you project, the idea is really interesting but as you said it's really a PoC; I can think of an high number of issues. So I'm happy

Re: [E-devel] Eo del/unref question

2013-01-31 Thread Davide Andreoli
2013/1/29 Tom Hacohen > No, custom constructor is not the old one. > > You need to use: > > #define elm_obj_win_constructor(name, type) > ELM_OBJ_WIN_ID(ELM_OBJ_WIN_SUB_ID_WIN_CONSTRUCTOR), EO_TYPECHECK(const > char *, name), EO_TYPECHECK(Elm_Win_Type, type) > After some more tests I have this

Re: [E-devel] Eo del/unref question

2013-01-30 Thread Yakov Goldberg
On 01/30/2013 03:09 PM, Cedric BAIL wrote: > On Wed, Jan 30, 2013 at 9:10 PM, Yakov Goldberg wrote: >> On 01/30/2013 12:49 PM, Cedric BAIL wrote: >>> Hello, >>> >>> On Wed, Jan 30, 2013 at 6:13 PM, Yakov Goldberg wrote: The idea is to provide Eo with introspection and automatic bindin

Re: [E-devel] Eo del/unref question

2013-01-30 Thread Cedric BAIL
On Wed, Jan 30, 2013 at 9:10 PM, Yakov Goldberg wrote: > On 01/30/2013 12:49 PM, Cedric BAIL wrote: >> Hello, >> >> On Wed, Jan 30, 2013 at 6:13 PM, Yakov Goldberg wrote: >>> The idea is to provide Eo with introspection and automatic bindings >>> generation. >>> >>> I made some PoC, a

Re: [E-devel] Eo del/unref question

2013-01-30 Thread Yakov Goldberg
On 01/30/2013 12:49 PM, Cedric BAIL wrote: > Hello, > > On Wed, Jan 30, 2013 at 6:13 PM, Yakov Goldberg wrote: >> The idea is to provide Eo with introspection and automatic bindings >> generation. >> >> I made some PoC, and can generate bindings for Python and JS - >> elev8. (elev8 is

Re: [E-devel] Eo del/unref question

2013-01-30 Thread Cedric BAIL
Hello, On Wed, Jan 30, 2013 at 6:13 PM, Yakov Goldberg wrote: > The idea is to provide Eo with introspection and automatic bindings > generation. > > I made some PoC, and can generate bindings for Python and JS - > elev8. (elev8 is javascript runtime based on Google's v8 js engine). > >

Re: [E-devel] Eo del/unref question

2013-01-30 Thread Tom Hacohen
On 30/01/13 01:59, Gustavo Sverzut Barbieri wrote: > On Tuesday, January 29, 2013, Tom Hacohen wrote: > >> Don't use eo_del/unref as counterparts to the old API. Create the objects >> with the new API if you would like to use them... > > > This is confusing at last > Burden of legacy. There might

Re: [E-devel] Eo del/unref question

2013-01-30 Thread Yakov Goldberg
Hi Davide, The idea is to provide Eo with introspection and automatic bindings generation. I made some PoC, and can generate bindings for Python and JS - elev8. (elev8 is javascript runtime based on Google's v8 js engine). I scan C -souces for Eo classes and functions definition

Re: [E-devel] Eo del/unref question

2013-01-29 Thread Gustavo Sverzut Barbieri
On Tuesday, January 29, 2013, Tom Hacohen wrote: > Don't use eo_del/unref as counterparts to the old API. Create the objects > with the new API if you would like to use them... This is confusing at last > On 29 Jan 2013 19:37, "Davide Andreoli" wrote: > > > Hi all, > > I'm working/studying

Re: [E-devel] Eo del/unref question

2013-01-29 Thread Davide Andreoli
2013/1/29 Tom Hacohen > No, custom constructor is not the old one. > > You need to use: > > #define elm_obj_win_constructor(name, type) > ELM_OBJ_WIN_ID(ELM_OBJ_WIN_SUB_ID_WIN_CONSTRUCTOR), EO_TYPECHECK(const > char *, name), EO_TYPECHECK(Elm_Win_Type, type) > haa, ok,now i can create a window u

Re: [E-devel] Eo del/unref question

2013-01-29 Thread Tom Hacohen
No, custom constructor is not the old one. You need to use: #define elm_obj_win_constructor(name, type) ELM_OBJ_WIN_ID(ELM_OBJ_WIN_SUB_ID_WIN_CONSTRUCTOR), EO_TYPECHECK(const char *, name), EO_TYPECHECK(Elm_Win_Type, type) >From elm_win.h. And well, you should switch to Eo for all the objects.

Re: [E-devel] Eo del/unref question

2013-01-29 Thread Davide Andreoli
2013/1/29 Tom Hacohen > Don't use eo_del/unref as counterparts to the old API. Create the objects > with the new API if you would like to use them... > Hi, thanks for the fast reply. I have tried that approach but I have problems with some objects than, for example elm_win: if I do: win = eo_ad

Re: [E-devel] Eo del/unref question

2013-01-29 Thread Tom Hacohen
Don't use eo_del/unref as counterparts to the old API. Create the objects with the new API if you would like to use them... On 29 Jan 2013 19:37, "Davide Andreoli" wrote: > Hi all, > I'm working/studying Eo while trying to optimize the python bindings > and I have some problems deleting eo object