From: Carsten H. (T. R. <ra...@ra...> - 2010-01-23 07:28:51
|
On Sat, 23 Jan 2010 02:11:59 -0500 Jose Gonzalez <jos...@ju...> said: > Carsten wrote: > > > On Sat, 23 Jan 2010 00:58:26 +0100 Peter Wehrfritz <pet...@we...> > > said: > > > >> Albin Tonnerre wrote: > >> > >>> On Fri, 22 Jan 2010 23:19 +0100, Vincent Torri wrote : > >>> > >>> > >>>> why not moving ecore_txt to eina, btw ? > >>>> > >>>> > >>> As far as I understand it, eina is about providing data types. IMHO > >>> neither ecore_str nor ecore_txt fit in that category. > >>> > >>> > >> Right, nor does ecore_file, but it seems that the tendency is to put > >> everything into to eina which could be used by ecore and evas. > >> > > > > 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 -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... |