On 17/06/14 20:25, Cedric BAIL wrote: > Hello, > > So I did just a very quick high level review for now and the following > is just my opinion. But I do think it makes more sense to have what > you name emodel be part of either Eo directly or a new Efl library as > it should be a core object like we do plan to do with other core > object like color, text, ... If it become Eo_Model or Efl_Model > (Raster a preference ?), then EModel_Eio, I think, should move and be > part of Eio directly (and become Eio_Model). > > On the same topic I think there is a small potential and logical to > have an elm_view top object that will provide model_get/set that are > in common between Elm_View_List and Elm_View_Form. > > I will give a better look at the code later this week. >
I'll have to take a look at Emodel to see exactly if it's eo or efl material. Without looking, I'm leaning more towards efl, as this is where we are going to put the shared base at, and I'd like to keep eo is clean and small as possible. I haven't looked at the code at all yet. -- Tom. ------------------------------------------------------------------------------ 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