On Sun, 24 Jan 2010 00:02 +0100, Vincent Torri wrote : > > to summarize: > > * ecore_txt moved in eina
I think we'll just have to agree to disagree here :) > * ecore_job merged in ecore I've made a patch doing this. > * nothing done for ecore_file (raster wants it in ecore) Do you mean ecore_input here ? > > I would like ecore_input_evas being not merged into ecore_input. The > reason is that if so, ecore_input depends on evas. As ecore_x and > other graphic subsystems depends on ecore_input, that would mean > that ecore_x would then depend on evas, which is not good. Merging ecopre_input_evas into ecore_input is not the question. I'm more curious about merging ecore_input in ecore. Since englebass split the evas-specific parts out, it means that ecore_input is basically a handful functions only relying on ecore. Hence, I don't see any clear rationale as to why we should keep it separate. Regards, -- Albin Tonnerre ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
