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 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: 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 TARGET="_blank" ) to make it easier for my 'authors' to get it right. Turns out this isn't *just* a convenience - regular Markdown has *no way* to specify a link that opens in a new tab. In fact, Markdown doesn't allow spaces in the URI, so you can't even type it out longhand. Since many, or even most, of the links in articles on my site will want to open in new tabs, it's out of the question to do without that - so mergMarkdownToXHTML isn't going to work. So - I'm back to my own converter which will undoubtedly get a few more features added in the next week or so, so I'll post the final version (or a link to it) when I think I'm done. -- Alex. On 05/11/2017 20:40, Kay C Lan via use-livecode wrote: 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 James could enlighten us. Now all I need is someone to tell me there is similar function that converts HTML (or more specifically the LC subset of HTML used by Fields) to Markdown otherwise I too will be reading more about Markdown (thanks for the link) and learning something new. ___ 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 ___ 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
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 ;-) ___ 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
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, keyframes, etc. 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
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. Landman Gay via use-livecode < > use-livecode@lists.runrev.com> 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. > > Hmm… I’m not sure if Mark will change his mind on synonyms even given > death threats ;-) > > I like canvas too though. One nice thing is I feel it gives more scope for > interactive elements than picture does. > > Cheers > > Monte > ___ > 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 ___ 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'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, 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 that if I kill Mark my career will be cut short. I have to think about that. Hmm… I’m not sure if Mark will change his mind on synonyms even given death threats ;-) I like canvas too though. One nice thing is I feel it gives more scope for interactive elements than picture does. Cheers Monte ___ 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 ___ 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 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 short. I have to think about that. Hmm… I’m not sure if Mark will change his mind on synonyms even given death threats ;-) I like canvas too though. One nice thing is I feel it gives more scope for interactive elements than picture does. Cheers Monte ___ 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: 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 James could enlighten us. Now all I need is someone to tell me there is similar function that converts HTML (or more specifically the LC subset of HTML used by Fields) to Markdown otherwise I too will be reading more about Markdown (thanks for the link) and learning something new. ___ 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
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 about that. ___ 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 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 | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ 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 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 ___ 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
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 about figure, in the way it is used in presenting visual information in books/articles etc then a figure can contain all sorts of visual elements, graphics, drawings, images, text, whatever. Terry... On 5/11/2017 11:19 pm, "use-livecode on behalf of Mark Waddingham via use-livecode" wrote: 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'? ___ 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
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 have (especially as it sounds like what Mark has done to to create a ‘superImage’ / ‘superGraphic’ control (I know there is more to it than that, but for me this is what stands out as new) In much the same way that ‘trueWord’ joined ‘word’ we could have ‘uniImage’ or ‘trueImage’ (or ‘uniGraphic’ or ‘trueGraphic’) - this will keep the number of control names down as a low as possible and won’t break anything in old code Kind regards Dave ___ 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 ___ 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
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’ control (I know there is more to it than that, but for me this is what stands out as new) In much the same way that ‘trueWord’ joined ‘word’ we could have ‘uniImage’ or ‘trueImage’ (or ‘uniGraphic’ or ‘trueGraphic’) - this will keep the number of control names down as a low as possible and won’t break anything in old code Kind regards Dave ___ 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
@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 it is more obvious to people who don't work with a particular feature frequently. On Sun, Nov 5, 2017 at 9:15 AM, hh via use-livecode < use-livecode@lists.runrev.com> 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, > 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 container.] > > @Mark. > > But I think, the interesting thing is not the name (call it as you > like it) but the direction of your path, the content of the object. > Let's talk about that. > > Will it be possible to edit properties: > > Getting and setting the points of a graphic? > Getting and setting the imagedata of a placed image? > Getting and setting the specific data of an SVG? > > Can it be used for exactly one of the objects or also a mix of the > three, say an SVGicon on top of an image? > > For example: > A lot of people are not able to write SVG, they are simply copying > out of programs like 'inkscape' and would like to paste the code > into a property of the control. Will that be possible? > > Who if not you knows that most of this (except the SVG part) is > already possible in LCB? > > For example my IconGrid widget has for each element > * a paint property (color) > * a text property (textsize, textfont settable) > * an image property (image scalable) > * a SVGIcon property (svg scalable). > > So, if you would extend the SVGIcon widget to a SVG_1.0 widget, we > could have all that without the need for a new container. > > ___ > 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 > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ 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
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 container.] @Mark. But I think, the interesting thing is not the name (call it as you like it) but the direction of your path, the content of the object. Let's talk about that. Will it be possible to edit properties: Getting and setting the points of a graphic? Getting and setting the imagedata of a placed image? Getting and setting the specific data of an SVG? Can it be used for exactly one of the objects or also a mix of the three, say an SVGicon on top of an image? For example: A lot of people are not able to write SVG, they are simply copying out of programs like 'inkscape' and would like to paste the code into a property of the control. Will that be possible? Who if not you knows that most of this (except the SVG part) is already possible in LCB? For example my IconGrid widget has for each element * a paint property (color) * a text property (textsize, textfont settable) * an image property (image scalable) * a SVGIcon property (svg scalable). So, if you would extend the SVGIcon widget to a SVG_1.0 widget, we could have all that without the need for a new container. ___ 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
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 subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
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 LiveCode Script. I'd be wary if the two notions - i.e. the Canvas type in LCB and the 'SomethingLikePicture' object in LCS - were unrelated, but they aren't. After all it is the Canvas type in LCB which provides the actual ability to render the commands which come out of processing an SVG file - the mapping from resulting attributed element (e.g. rect with paint and stroke attributes) is almost a 1-1 mapping from notion to canvas command and the plan is to make this completely 1-1. So, we can view the LCB Canvas Type as being a 'rasterization-only' target for SVG commands, whereas the LCS canvas object essentially records the commands and plays them back on demand. In fact, 'canvas' perhaps describes what the proposed object will actually be - it will allow you (from LCS) to describe a sequence of 2d vector graphics operations, which are then rendered on demand - essentially a deferred version of the LCB Canvas Type (essentially the 'canvas' script object would be a high-level wrapper around the LCB canvas type). Certainly the idea of being able to specify an image, or vector graphics, or a single graphic type to be drawn on a 'canvas' perhaps makes more sense than on a 'picture' (or other image-like synonyms). Warmest Regards, Mark. -- Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ LiveCode: Everyone can create apps ___ 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
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 "Image" or "Graphic" for a newcomer. The forum is full of synonyms that take a graphic for a bitmap and an image for a vector graphic. Why not call the new widget something like "Blackboard"? Or something like that. It conveys the notion that you can put all sort of things onto a blackboard, regardless of their internal representation. It alludes to the container for those things not the result of what is displayed. I like "Canvas" from LCB but unfortunately that is already taken. It would have been my favorite. Logically "Image", "Graphic" and "Picture" are all elements of a class of "visuals", but now "Image" and "Graphic" become elements of the class "Picture". It is a bit fuzzy what the difference in logical hierarchy is. A new term could prevent a possible confusion that "Picture" is a new logical class with said elements but at the same time a picture could be considered a member of class "Picture". Kind regards Bernd ___ 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 ___ 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 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 Mathewson via use-livecode < use-livecode@lists.runrev.com> wrote: > 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 "Image" or "Graphic" for a > newcomer. The forum is full of synonyms that take a graphic for a bitmap > and an image for a vector graphic. > > > > Why not call the new widget something like "Blackboard"? Or something > like that. It conveys the notion that you can put all sort of things onto a > blackboard, regardless of their internal representation. It alludes to the > container for those things not the result of what is displayed. > > > > I like "Canvas" from LCB but unfortunately that is already taken. It > would have been my favorite. > > > > Logically "Image", "Graphic" and "Picture" are all elements of a class > of "visuals", but now "Image" and "Graphic" become elements of the class > "Picture". > > > > It is a bit fuzzy what the difference in logical hierarchy is. A new > term could prevent a possible confusion that "Picture" is a new logical > class with said elements but at the same time a picture could be considered > a member of class "Picture". > > > > Kind regards > > Bernd > > ___ > > 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 > > ___ > 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 > ___ 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
