Android Studio 3.0

Android Studio 3.0 is now a stable release, and *finally* fully supports Kotlin. https://android-developers.googleblog.com/2017/10/android-studio-30.html -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list

Re: Markdown ultra-lite

Well, just for completeness, I'll report that I have decided to use my own simple-minded version rather than mergMarkdownToXHTML. I had added one tiny convenience feature (a trailing "*" in a URL would be converted to make the link open in a new browser tab/window - by changing it to 

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: Markdown ultra-lite

On Sun, Nov 5, 2017 at 1:39 AM, Alex Tweedly via use-livecode wrote: > > (*) I read about Markdown; it was interesting; I learned something - no > hours were truly "wasted" > Nor was I aware that mergMardownToXHMTL existed, so thank you for raising this thread so

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