Re: OT Re: Referencing Livecode

Hi. These are great examples of use cases for LiveCode and it is great how you explain the app design. It especially cool that the apps are used for citizen science. It complements LiveCode's “anyone can code” tag line with the “any one can do science" ethic of citizen science. Thanks Alan.

OT Re: Referencing Livecode

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 app, so I’m now an enthusiastic CS observation reporter. Cheers, David G > On 21 Jun 2022, at 12:46 am

Re: Referencing Livecode

Alan Stenhouse via use-livecode wrote > 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 > scient

Re: Referencing Livecode

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://w

Re: Referencing Livecode

> On 17 Jun 2022, at 6:55 pm, Martin Koob via use-livecode > wrote: > > > Here is a link to that conference paper where you can download it. > https://www.researchgate.net/publication/269337987_Using_Cognitive_Load_Theory_to_select_an_Environment_for_Teaching_Mobile_Apps_Development > >

Re: Referencing Livecode

What about this link from the LiveCode.com site? https://livecode.com/core-benefits-of-livecode/ It summarizes what LiveCode is and gives a comparison of LiveCode script to code in JavaScript, PHP and Java. It even mentions an academic article: "A 2016 peer reviewed study conducted at Southe

Re: Referencing Livecode

That’s absurd. Everyone knows it was a Sherland pony. Sent from my iPhone > On Jun 17, 2022, at 10:28, Richmond Mathewson via use-livecode > wrote: > > As I, or anyone else could write on Wikipedia about Hamlet being > Shakespeare's coded love notes to a camel he met in Oxford, I really wonde

Re: Referencing Livecode

I think no matter what you go to, inevitably you are looking for what other people have said in critiquing hamlet or anything else. We call some people experts because other people called experts certified them as such. It can’t be any other way. But I often wonder who the first expert in any fi

Re: Referencing Livecode

As I, or anyone else could write on Wikipedia about Hamlet being Shakespeare's coded love notes to a camel he met in Oxford, I really wonder why anyone, 'academic' or not, would stick their neck under that guillotine's fairly jittery blade escapes me completely. I often look up things on Wikipedia

Re: Referencing Livecode

The same rules apply to US schools. It may be similar to doing a critique of Hamlet after reading only the Cliff Notes summary. No actual research or thought required. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On June 17, 2022 11:11

Re: Referencing Livecode

I wonder why that is? While you may find inaccurate information on Wikipedia, the vastly overwhelming information there is absolutely accurate. But isn't that true of EVERY source? In my life experience I have found that settled science is very unsettled indeed. Salt causes high blood pressure.

Re: Referencing Livecode

Maybe a direct link here would be better: https://livecode.com/resources/ Sent from my iPhone > On Jun 17, 2022, at 6:39 AM, Mark Smith via use-livecode > wrote: > > I think in this instance, probably asking support would be the best bet. > >> On 16 Jun 2022, at 2:31 pm, David V Glasgow

Re: Referencing Livecode

I think in this instance, probably asking support would be the best bet. > On 16 Jun 2022, at 2:31 pm, David V Glasgow via use-livecode > wrote: > > Hi Folks, > > I am writing a paper for publication (I hope) describing analysis of internet > predator messages achieved using Livecode. > > I

Re: Referencing Livecode

Of course that is completely true for academic content! This ain’t that. In the paper I simply state that all text searching, manipulation and aggregation was achieved using Livecode scripts, with a footnote to a brief description and link to … Go on. Ask your wife. That is how it’s done. (

Re: Referencing Livecode

From what I know (my wife is a senior academic at a university) references to Wikipedia pages are academic suicide, fail, go straight to jail, do not pass GO, do not collect 200 smackers, and you get the picture. On Fri, 17 Jun 2022, 11:47 David V Glasgow via use-livecode, < use-livecode@lists.run

Re: Referencing Livecode

> On 16 Jun 2022, at 9:08 pm, J. Landman Gay via use-livecode > 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 anyt

Re: Referencing Livecode

Is there a reason not to use the LC site URL, either alone or in addition to the Wikipedia one? Re: the errors, they look like examples of functions that would return "false" but I haven't seen them in context. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://