Diego wrote:
> 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
>
This may seem like a nice addition to evas.. but it's really
not a good way to go about it (nor are the particular api functions
added or internal engine functions particularly desirable).
Evas needs better vgfx support overall, and that means that
certain kinds of objects like lines, rectangles, polygons,... should
support stroke and/or fill properties - including such things as stroke
weight(s) as you want here for lines.
To do this correctly, and satisfactorily, needs a lot of work -
something like this right now, while well-intentioned, is really not
advisable.. This is not a trivial gfx aspect to support well.
As far as an api goes, one should be able to set stroke and fill
colors and/or textures on an object, wether an object should be stroked
and/or filled (if possible), and various stroke properties such as
weight(s), cap/join styles, etc. Of course one could cut down the set
of things one may want evas to support - it's not necessary to have
full support for everything.
If you're interested in really looking into adding such vgfx
capabilities to evas you could check out various polygon rasterization
implementations and polygon-stroking approaches. Maybe consult with
Jorge (turran) as he's been doing some work on aa polygon rasterization.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
