On 19/06/14 14:18, Daniel Kolesa wrote: > 2014-06-19 14:02 GMT+01:00 Tom Hacohen <tom.haco...@samsung.com>: > >> Hey, >> >> I'm sending this mail to get people up to date regarding what >> JackDanielZ and I have been working on (mostly chatting about it and >> building the needed infra) the last few months, and what we will >> actually be working on during the weeks to come. >> >> We are working on the Eo EFL API, making it clean, consistent, and >> predictable. This work covers sharing similar interfaces among similar >> classes all over the EFL, adding Eo API to things that are not covered >> by Eo at the moment and should be, and probably in the future also >> fixing some broken API we might have lingering around. >> >> I've created a short wiki page with a bird's eye on what's coming. You >> can find it here: >> https://phab.enlightenment.org/w/efl_interfaces/ >> >> Please let me know if you have any questions or comments about this change. >> > > It's pretty clear that we need something like this. But I fear that having > lots of "global" efl_ prefixed funcs will lead to interface creep, not > something we necessarily need; also, it means we'll have to split these > into many different interfaces - we will want to categorize these somehow, > instead of shoving everything into one. > > This is all something that we need to think about...
It actually isn't obvious from my email, but the interface is named: "efl_file" and the property is "file" (file_set). Normally it would have been generated as efl_file_file_set, but we have a thing in eolian that removes the redundant duplication so it becomes efl_file_set. They will be split to many interfaces, you'll have a file interface, a text interface and etc. Categorizing them is part of the process, and I'll be sending .eo files to the ML as we go to show the splits and ask for feedback. This email is more of a "get ready to give some feedback soon". :) ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
