>>>> ......... >>>> >>> how is "putting everything in ecore" and moving "everything to eina" any >>> better? you're just shuffling pile of paper from desk a to desk b. >>> >>> >> Ummm, generally that would seem pointless indeed... But there are issues >> of dependencies to consider here besides just mere moving of things from one >> place to another. >> For a variety of things, especially things you might want to use eg. in >> evas itself, having them in ecore is problematic. In general, I'd say that if >> there's a chance that some functionality could be useful in evas, or in apps >> that might not depend on evas, then those things should not be in ecore - not >> so long as ecore itself depends on evas. >> > > yes - thats true, though only because of ecore-evas/ecore-evas-input >
BTW, besides ecore_evas and ecore_input_evas, there is also ecore_imf_evas, and even ecore_config has in its public header the inclusion of Evas.h - which is needed there for one function: EAPI int ecore_config_evas_font_path_apply(Evas *evas); There could be more, haven't checked... this is just something I remember being there from sometime back. If ecore had been split along the lines of an ecore_base and ecore_ui say, then not only would many of these wacky 'dependency issues' have been avoided, but it's possible that things like the Ecore_Evas data structure wouldn't have been needed at all since conceivably the functionality expressed via that could have been made part of evas itself (as evas could then have used ecore_base/ui). ____________________________________________________________ Banking Click here to find the perfect banking opportunity! http://thirdpartyoffers.juno.com/TGL2141/c?cp=pEV9GUX4KqsL2CSC2aDleQAAJ1CE1nexA7BxlOpTpVzzI1I8AAYAAAAAAAAAAAAAAAAAAADNAAAAAAAAAAAAAAAAAAAXeAAAAAA= ------------------------------------------------------------------------------ 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
