On Tue, 20 May 2008 10:14:48 -0300 "Diego Bitencourt Contezini" <[EMAIL PROTECTED]> babbled:
hmm. i'd rather hold here in favor of a much more... expansive set of vgfx support... and nail this kind of thing all in one shot. > We decided to improve the line implementation to speed up the use of > evas-lines in python (our case). Yes, we could just use polygons, but we are > trying to reduce processor usage at this point. > Its faster to draw lines (with lines implementation) directly, specially > dealing with vertical/horizontal/45 deg. lines. > Calculating where points of polygons must be drawn relative to width of line > in python-side is a lost of processing too. > > Being faster, simpler and without breaking any compatibility, I dont know > why Lines should not to have width support. Specially thinking about how > simpler it makes to work with Lines. > Yes, the code may be optimized, but its working fine and fast here. > > Greetings, > > Diego B. Contezini > > On Sun, May 18, 2008 at 11:51 PM, The Rasterman Carsten Haitzler < > [EMAIL PROTECTED]> wrote: > > > On Tue, 13 May 2008 17:20:27 -0300 "Diego Bitencourt Contezini" > > <[EMAIL PROTECTED]> babbled: > > > > any reason you didnt just use polygons? :) > > > > > Hello all. > > > Working with evas+Lines in python, is fast. But if you need a line with > > more > > > then one pixel of width, it gets very slow (in dispositives like N800), > > > because object Line dont have width support, so its needen to use > > Rectangles > > > to make it works. > > > > > > I made a modification to support width in Lines object. It is composed by > > 3 > > > patchs. > > > *First*, in evas/lib/*, it changes internal call to engine line drawer, > > > inserting more one argument to the same function. It is a callback, so, > > no > > > modification is needen in any engine module that dosnt support Lines with > > > more then 1 pixel (they will just draw with only 1 pixel). Has added new > > > functions to deal with width, without breaking any compatibility of other > > > functions. > > > *Second*, in evas/engine/software16 to add support to width. > > > *Third,* in python-evas binding, to add support to use the modifications > > > made in evas. > > > > > > If anyone get any bug or suggest any modification to patch, im a > > listener. > > > > > > Thanks all > > > > > > Diego Bitencourt Contezini > > > > > > > > > -- > > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > > The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] > > > > > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
