With Mike's health problems as well, it's sounding like the entire thing (EFL and Enlightenment) might need to just slow down for a bit.
On Fri, 3 Jun 2016 16:24:55 -0700 Cedric BAIL <cedric.b...@free.fr> wrote: > Hello, > > I just would like to start a thread regarding what is still pending > for next release and what we should do about it. First let's start > with what is not ready : > - Most of the elementary widgets have not been renamed correctly to be > in efl.ui namespace. > - Edje and Elm.Layout have not been refactorized and properly > inherited from each other. > - Text interface is not there (this impact also entry, label and > edje). > - Genlist is also not there. > - All eo object still needs a proper cleanup and use of own(). > - Uri manager is not there. > - Color/Color_Class is not there. > - Efl photocam is not there. > - Efl video is not there. > - Efl.Ui.Window is not there. > - Efl.Ui.Focus cleanup is not there. > > Sone of the above have patch in review process that may land before > Monday morning, but I prefer to just give the current status as I may > not have time this weekend as I am moving. Also most of the API that > have landed so far have not been tested in any real application and we > don't really if they do fit their purpose (making life easier). My SledjHamr project is one of the real applications that would be using a lot of the Ecore_Con, Elm, Eo, Evas_3D, and threading stuff. It's still not fully working right, but at least builds and doesn't crash anymore. Some of the current bugs might be related to the focus and genlist stuff not being there. Video is due to be added to this project later (I want to hook up video to the terrain heightfield, so people can create earthquakes). My new Conky experiments will use Lua and Edje stuff, and might eventually use whatever EFL has for hardware monitoring these days. That will need the color and text stuff, so that's on hold for now. > It is obvious to me, and I am pretty to sure to everyone involved in > the development of 1.18 that we can not do an alpha while some of the > biggest change are not there yet. Now the question is should we delay > the alpha ? Or should we make the alpha a technical preview followed > by an alpha later on ? Should we just move on and delay the above > change for 1.19, in which case all the new API need to remain BETA. > Also if we do delay, how much longer is needed for a release ? Isn't > it going to drag on ? > > Oh and did I miss anything in the above list ? I tired to compile EFL yesterday, had issues with Lua and EIO. The Lua issue is likely a problem at my end, but the EIO issue looked like a problem at your end. I might poke at that more later today. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world.
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
