The coming of SVG

J. Landman Gay jacque at
Tue Nov 7 14:02:36 EST 2017

I believe the objection to using "vector" is because the object isn't 
going to contain only vector graphics. Eventually it will be a 
representation of many different image formats, a sort of catch-all that 
will replace all the existing bitmap and vector controls in the future.

On 11/7/17 12:23 PM, Stephen Barncard via use-livecode wrote:
> Well,  the word vector is not to be found anywhere in the dictionary.
> *vectorImage*  (we already have newImage and deleteImage messages, and
> several properties begin with *image*
> *imageVector*  (we already have imageSource imageData and imagePixmapID
> *vectorRender*
> somehow function and command names look far more important in a classic
> boldface serif font.
> --
> Stephen Barncard - Sebastopol Ca. USA -
> On Tue, Nov 7, 2017 at 10:05 AM, Richmond Mathewson via use-livecode <
> use-livecode at> wrote:
>> I have a feeling the name should be one word, probably in camel format,
>> so that has to be
>> vectorSomethingOrOther
>> shartened, presumably, to vSOO
>> Richmond.

Jacqueline Landman Gay         |     jacque at
HyperActive Software           |

More information about the use-livecode mailing list