Hi all, i have added a couple of projects into proto: Ecore_Li: Its an ecore based abstraction for linux input devices, this code has part of the current ecore_fb code i did and other code that wasnt committed into ecore_fb, i prefer to have the input events away from ecore_fb, mainly because there are cases for which you wont need a framebuffer display (handling power/reset buttons on a daemon, webcam buttons under a graphical app in X, etc).
Enesim: Enesim it's a vector/raster pipeline, on the vector side you have components and readers of vector data, only two components are coded right now: source_csv (to read vector data from a file) and transform (to do matrix transformations to the vector data); other components like a bezier curves handling, contour, binary ops, etc are on the TODO. On the raster side you have renderers, scanlines, rasterizers and surfaces, note that there's no graphics context, you just plug the elements as you will and thats it. The context and objects (as seen on evas) can be built on top of the raster elements. In order to compile them you need edata, it's just a split of Ecore_Data from Ecore, but before adding it into CVS i would like your opinions about it, a while ago there was a discussion about splitting ecore in libraries by themselves, this should be step forward it, what do you think? Anyone who has interest in this projects feel free to contribute, discuss or ask =) regards, turran ------------------------------------------------------------------------- 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-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
