On Thu, 23 Aug 2007 08:19:51 +1000, David Seikel wrote: Thanks, Kim and David:
>> > Am I missing something obvious or is this not a workable combination. >> > >> Um... e16 should be compatible with just about anything, but engage >> seems to be "somewhat less functional" than it has been. > > EFL APIs move on, but engage has no maintenance being done. So it sits > and it's bits rot. > It's such a shame because engage really had super qualities and appeal. You're right about the APIs David. But on the cvs logs, I saw some minor action in cvs several weeks ago. Not enough though to make it work right. (or because I did not have enough information to make it work right due to lack of doc). IMVHO, marrying a product to a particular OS or WM is a poor choice. Making engage only compatible with E17 as a module and forsaking standalone is a shame. I think that if engage standalone is to survive, it will have to fork off the existing modular project and become independent. Next, it will have to have a standardized, non-eap-style, method of accessing programs and objects. .desktop files are so small as are most png files, there's no point to package them. Anyway, thanks for preventing me from beating my head against a wall (for now, anyway). :) -- Peter ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
