On Tue, 7 Sep 2010, Vincent Torri wrote:
>> I'd say do the app now, otherwise we'll end with yet another library >> with an associated application to use... :-/ >> >> As Vincent said, the API is quite similar, so pick one like epdf and >> do the app. Once it's okay, you can write the abstraction with similar >> api and sed the code. >> >> During the process you may find some API being "wrong" or "unhelpful", >> maybe require more API and you have to change a single place. The >> other approach you'd have to change 3 + 1 places. Then if you notice >> it is wrong, you go and change that amount again, etc. > > actually, there is something to check in epdf : is the API sufficient for > having a responsive gui like evince (a part with the rendered page and on the > left, a list of thumbnails of the pdf document which can scroll). The > rendering can take a lot of time, even if it is possible to zoom) when I say "zoom", I mean the ones provided by the document library, not evas' one. Vincent ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
