Re: [E-devel] UnifiedAPI Namespace definition proposal

2018-02-28 Thread Davide Andreoli
2018-02-24 16:47 GMT+01:00 Andrew Williams : > Just to follow up on this by way of “documentation on the website > handover”. Whether there is “consensus” or not there is still an underlying > issue. I exposed the namespaces that Daniel mentioned to make the website > API index more readable: http

Re: [E-devel] UnifiedAPI Namespace definition proposal

2018-02-24 Thread Andrew Williams
Just to follow up on this by way of “documentation on the website handover”. Whether there is “consensus” or not there is still an underlying issue. I exposed the namespaces that Daniel mentioned to make the website API index more readable: https://www.enlightenment.org/develop/api/start As you ca

Re: [E-devel] UnifiedAPI Namespace definition proposal

2018-02-24 Thread Davide Andreoli
2018-02-24 10:16 GMT+01:00 Vincent Torri : > On Fri, Feb 23, 2018 at 7:53 PM, Davide Andreoli > wrote: > > 2018-02-23 12:03 GMT+01:00 Daniel Kolesa : > > > >> On Thu, Feb 22, 2018, at 14:05, Davide Andreoli wrote: > >> > Hi all, > >> > > >> > I'm working again on autogenerated python bindings for

Re: [E-devel] UnifiedAPI Namespace definition proposal

2018-02-24 Thread Vincent Torri
On Fri, Feb 23, 2018 at 7:53 PM, Davide Andreoli wrote: > 2018-02-23 12:03 GMT+01:00 Daniel Kolesa : > >> On Thu, Feb 22, 2018, at 14:05, Davide Andreoli wrote: >> > Hi all, >> > >> > I'm working again on autogenerated python bindings for efl UnifiedAPI but >> > I'm quite blocked by the lack of na

Re: [E-devel] UnifiedAPI Namespace definition proposal

2018-02-23 Thread Felipe Magno de Almeida
On Fri, Feb 23, 2018 at 7:00 PM, Daniel Kolesa wrote: > On Fri, Feb 23, 2018, at 19:42, Davide Andreoli wrote: [snip] >> Of course Eolian should help us to not make mistakes, but the real issue >> at this point is that there isn't a clear consensus of what the namespaces >> are and how they shou

Re: [E-devel] UnifiedAPI Namespace definition proposal

2018-02-23 Thread Daniel Kolesa
On Fri, Feb 23, 2018, at 19:42, Davide Andreoli wrote: > 2018-02-22 17:02 GMT+01:00 Carsten Haitzler : > > > On Sun, 18 Feb 2018 10:28:54 +0100 Davide Andreoli > > > > said: > > > > hey dave. i had this marked... :) > > > > > Hi all, > > > > > > I'm working again on autogenerated python bindings

Re: [E-devel] UnifiedAPI Namespace definition proposal

2018-02-23 Thread Daniel Kolesa
On Fri, Feb 23, 2018, at 19:53, Davide Andreoli wrote: > 2018-02-23 12:03 GMT+01:00 Daniel Kolesa : > > > On Thu, Feb 22, 2018, at 14:05, Davide Andreoli wrote: > > > Hi all, > > > > > > I'm working again on autogenerated python bindings for efl UnifiedAPI but > > > I'm quite blocked by the lack o

Re: [E-devel] UnifiedAPI Namespace definition proposal

2018-02-23 Thread Davide Andreoli
2018-02-22 17:02 GMT+01:00 Carsten Haitzler : > On Sun, 18 Feb 2018 10:28:54 +0100 Davide Andreoli > > said: > > hey dave. i had this marked... :) > > > Hi all, > > > > I'm working again on autogenerated python bindings for efl UnifiedAPI but > > I'm quite blocked by the lack of namespace definit

Re: [E-devel] UnifiedAPI Namespace definition proposal

2018-02-23 Thread Davide Andreoli
2018-02-23 12:03 GMT+01:00 Daniel Kolesa : > On Thu, Feb 22, 2018, at 14:05, Davide Andreoli wrote: > > Hi all, > > > > I'm working again on autogenerated python bindings for efl UnifiedAPI but > > I'm quite blocked by the lack of namespace definitions in eo/eolian. > > > > This is a noproblem in

Re: [E-devel] UnifiedAPI Namespace definition proposal

2018-02-23 Thread Daniel Kolesa
On Thu, Feb 22, 2018, at 19:42, Mike Blumenkrantz wrote: > It seems there is some confusion both in this mail and in the community > about how the interfaces API works, partly due to how .eo files work and > the current syntax that is used. Some changes are in progress to make > things more clear,

Re: [E-devel] UnifiedAPI Namespace definition proposal

2018-02-23 Thread Daniel Kolesa
On Thu, Feb 22, 2018, at 14:05, Davide Andreoli wrote: > Hi all, > > I'm working again on autogenerated python bindings for efl UnifiedAPI but > I'm quite blocked by the lack of namespace definitions in eo/eolian. > > This is a noproblem in C and any other language without proper namespacing, > b

Re: [E-devel] UnifiedAPI Namespace definition proposal

2018-02-22 Thread The Rasterman
On Sun, 18 Feb 2018 10:28:54 +0100 Davide Andreoli said: hey dave. i had this marked... :) > Hi all, > > I'm working again on autogenerated python bindings for efl UnifiedAPI but > I'm quite blocked by the lack of namespace definitions in eo/eolian. a read of the below... why can't you just ha

Re: [E-devel] UnifiedAPI Namespace definition proposal

2018-02-22 Thread Mike Blumenkrantz
It seems there is some confusion both in this mail and in the community about how the interfaces API works, partly due to how .eo files work and the current syntax that is used. Some changes are in progress to make things more clear, and there will be more info on this soon. Regarding the points t

[E-devel] UnifiedAPI Namespace definition proposal

2018-02-22 Thread Davide Andreoli
Hi all, I'm working again on autogenerated python bindings for efl UnifiedAPI but I'm quite blocked by the lack of namespace definitions in eo/eolian. This is a noproblem in C and any other language without proper namespacing, but for the langs that provide namespaces (like python and many others

[E-devel] UnifiedAPI Namespace definition proposal

2018-02-18 Thread Davide Andreoli
Hi all, I'm working again on autogenerated python bindings for efl UnifiedAPI but I'm quite blocked by the lack of namespace definitions in eo/eolian. This is a noproblem in C and any other language without proper namespacing, but for the langs that provide namespaces (like python and many others