Christopher Michael wrote: > I've been reading through the efreet code and it's not too shabby, so > big (insert your favorite type) cookie to the authors there :) but > before I jump head first into this porting nightmare I have a few > remaining questions.... > > 1) Is it really worth the effort to port all this efreet code into > ecore_desktop, just to be pulling it out at a later date when ecore gets > broken apart ??
I'd prefer keeping it out of ecore, but its been decided that that's where it's to go. > > 2) Am I correct in assuming that we still want to keep the > ecore_desktop_some_function calls and just replace the code inside with > efreet code ?? (with #ifdef NEW_CODE blocking of course..ie: we still > would have ecore_desktop_some_func, just that it would run efreet code) > I'd prefer if you keep the efreet naming and just s/efreet/ecore_desktop/g. We put some thought into the APIs and think they came out pretty good. (Unless we got the words around backwards for the typical ecore naming, then swap them around.) dan ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
