On Fri, 29 Jul 2016 08:22:51 +0900 Carsten Haitzler (The Rasterman) <[email protected]> wrote:
> On Thu, 28 Jul 2016 14:55:46 -0700 Cedric BAIL <[email protected]> > said: > > > Hello, > > > > I came to realize that splitting this 3 components don't really make > > any more sense. If you want to build anything on top of efl, you are > > i totally agree. in fact if we are going to merge... we should do a > lot more merging. we need to decide on a future much smaller set of > libraries > > e.g. (lib* assumed) > > efl: > eina, eo, ecore, efl, eio > > eflgui: > evas, edje, emotion, elementary, ector, ecore_audio, ecore_imf, > ecore_imf_evas, ecore_input > > eflnet: > ecore_con, ecore_ipc, eldbus, ecore_avahi > > eflsys: > ecore_file, efreet, efreet_mime, efreet_trash, elocation > > others left over to figure out... > ephysics, eet, elua, embryo, eolian, ethumb, ethumb_client > > and definitely unportable or dubiously universal lib api's: > eeze, ecore_drm, ecore_drm2, ecore_buffer, ecore_cocoa, ecore_fb, > ecore_psl1ght, ecore_sdl, ecore_wayland, ecore_wl2, ecore_win32, > ecore_x, elput, escape, evil I think you left out evas_3D, though I'm beginning to suspect I'm the only major user of that outside of Samsung. Cedric mentioned that I might be. Eet should be part of the efl library, it's a basic part of the system, the data format used by most everything else. Eolian is basically part of eo, it could join it in efl. On the other hand, it's more a tool than a library? Embryo should be elfgui, it's all about GUI stuff, and again a basic part of the system used everywhere. Ethumb and ethumb_client also could be part of eflgui, since ecore_audio is. Evas_3D probably belongs in eflgui as well, and I understand there may be some linking of evas_3D and ephysics at some stage, so they might go together. The unportable ones could all get lumped into a portability library, though obviously not all at the same time. B-) Eeze in eflsys maybe? Elua I haven't played with yet, it was lacking docs and examples last time I looked, and I didn't have the time to grok the source code. So not sure where it belongs. I don't even know what elput is. You are probably well aware of my thoughts about efreet, so I wont mention where I think it belongs. lol On the other hand, your suggested tactic for those of us that need to squeeze the libraries down to a bare minimum set, is to build the lot, but don't actually install the ones not needed. This merge idea makes that all but impossible I think. We may need to rethink that tactic. Though my main need for that is in an embedded project that's going to stick with an older version of EFL, but I recall there where other people with that issue. -- 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
------------------------------------------------------------------------------
_______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
