Re: The coming of SVG

On 1/5/18 9:03 AM, Mark Waddingham via use-livecode wrote: Take a look in the dictionary under drawingSvgCompile(). I just read this and, not being very familiar with SVG formats, I'm confused. Is there a way to use this to provide a larger hit region around an SVG? -- Jacqueline Landman

Re: The coming of SVG

Brilliant thanks Mark! :) Kind regards Dave - "The first 90% of the task takes 90% of the time, and the last 10% takes the other 90% of the time." Peter M. Brigham -- Sent from: http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html

Re: The coming of SVG

Thank you, Mark. This is bug report 20832. I included your response in the description. > On Jan 5, 2018, at 11:54 AM, Mark Waddingham via use-livecode > wrote: > > On 2018-01-05 17:21, Bleiler, Timothy via use-livecode wrote: >> I’ve been testing this a little

Re: The coming of SVG

On 2018-01-05 17:21, Bleiler, Timothy via use-livecode wrote: I’ve been testing this a little and I’ve run into some files that don’t render correctly. I’ve attached a simple example I found on the internet that contains this info about how it was created - Generator: Adobe Illustrator 22.0.1,

Re: The coming of SVG

Oops, I guess we can’t send attachments to the list. Here is a link to the file I tested. https://lovesvg.com/2018/01/cat-5169/ Tim Bleiler, Ph.D. Instructional Designer, HSIT University at Buffalo > On Jan 5, 2018, at 11:21 AM, Bleiler, Timothy via use-livecode >

Re: The coming of SVG

I’ve been testing this a little and I’ve run into some files that don’t render correctly. I’ve attached a simple example I found on the internet that contains this info about how it was created - Generator: Adobe Illustrator 22.0.1, SVG Export Plug-In . SVG Version: 6.00 Build 0). When I

Re: The coming of SVG

On 2018-01-05 15:58, Dave Kilroy via use-livecode wrote: Hi - anyone got news on 'VectorIcon' or whatever it's going to be called? I was thinking it would arrive with LC (dp11) but it didn't It did - but not in widget form. There is a script library which compiles an SVG file into a metafile

Re: The coming of SVG

he he - that should be "svg compiler" Dave - "The first 90% of the task takes 90% of the time, and the last 10% takes the other 90% of the time." Peter M. Brigham -- Sent from: http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html

Re: The coming of SVG

Hi - anyone got news on 'VectorIcon' or whatever it's going to be called? I was thinking it would arrive with LC (dp11) but it didn't When using Mark's external that he shared on LC Global I can get it working in the IDE but it's a no-show on an iOS device (amongst other errors I get "864,7,1

Re: The coming of SVG

On 2017-11-10 18:50, David Bovill via use-livecode wrote: I don't think this would help (below). What is nice is to be able to use professional illustration tools, and then add hypertext links to one of the objects in the svg with built in tools - for instance using Graphic, or OmniGraphl).

Re: The coming of SVG

On 2017-11-10 18:25, hh via use-livecode wrote: PLEASE, let us first have the basic enhanced object, probably "canvas". This will need at least a full year (my estimate). Well, let's first have the ability to display SVG :) My current approach (as I said previously) is to integrate SVG

Re: The coming of SVG

On 2017-11-10 19:02, hh via use-livecode wrote: @David. You respond to my answer for jbv (relating SVG-animation). The answer for you is two paragraphs upwards, a LC stack: http://forums.livecode.com/viewtopic.php?p=129274#p129274 The algorithm there allows you to get the clicked shape. That's

Re: The coming of SVG

@David. You respond to my answer for jbv (relating SVG-animation). The answer for you is two paragraphs upwards, a LC stack: http://forums.livecode.com/viewtopic.php?p=129274#p129274 The algorithm there allows you to get the clicked shape. That's all you need for setting clickregions of an image

Re: The coming of SVG

I don't think this would help (below). What is nice is to be able to use professional illustration tools, and then add hypertext links to one of the objects in the svg with built in tools - for instance using Graphic, or OmniGraphl). That way you can create complex beautiful (and scaleable)

Re: The coming of SVG

PLEASE, let us first have the basic enhanced object, probably "canvas". This will need at least a full year (my estimate). Then add other things (you can already now have via LC Script or via JavaScript in a browser widget): > David wrote: > It is realy hard with any technology other than SVG /

Re: The coming of SVG

On Fri, November 10, 2017 2:31 pm, David Bovill via use-livecode wrote: > Mark one of the most important applications of SVG / canvas object > implementation is the ability to create rich interactive graphics - not > simply imagery. Tools for animation of the svg graphics would be great too. SMIL

Re: The coming of SVG

Mark one of the most important applications of SVG / canvas object implementation is the ability to create rich interactive graphics - not simply imagery. It is realy hard with any technology other than SVG / Canvas to attach events or hypertext links to a complex area of an image. Using SVG's you

Re: The coming of SVG

@ Mark. Once again thanks for such a deep information. You are also a gifted teacher. I also know from writing kind of a canvas cheat sheet (WIP) that LCB canvas is already a larger set than HTML5 canvas but there are still a few important properties missing (some of them we can have from HTML5

Re: The coming of SVG

+1 vote for Viewer ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode

Re: The coming of SVG

On 2017-11-09 15:13, hh via use-livecode wrote: @Mark. You wrote several times "... the LCB canvas abilities ..., which are a superset of the HTML5 Canvas abilities" It is just now more "planned to be a superset"? The HTML5 canvas has for example the ability to set and get dataURLs. And LCB

Re: The coming of SVG

@Mark. You wrote several times "... the LCB canvas abilities ..., which are a superset of the HTML5 Canvas abilities" It is just now more "planned to be a superset"? The HTML5 canvas has for example the ability to set and get dataURLs. And LCB doesn't even have a base64 encoder/decoder.

Re: The coming of SVG

On 2017-11-08 18:47, Alejandro Tejada via use-livecode wrote: By the way, this new control is a LC9 only widget. Right? Yes - SVG abilities will initially appear (in some form) in 9. Warmest Regards, Mark. -- Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ LiveCode: Everyone

Re: The coming of SVG

On 2017-11-08 23:02, Mike Kerner via use-livecode wrote: I was just reading an article, this morning, about the trainwreck of new gestures to accommodate the X's lack of a home button, and I guess what the author was saying is pretty much what I'm trying to say: If it isn't obvious and easy,

Re: The coming of SVG

My $0.02 on the three leading candidates: "picture" -- gets my vote for this proposed object because we have decades of precedent well established with Apple's picture ('PICT') format, distinguished by the same thing that defines this new object: a type of image that can be comprised of

Re: The coming of SVG

Viewer +1 Jim Lambert ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode

Re: The coming of SVG

I was just reading an article, this morning, about the trainwreck of new gestures to accommodate the X's lack of a home button, and I guess what the author was saying is pretty much what I'm trying to say: If it isn't obvious and easy, then it's wrong. Keep the language on the level of what a

Re: The coming of SVG

Having followed this discussion from digest purgatory while on a conference trip, my vote is for “Viewer” as well. Viewer has these advantages: - not already a token in either LCS or LCB (that I know of) - is descriptive of what it does - is a nice parallel to player, a container for

Re: The coming of SVG

Martin Koob wrote: > what about calling it a *viewer* object which would then > allow us to view SVGs, images, graphics or any other > drawing or illustration format. Actually, I like the name "viewer" too, but if we could use the word "viewer" then "viewport" is more descriptive:

Re: The coming of SVG

I was thinking that to view movies or videos we user a *player* object not a movie or video object. So what about calling it a *viewer* object which would then allow us to view SVGs, images, graphics or any other drawing or illustration format. This way the name is not tied to the data type

Re: The coming of SVG

Hi all, long time not around, but clarity in language is a key point so my 2 cents : 1) I would much favor DRAWING versus image. The core differentation of a vector image is that it has been drawn versus "shot" by a camera for an image. That can be physically understood by all. The idea of a

Re: The coming of SVG

On 11/7/17 2:01 PM, Alex Tweedly via use-livecode wrote: On 07/11/2017 19:02, J. Landman Gay via use-livecode wrote: 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

Re: The coming of SVG

On 07/11/2017 19:02, J. Landman Gay via use-livecode wrote: 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

Re: The coming of SVG

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

Re: The coming of SVG

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

Re: The coming of SVG

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. On 7/11/17 5:31 pm, Bob Sneidar via use-livecode wrote: +1 for vector something or other. Bob S On Nov 6, 2017, at 15:35 , Stephen

Re: The coming of SVG

+1 for vector something or other. Bob S > On Nov 6, 2017, at 15:35 , Stephen Barncard via use-livecode > wrote: > > How about just plain vector? > > Or is that a parameter? ___ use-livecode mailing list

Re: The coming of SVG

How about just plain vector? Or is that a parameter? On Mon, Nov 6, 2017 at 13:04 sphere via use-livecode < use-livecode@lists.runrev.com> wrote: > I agree with Rick and Jacque. > Something combined with SVG or vector-image is better. > Anyone working with images knows (or learns very fast) what

Re: The coming of SVG

I agree with Rick and Jacque. Something combined with SVG or vector-image is better. Anyone working with images knows (or learns very fast) what svg's are. Picture is to much linked to Photo (for me it is the same), if you take a picture the result is a photo. I would not think for picture at all

Re: The coming of SVG

On 06/11/2017 16:52, Mark Waddingham via use-livecode wrote: In any case, introducing a new control (which is far more than an image) in the first instance doesn't stop it at some point 'feeling' like an image from the point of view of script in the future so it seems like a getting the

Re: The coming of SVG

On 2017-11-06 15:34, Ben Rubinstein via use-livecode wrote: This might be a stupid question, but might it be possible for this new control to completely replace the existing image control? It isn't a stupid question... There aren't very many special properties relating especially to images.

Re: The coming of SVG

I hope not, because I was thinking the same thing. One of those properties could be "type" or "class", and that could be "svg", for instance. On Mon, Nov 6, 2017 at 9:34 AM, Ben Rubinstein via use-livecode < use-livecode@lists.runrev.com> wrote: > This might be a stupid question, but might it

Re: The coming of SVG

This might be a stupid question, but might it be possible for this new control to completely replace the existing image control? There aren't very many special properties relating especially to images. If the new object implemented those at least to a first approximation, then perhaps it

Re: The coming of SVG

@Mark Thank you very much for that fine explanation. Hopefully the team and you will find enough time to implement the enhanced 'canvas' (whatever the name). ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to

Re: The coming of SVG

On 2017-11-05 15:15, hh via use-livecode wrote: Until now I saw it like that: , and are HTML5 tags. And and are different concepts. Roughly is more an XML-based vector graphics format, Yes - SVG is a way of encoding a sequence of vector graphics commands using XML. is more an API

Re: The coming of SVG

Maybe ‘raster’ as an anternative for ‘canvas’? Cheers, Erik On 05/11/17 22:06, "use-livecode on behalf of Richmond Mathewson via use-livecode" wrote: I'm not sure how the word "canvas" conjures up ideas

Re: The coming of SVG

On 2017-11-05 21:49, Monte Goulding via use-livecode wrote: On 6 Nov 2017, at 6:24 am, J. Landman Gay via use-livecode wrote: will stop Jacque killing Mark when there is no abbreviation If we go with "canvas" I expect "cv" or similar. :) It did occur to me

Re: The coming of SVG

From Wikipedia: The word "canvas" is derived from the 13th century Anglo-French canevaz and the Old French canevas. Both may be derivatives of the Vulgar Latin cannapaceus for "made of hemp," originating from the Greek κάνναβις (cannabis). So give it the synonyms hemp and cannabis -- if not joint

Re: The coming of SVG

FRAME would be good except it is already defined in the Livecode Dictionary as: 'One of the images in the sequence of images that makes up an animation or video.’ And there’s also framecount and framerate relating to animated GIFs. Presumably some video widgets would also refer to movie frames,

Re: The coming of SVG

https://www.w3schools.com/html/html5_canvas.asp "Canvas" could be confused with the html5 element of the same name. What with livecode deploying to html5 now... On 5 Nov 2017 8:49 pm, "Monte Goulding via use-livecode" < use-livecode@lists.runrev.com> wrote: > > > On 6 Nov 2017, at 6:24 am, J.

Re: The coming of SVG

I'm not sure how the word "canvas" conjures up ideas of interactivity. Interactive words: Playground Kitchen Chalkboard Tray Not, frankly, that any of the above would do. I'm still pushing svgImage although vImage (as in Vector + Image) might not be bad. Richmond. On 11/5/17 10:49 pm,

Re: The coming of SVG

> On 6 Nov 2017, at 6:24 am, J. Landman Gay via use-livecode > wrote: > >> will stop Jacque killing Mark when there is no >> abbreviation > > If we go with "canvas" I expect "cv" or similar. :) It did occur to me that > if I kill Mark my career will be cut

Re: The coming of SVG

Please consider it very carefully! Do not proceed until you have found a proper replacement. Tore > 5. nov. 2017 kl. 20:24 skrev J. Landman Gay via use-livecode > : > > It did occur to me that if I kill Mark my career will be cut short. I have to > think

Re: The coming of SVG

On 11/5/17 3:17 AM, Lagi Pittas via use-livecode wrote: will stop Jacque killing Mark when there is no abbreviation If we go with "canvas" I expect "cv" or similar. :) It did occur to me that if I kill Mark my career will be cut short. I have to think about that. -- Jacqueline Landman Gay

Re: The coming of SVG

On 11/5/17 6:19 AM, Mark Waddingham via use-livecode wrote: Hmmm - actually, why not 'canvas'? I like this. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___

Re: The coming of SVG

If not picture (or canvas) then another couple of names that might work and don’t have baggage associated with them are figure and drawing. I perhaps like the look/sound of drawing better but it doesn’t really capture the ability of the object to contain an image particularly well. If you think

Re: The coming of SVG

svgImage shortened to svgImg Richmond. On 11/5/17 5:46 pm, Dave Kilroy via use-livecode wrote: Hmm tricky this naming business isn’t it! My take on this is that it would be better to have a modifier for an existing control name rather than baptise a new control name to join what we already

Re: The coming of SVG

Hmm tricky this naming business isn’t it! My take on this is that it would be better to have a modifier for an existing control name rather than baptise a new control name to join what we already have (especially as it sounds like what Mark has done to to create a ‘superImage’ / ‘superGraphic’

Re: The coming of SVG

@mark when possible, I think it's better to keep the vocabulary simpler or more obvious in LC. It's one of the benefits of the environment and the tool - less mental effort around the tool and the language. When possible, I think it's better to make it obvious to non-nerds, which will also mean

Re: The coming of SVG

Until now I saw it like that: , and are HTML5 tags. And and are different concepts. Roughly is more an XML-based vector graphics format, is more an API for drawing on a bitmap surface. And is a container for an image at different sizes. [And, as James says, is also a (different) HTML

Re: The coming of SVG

Between Bernd’s post and Richard’s I too thought of frame but then discounted (reluctantly) as it has a specific meaning in html which could also be confusing. James ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to

Re: The coming of SVG

On 2017-11-05 00:59, Niggemann, Bernd via use-livecode wrote: I like "Canvas" from LCB but unfortunately that is already taken. It would have been my favorite. Hmmm - actually, why not 'canvas'? Certainly there is a Canvas type in LiveCode Builder, but the 'canvas' idea hasn't been used in

Re: The coming of SVG

Frame Richmond. On 11/5/17 1:59 am, Niggemann, Bernd via use-livecode wrote: for me "Picture" is a bit confusing. We have "Image" for bitmaps, "Graphic" for vector graphics of a certain type and now we might have "Picture" for all kinds of elements. However "Picture" is easily confused with

Re: The coming of SVG

I was going for PICTURE but now I think Richmond’s FRAME is better. It takes into account the newbies, encompasses the same thought process as Bernd’s BLACKBOARD and will stop Jacque killing Mark when there is no abbreviation, because BLACK is taken. Lagi On Sun, 5 Nov 2017 at 08:53, Richmond

Re: The coming of SVG

for me "Picture" is a bit confusing. We have "Image" for bitmaps, "Graphic" for vector graphics of a certain type and now we might have "Picture" for all kinds of elements. However "Picture" is easily confused with "Image" or "Graphic" for a newcomer. The forum is full of synonyms that take a

Re: The coming of SVG

What about: wad (also honouring the main author of the new "container") on mouseUp if there is no wad "w_1" then create wad "w_1" put image "img_1" into wad "w_0" put graphic "grc_1" onto back of wad "w_1" put svgicon "svg_1" onto front of wad "w_1" end if end

Re: The coming of SVG

Of the alternatives presented “picture” gets my vote. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

Re: The coming of SVG

Humph: when I was 32 and using a Mac Performa 475 SuperPaint was a "not so super" program for doing things that by today's standards look largely like a complete and utter waste of time. I don't know what the new "SVG" thang should called, and I am slobbering in excitement at the thought of

Re: The coming of SVG

The issue with art is that anything that I do will automatically be relabeled "areYouKiddingThatIsNotArt", and abbreviated "thatIsSoNotArt", with a synonym "hahahahahahahahahahahahahahahahahahaha" On Sat, Nov 4, 2017 at 2:34 AM, Richard Gaskin via use-livecode < use-livecode@lists.runrev.com>

Re: The coming of SVG

Alejandro Tejada wrote: > By the way, this new control type, Could allow easier implementation > of image libraries, where you store a single instance of a bitmap > or graphic and then LiveCode engine just rebuild your picture > from the original data applying all transformation or changes >

The coming of SVG

Jim Lambert wrote: > I like Mark's ‘picture' because it is general. A picture can contain > both vectors and bitmaps. Richard Gaskin wrote: > Seconded. When I first read Mark's post I was wary of "picture", > but on further reflection I remembered Apple's PICT file/data type, > distinct from

Re: The coming of SVG

On Sat, Nov 4, 2017 at 7:19 AM, hh via use-livecode wrote: > > Probably we could call it "artwork"? > (If all the promises realise it is indeed a software artwork!) Beat me to it. But considering LC takes the hard work out of cross platform programing. And

Re: The coming of SVG

Actually, any button using an image/icon should have a scale and alternately a position, like when you set a picture for a web avatar. But that may be asking too much. A scale percentage would be great! I usually import the image, set it's scale, lock it's location, and then the buttons that

Re: The coming of SVG

Jim Lambert wrote: > I like Mark's ‘picture' because it is general. A picture can contain > both vectors and bitmaps. Seconded. When I first read Mark's post I was wary of "picture", but on further reflection I remembered Apple's PICT file/data type, distinct from PNTG as the latter was

Re: The coming of SVG

I like Mark's ‘picture' because it is general. A picture can contain both vectors and bitmaps. Any word with ‘icon’ in it seems overly specific as does ’SVG’-anything; while ‘vectorimage’ implies an image made up of vectors. set the filename of pct 1 to ‘blah blah.blah’ Jim Lambert

Re: The coming of SVG

Oh you 'nix people. Okay, "vct" then. ;) Mark doesn't like abbreviations. We're at his mercy. On 11/3/17 3:16 PM, Mike Kerner via use-livecode wrote: Please, not "vi" On Fri, Nov 3, 2017 at 4:14 PM, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: On 11/3/17 1:41 PM,

Re: The coming of SVG

> At least historically, paintings were bitmapped, > not vector (think MacPaint vs. MacDraw) Yes. And LCB "draws" an image and uses "OnPaint" for it's canvas. Probably we could call it "artwork"? (If all the promises realise it is indeed a software artwork!)

Re: The coming of SVG

Please, not "vi" On Fri, Nov 3, 2017 at 4:14 PM, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > On 11/3/17 1:41 PM, Mark Waddingham via use-livecode wrote: > >> As I said one of the goals of this control would eventually be to replace >> the image object - so at some

Re: The coming of SVG

On 11/3/17 1:41 PM, Mark Waddingham via use-livecode wrote: As I said one of the goals of this control would eventually be to replace the image object - so at some point (all being well) you will be able to do:   set the filename of "foo" to "foo.png"   set the filename of "foo" to

Re: The coming of SVG

Universal Image Object uni-Image imagePak UIO imageBlob imagepack imageContainer quicktime... (oh, wait..) how about imageData ... has been used yes but base the 'thing' on that ...add the options -- Stephen Barncard - Sebastopol Ca. USA - mixstream.org On Fri, Nov 3, 2017 at 12:49 PM,

Re: The coming of SVG

At least historically, paintings were bitmapped, not vector (think MacPaint vs. MacDraw) On Fri, Nov 3, 2017 at 3:40 PM, hh via use-livecode < use-livecode@lists.runrev.com> wrote: > Look forward to the first release of . > > For the name, what about "painting"? > >

Re: The coming of SVG

Look forward to the first release of . For the name, what about "painting"? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

Re: The coming of SVG

On 2017-11-03 19:33, Rick Harrison via use-livecode wrote: I like “vectorImage” too! “Picture" has been used for images for a long time, and we don’t want to add more confusion for users. Where do you think the confusion would come from? As I said one of the goals of this control would

Re: The coming of SVG

On 2017-11-03 19:02, Bleiler, Timothy via use-livecode wrote: This is good news!! Is there any reason not to call the control “SVG?” Three main reasons: - SVG is a somewhat human-unfriendly term - SVG is technically a vector graphics interchange format (and so an adjective, not a noun

Re: The coming of SVG

I like “vectorImage” too! “Picture" has been used for images for a long time, and we don’t want to add more confusion for users. Just my 2 cents.. Rick > On Nov 3, 2017, at 2:23 PM, J. Landman Gay via use-livecode > wrote: > > Or maybe "vectorImage".

The coming of SVG

Mark Waddingham wrote: > we are now firmly on the road to full SVG support in LiveCode! These are great good news! Congratulations. :-D > the name is currently vectoricon Actually, I like the name "Picture" because it remembers me about the PICT file format that could include bitmaps, vectors

Re: The coming of SVG

On 11/3/17 1:12 PM, J. Landman Gay via use-livecode wrote: On 11/3/17 11:05 AM, Mark Waddingham via use-livecode wrote: the name is currently vectoricon To be honest, I like this better than "picture". It's more descriptive. Or maybe "vectorImage". -- Jacqueline Landman Gay |

Re: The coming of SVG

SVG's are not just standalone objects. They are also part of various widgets. On Fri, Nov 3, 2017 at 2:02 PM, Bleiler, Timothy via use-livecode < use-livecode@lists.runrev.com> wrote: > This is good news!! > > Is there any reason not to call the control “SVG?” > Why create another abstraction

Re: The coming of SVG

On 11/3/17 11:05 AM, Mark Waddingham via use-livecode wrote: the name is currently vectoricon To be honest, I like this better than "picture". It's more descriptive. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software |

Re: The coming of SVG

This is good news!! Is there any reason not to call the control “SVG?” Why create another abstraction in the name from what the control actually is? e.g. Set the fileName of SVG “My Picture” to …. Tim Bleiler, Ph.D. Instructional Designer, HSIT University at Buffalo > On Nov 3, 2017, at

Re: The coming of SVG

Hi Mark > Am 03.11.2017 um 14:19 schrieb Mark Waddingham via use-livecode > : > > Hi all, > > My most recent talk at LCG (in October) was 'Building an SVG Widget' and in > order to talk about such a thing, I needed to actually build one - so I did :) > > So, we

Re: The coming of SVG

On 2017-11-03 14:19, Mark Waddingham via use-livecode wrote: Hi all, My most recent talk at LCG (in October) was 'Building an SVG Widget' and in order to talk about such a thing, I needed to actually build one - so I did :) So, we are now firmly on the road to full SVG support in LiveCode!

Re: The coming of SVG

This is great news! Bill William Prothero http://es.earthednet.org > On Nov 3, 2017, at 8:18 AM, Mike Kerner via use-livecode > wrote: > > OOOH. Cool. So pretty soon maybe I can render interfaces in Sketch > after applying themes from my favorite interface

Re: The coming of SVG

OOOH. Cool. So pretty soon maybe I can render interfaces in Sketch after applying themes from my favorite interface design houses... On Fri, Nov 3, 2017 at 9:19 AM, Mark Waddingham via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi all, > > My most recent talk at LCG (in

The coming of SVG

Hi all, My most recent talk at LCG (in October) was 'Building an SVG Widget' and in order to talk about such a thing, I needed to actually build one - so I did :) So, we are now firmly on the road to full SVG support in LiveCode! At the moment the implementation only supports geometric