OT Re: Referencing Livecode

David V Glasgow dvglasgow at gmail.com
Tue Jun 21 06:42:01 EDT 2022


That is really helpful Alan.  A pair of fine papers!  

I visited Australia & NZ a few years back and started using iNaturalist and then the Seek <https://www.inaturalist.org/pages/seek_app> app, so I’m now an enthusiastic CS observation reporter.

Cheers,

David G

> On 21 Jun 2022, at 12:46 am, Alan Stenhouse <alanstenhouse at hotmail.com> wrote:
> 
> Hi David
> 
> In a couple of my publications, I described developing apps with Livecode and referred to www.livecode.org and www.livecode.com, but didn't include anything in the references as there was nothing (AFAICS at that time) that would satisfy scientific publication standards.
> 
> See: https://www.sciencedirect.com/science/article/pii/S2351989420309173
> and
> https://www.sciencedirect.com/science/article/pii/S2351989421001761
> 
> HTH
> 
> cheers
> 
> Alan
> 
> 
>> On 18 Jun 2022, at 1:30 am, David V Glasgow wrote:
>> 
>>> On 16 Jun 2022, at 9:08 pm, J. Landman Gay via use-livecode <use-livecode at lists.runrev.com> wrote:
>>> 
>>> Is there a reason not to use the LC site URL, either alone or in addition to the Wikipedia one?
>> 
>> The https://livecode.com landing page is rather sparse, and focussed on drawing customers in rather than conveying anything about text processing, or obvious links to information on text processing.  No criticism of that at all.  It?s a commercial site.  
>> 
>> Wiki page has the disadvantage of a banner warning about link rot, but the advantage of lots of information presented in a more academic and neutral style.
>> 
>> 
>>> 
>>> Re: the errors, they look like examples of functions that would return "false" but I haven't seen them in context.
>>> --
>> 
>> They do, don?t they.  From memory, that wasn?t the context though.  
>> 
>> Cheers
>> 
>> David G
> 



More information about the use-livecode mailing list