Refactor Ecore.Exe to EFL.Exe
Open, Showstopper IssuesPublic

Description

Within Efl_Core this Exe namespace should be moved out of Ecore

whenever doing this, *PLEASE* use Efl.Io interfaces, so it's similar everywhere (ie: API will be mostly the same as the one for Efl.Net), namely Efl.Io.Reader, Efl.Io.Closer and the likes. For UNIX, you can benefit from Efl.Io.Reader.Fd and similar, not sure how is that on Windows.

With that, you only need the basics: monitor for incoming data and when writes can be done without blocking, as well as monitor child exit. Buffering and high level operations should be done by the existing Efl.Io.Copier and Efl.Io.BufferedStream

ajwillia.ms renamed this task from Refactor Ecore.Exe to EFl.Exe to Refactor Ecore.Exe to EFL.Exe.Nov 29 2017, 5:37 AM
bu5hm4n added a project: Restricted Project.Jun 10 2018, 10:54 AM
zmike edited projects, added Restricted Project; removed efl.Jun 11 2018, 6:51 AM
bu5hm4n edited projects, added efl: system integration, Restricted Project; removed Restricted Project, Restricted Project.Jun 11 2018, 7:19 AM

@ajwillia.ms @zmike Can I have more information on the purpose of this task? As it is written now, I do not understand what needs to be done.

There currently exist efl_exe.eo and ecore_exe.eo classes but their relationship is not readily apparent.

A #Goal ticket should not be set to a milestone.