Re: Writing Extensions

2017-05-17 Thread Mark Waddingham via use-livecode
On 2017-05-17 18:05, Mark Wieder via use-livecode wrote: Ha! Yes, It sounds like that should take care of that issue. I kept thinking the pointer was showing me where the error occurred (the line number was correct), but I kept changing the parameter it was pointing to and still got the same

Re: Writing Extensions

2017-05-17 Thread Mark Wieder via use-livecode
On 05/17/2017 12:19 AM, Mark Waddingham via use-livecode wrote: Yes - LCB errors now emit with a marker and code line as to where the error is... However, this requires a monospaced font to look right (it works really well from the terminal, for example) - so just making the log in field in the

Re: Writing Extensions

2017-05-17 Thread Richmond Mathewson via use-livecode
Why do I feel that the reason for all this "wierdness" is because LCB has been written from C++ programmers from the ground up, while LiveCode still (well, just about) hangs onto to its HyperCard heritage. LiveCode, at its best, preserves the clarity that was the best thing about HyperCard

Re: Writing Extensions

2017-05-17 Thread Mark Waddingham via use-livecode
On 2017-05-17 21:34, Richmond Mathewson via use-livecode wrote: Why do I feel that the reason for all this "wierdness" is because LCB has been written from C++ programmers from the ground up, while LiveCode still (well, just about) hangs onto to its HyperCard heritage. LiveCode, at its best,

Re: Writing Extensions

2017-05-17 Thread Mark Wieder via use-livecode
On 05/17/2017 12:09 AM, Ali Lloyd via use-livecode wrote: Mark, it would be lovely if you could be more specific. What parts of the docs in particular could be improved and how? What specific sticking points did you have? Oh, where to start? Here are some thoughts off the top of my head:

Re: Writing Extensions

2017-05-17 Thread Ali Lloyd via use-livecode
LCB as a language is marginally (if at all) more complex than LiveCode. In fact many lines of code are indistinguishable between the two. The difficulty Mark was having is more related to the fact that LCB is not 'live' like LiveCode Script, and that we certainly haven't quite cracked the

Android policy update

2017-05-17 Thread J. Landman Gay via use-livecode
I just got a developer email about a revision to Google's policies for apps on Google Play. Google will not allow apps that download executable code, similar to Apple's policy. It sounds like that includes stack content downloaded via a "launcher" app.

Re: English Like?

2017-05-17 Thread Marc Siskin via use-livecode
Bill, The solution to your issue is to use the short name version of name. Marc On May 17, 2017, at 1:41 PM, William Prothero via use-livecode > wrote: Folks: It can be difficult for long term users of an application to

Re: Writing Extensions

2017-05-17 Thread Mark Wieder via use-livecode
On 05/17/2017 01:10 PM, Ali Lloyd via use-livecode wrote: LCB as a language is marginally (if at all) more complex than LiveCode. In fact many lines of code are indistinguishable between the two. Yes. In fact it's the areas where they differ that make for a difficult learning curve. There are

Re: English Like?

2017-05-17 Thread Richard Gaskin via use-livecode
William Prothero wrote: > When Director died, I looked around, held my nose, and jumped to > livecode, and now I’m glad I jumped that initial negative barrier. > But, I take exception to the many claims that livecode is > “english-like” (in spite of the many “english-like” commands), >

Re: Writing Extensions

2017-05-17 Thread Mark Wieder via use-livecode
On 05/17/2017 02:30 PM, JB via use-livecode wrote: It looks to me like a the easier stepping stone to fill the gap is just write the code in C/C++, compile it and call it using a shell coimmand. Is that working for you in Android apps? -- Mark Wieder ahsoftw...@gmail.com

Re: Android policy update

2017-05-17 Thread Richard Gaskin via use-livecode
J. Landman Gay wrote: I just got a developer email about a revision to Google's policies for apps on Google Play. Google will not allow apps that download executable code, similar to Apple's policy. It sounds like that includes stack content downloaded via a "launcher" app.

English Like?

2017-05-17 Thread William Prothero via use-livecode
Folks: It can be difficult for long term users of an application to appreciate the “exceptions” to the philosophy of a dev app. I think the livecode community is affected by “familiarity” over clarity sometimes. For years (when Director was a viable dev platform), I had a negative feeling about

Re: Writing Extensions

2017-05-17 Thread JB via use-livecode
It looks to me like a the easier stepping stone to fill the gap is just write the code in C/C++, compile it and call it using a shell coimmand. I have been doing it in C and it works really good. I am amazed at how easy it is. If you can get the C code I posted to print out the argument you

Re: Writing Extensions

2017-05-17 Thread JB via use-livecode
This may sound crazy but I do not have any mobile phones. I have a really old iPad that won’t run the newer os. I think androids are written in Java and I have used Java. I have read C can be ported to Java but that is all I know. JB > On May 17, 2017, at 2:49 PM, Mark Wieder via

Re: Writing Extensions

2017-05-17 Thread Ali Lloyd via use-livecode
Mark, it would be lovely if you could be more specific. What parts of the docs in particular could be improved and how? What specific sticking points did you have? Could you file a bug report about the extension builder? It may be that something about error reporting has changed that hasn't been

Re: Writing Extensions

2017-05-17 Thread Mark Waddingham via use-livecode
On 2017-05-17 09:09, Ali Lloyd via use-livecode wrote: Mark, it would be lovely if you could be more specific. What parts of the docs in particular could be improved and how? What specific sticking points did you have? Could you file a bug report about the extension builder? It may be that