> But why didn't we just put eina inside the libs cvs directory (svn > checkout http://efl-research.googlecode.com/svn/trunk/eina eina). And > start hacking from here. We can then slowly switch evas , ecore and > eet to the data type eina provide or the one we add to eina. It should > be easier to start from something with code and hack than agree on > what we should put in. But if you are going to do the work, I will > agree and help on this project as it's something we need to do.
there is already an 'edata' in e17/proto, btw Vincent ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
