On Sat, Dec 26, 2015 at 8:17 PM, Davide Andreoli <[email protected]> wrote: > Hi, > the python bindings are not elementary-only, but do not cover 100% of the > efl api for various reasons: > 1. lots of the efl stuff are not needed in py (Efreet is an example, as > python-xdg yet cover that area) > 2. lacks of dev time (Eio is an example here) > > So if you choose python for your filemanager you will need to do the > filesystem operations in a thread, > as you don't have access to Eio. > Here you can find some inspiration: > https://github.com/DaveMDS/epymc/blob/master/epymc/plugins/filemanager/filemanager.py > this is a 2 panes filemanager plugin for the epymc mediacenter, written in > python-efl using threads.
That is super-cool, thanx! > Choosing the language to use in your case is not an easy choice, at the end > I would say: > > * If your goal is to play/learn with the efl and have something work in a > short time go for the python > way, python is a lots simpler than C, and the python-efl documentation are > better then the C one. > > * If, instead, you plan to end up with a "serious" filemanager I would > choose C, mainly for > speed reason, C is around 30 times faster than python. And a filemanager > really need to be > as fast as possible. Hm, I'm not sure that file manager will be affected much. All the python IO is probably implemented in low level, UI operations are again in C, so it's mostly good threading model (backgrounding of heavy operations) and sorting that will be done on python side, so should not be a big deal. I am, however, worried that using python may result in unholy mixture of API styles and python-native-python invocations, but maybe that's just psychological trauma after debugging QtJambi segfaults. Regards, Stanislav ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
