Hi,
I think that maybe I could have explained this a little better, let me step
back from the implementation details for a minute.
As a user of this API all I want to know is do I have to unref a reference
that I have been handed. From this point of view we should be consistent.
My proposal was (
Hi,
Surely hide and unref are separate? Why are we trying to do both with a
single call to _del? If we wish to continue supporting "hide and unref" in
a single call then we can - but as a convenience. It could be documented as
such: "del will remove your reference to the object and, if the object
On Fri, 22 Dec 2017 09:43:20 + Andrew Williams said:
> Hi,
>
> I think that maybe I could have explained this a little better, let me step
> back from the implementation details for a minute.
>
> As a user of this API all I want to know is do I have to unref a reference
> that I have been h
Hi,
A good point - we do need consistency at the core. Additionally as Eo was
designed to make binding easier then allowing a :bool event type is
probably not in the spirit of things.
Whilst it is convenient I'd also say that (event->info) is unclear - given
the noun nature it looks like a check
On Fri, 22 Dec 2017 at 09:59 Carsten Haitzler wrote:
> On Fri, 22 Dec 2017 09:43:20 + Andrew Williams
> said:
>
> > Hi,
> >
> > I think that maybe I could have explained this a little better, let me
> step
> > back from the implementation details for a minute.
> >
> > As a user of this API a
On Fri, 22 Dec 2017 09:47:34 + Andrew Williams said:
> Hi,
>
> Surely hide and unref are separate? Why are we trying to do both with a
> single call to _del? If we wish to continue supporting "hide and unref" in
> a single call then we can - but as a convenience. It could be documented as
>
On Fri, 22 Dec 2017 10:10:48 + Andrew Williams said:
> On Fri, 22 Dec 2017 at 09:59 Carsten Haitzler wrote:
>
> > On Fri, 22 Dec 2017 09:43:20 + Andrew Williams
> > said:
> >
> > > Hi,
> > >
> > > I think that maybe I could have explained this a little better, let me
> > step
> > > bac
Hi,
I think your summary about the Gtk is not what you think - read the docs
further
https://developer.gnome.org/gtk3/stable/GtkWindow.html#gtk-window-new and
you see that actually the trivial example leaks the reference - just like
an efl_add_ref with no unref or del later.
They are *not* returni
We do have a showstopper design bug.
We are managing to work with it because we know how it works internally.
The API must be straight forward and provide consistent, robust options.
Any new user would be asking of efl_add:
*) Do I need to unref the result when I am done?
*) How long is my returne
> Original Message
> Subject: Re: [E-devel] efl_add causing confusion
> Local Time: December 21, 2017 7:18 PM
> UTC Time: December 22, 2017 3:18 AM
> From: ras...@rasterman.com
> To: Enlightenment developer list
> Cedric Bail
>> you have an object and you do evas_object_del()
hello
i've recently seen this gtk roadmap :
https://wiki.gnome.org/Projects/GTK%2B/Roadmap/GTK4
is there the same for EFL ?
Vincent
--
Check out the vibrant tech community on one of the world's most
engaging tech sites,
> Original Message
> Subject: Re: [E-devel] ecore / efl loop work
> Local Time: December 20, 2017 5:30 PM
> UTC Time: December 21, 2017 1:30 AM
> From: ras...@rasterman.com
> To: Andrew Williams
> Enlightenment developer list
>
> On Wed, 20 Dec 2017 18:36:30 + Andrew William
Original Message
> Subject: [E-devel] ecore / efl loop work
> Local Time: December 14, 2017 9:30 PM
> UTC Time: December 15, 2017 5:30 AM
> From: ras...@rasterman.com
> To: e
>
> I've been working on this for a while and now have things in a pretty good
> state. I just pushed a
Hi all,
I recently updated the API landing page to group by namespace:
https://www.enlightenment.org/develop/api/start
What this has indicated is that there are a few things out of place. The
list as far as I can see it is:
Efl.Access.* -> Efl.Ui.Access
Efl.Animator -> Efl.Animation.Animator
Efl
Hi enlightenment developers,
Many improvements are done due to last release.
Version 1.1 introduces faster data processing and redraw mechanisms.
The goal of this release is update the profiling viewer to be usable
during on-the-fly profiling. Updated Clouseau extension provide new UX
for make th
Ran into a build issue, maybe ninja specific not sure. I switched all E
cmake based ebuilds over to ninja generator from autotools. Cmake
supports both autotools/make and ninja. Thus far I have yet to see any
build issues specific to ninja. Though I suspect this maybe one.
ninja: error:
'/tmp/port
Hi Vincent,
I would really love this too - in fact I have been pushing for it. I
suggest regularly that it would be helpful to have a roadmap. On my most
recent request I was told bluntly “too much effort, you are the only person
that wants it”.
If we can get more support for such a document I wo
Hi,
I think it would be very nice to have a roadmap document.
For people like me that follow the project from a distance and do not hang
out much on IRC, there is little immediate visibility on what's going on.
I'd hope a roadmap could bring the key ideas of what (maybe who?) is doing
what, withou
18 matches
Mail list logo
