Vector Images and the SVGL stack

Scott Rossi scott at tactilemedia.com
Wed Nov 11 05:24:20 EST 2015


On 11/11/15, 1:00 AM, "use-livecode on behalf of Alejandro Tejada"
<use-livecode-bounces at lists.runrev.com on behalf of
capellan2000 at gmail.com> wrote:


>Please, notice the following: Livecode vector graphics only use integer
>(1,2,3,4,5...) for displaying graphics strokes (borders). This limitation
>could be a barrier to import and display faithfully many professional
>illustrations created or exported to SVG format.


Unfortunately, this is quite true, and relates to the same issue mentioned
by Richard Gaskin the other day:

> The difference between a true Bezier object and emulating Beziers with
> polygons is resolution.  Polygons can be made to like very good on
> screen, but cannot be made to resize larger, or print to a printer with
> higher resolution than the monitor, with the same smoothness as a true
> Bezier curve object.


Currently, the point system of LiveCode's default graphics is based on
full 1-pixel units, which limits the degree of subtlety that can be
applied to a graphic.  Until the "shape" object materializes and/or bezier
curves, it isn't possible to create a graphic with smooth articulated
curves that scales well to any size.  And even then, only LiveCode 8 and
later will be able to take advantage of it.


For the moment, one workaround is to display a graphic at a large size,
snapshot it as an image, and reduce the image down using "good" or "best"
resizeQuality.  While this can make for a decent looking object, it
defeats the purpose of using a graphic in the first place.

Regards,

Scott Rossi
Creative Director
Tactile Media, UX/UI Design






More information about the use-livecode mailing list