Re: Android: Myapp stopped
What minimum Android version is set in Standalone Settings? Does it include Android 6? On 10/12/23 8:35 AM, Klaus major-k via use-livecode wrote: Hi friends, I am trying to install my app on the tablets of my bandmembers and succeeded on all but one!? Info: Samsung Galaxy Tab S Android 6.0.1, API 23 After installation from LC (Test) I tap on the icon and get the alert: -> Leadsheeter stopped (angehalten) immediately, no more info. I already emptied cache and data and whatnot and even restarted the device a couple of times, no dice!? The only info I could get after starting Android Studio was in the "Device File Explorer" panel for the device which reads: data -> app -> com.major-k.de.leadsheeter-1 run-as: Could not set capabilities: Operation not permitted API too old? Anything else I can check in Android Studio? Any hints very welcome! Thanks a lot in advance. Best Klaus -- Klaus Major https://www.major-k.de https://www.major-k.de/bass kl...@major-k.de -- 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: Questions on Wasm export, licenses and file siz
Hi Richard specifically I need to know if I create an web page with multiple HTML5 export embeds whether the Livecode wasm approach forces the engine to be exported multiple times. On Thu, 12 Oct 2023 at 17:09, ambassador--- via use-livecode < use-livecode@lists.runrev.com> wrote: > David Bovill wrote: > > With the old JavaScript export you had a separation between the engine > > and stacks such that you could cache the engine part in the browser to > > speed up the loading of the much smaller stacks. Is that the case (or > > it is intended to be the case in the future) with the wasm export? > > A couple years ago Andre outlined the differences between JS and WASM, > worth reviewing: > https://www.mail-archive.com/use-livecode%40lists.runrev.com/msg08.html > > With your background you're probably well aware of the differences, but > since we see so many conceptualizing WASM as "compiled JavaScript" it's > worth taking a moment to review their respective boundaries. > > Given that WASM has no direct access to the DOM, and therefore no direct > manipulation of controls or events, it is not a drop-in replacement for JS. > > In LC terms, it may be best to think about WASM's relationship to the > browser as similar to what externals are to LC. > > Of course externals are very powerful; most of the v8 bullet points were > new externals. But they still need LC Script to interface with our apps. > > The degree to which LC Ltd will be able to compile the whole engine into > WASM is a good question, but it seems clear it will be limited in some > ways, and it's unlikely we'll see compilation of LC Script to WASM for the > foreseeable future. > > The good news is that the LC Community has a growing body of knowledge > around JavaScript: some of the cooler widgets are just wrappers around a > browser instance running JS/HTML/CSS. And given the vast amounts of > web-native (JS/HTML/CSS) code out in the world, folks are continually > finding new ways to integrate the native web stack with LC stack objects > nicely. > > If web deployment is the goal, I see no downside and much to be gained > from spending more time practicing JavaScript. While different from xTalk, > it's a good language, and arguably closer to what xTalk might have looked > like if HyperCard premiered 10 years later than it did. > > Being comfortable with JS means being able to fill in gaps between your LC > work and LC's web export more easily, and even within LC today it's the > gateway to vast components via the browser widget. > > JS is the only interactive language included in browsers. The best time > to learn it was yesterday. The second best time is today. > > Like AppleScript, PowerShell, bash, and others, learning other languages > opens new doors for integrating LC across a wide variety of systems. > > Bonus: the more you learn JS, the less you need to wait for with the > feature completion in LC's web export. > > As for your question about deployment size, we can expect a WASMified > engine to be smaller than its JS version, but there are so many factors > that go into that it may just be too early to tell. > > If you do a web search for "WASM replace JavaScript" you'll not only get > deeper discussions than what I've offered here, but also some confounding > benchmarks where it's possible to have compiled WASM larger than the source > code, and sometimes only slightly small, and then some amazingly smaller. > So much will depend on so many implementation details... > > -- > Richard Gaskin > Fourth World Systems > > ___ > 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: All Versions of LC crashing in Sonoma
Heather, Do you think Apple will address this issue in an update to Sonoma? Rebuilding all my applications will be difficult. Thank you, Bill Vlahos > On Oct 3, 2023, at 6:56 AM, Heather Laine via use-livecode > wrote: > > Hi Matthias, > > I think ANY menu will cause a crash. |f your app has no menus it will not be > affected by the issue. Otherwise, it will crash, as does LiveCode itself > prior to the fix. > > Best Regards, > > Heather > > Heather Laine > Customer Services Manager > LiveCode Ltd > www.livecode.com > > > >> On 3 Oct 2023, at 11:53, matthias rebbe via use-livecode >> wrote: >> >> Hi Heather, >> >> thanks for clarifying the reason for the crashes. >> >> At least this grants that standalones created with older LC versions will >> run as long as they do not contain a customized menu, right? >> >> Regards, >> Matthias >> >> >>> Am 03.10.2023 um 12:24 schrieb Heather Laine via use-livecode >>> : >>> >>> Hi Rolf, >>> >>> No, the problem is not related to signing. The problem centers on how >>> Sonoma handles menus, and any app that contains a menu will crash on Sonoma >>> unless built with LiveCode 9.6.10 or 10 dp-6. >>> >>> Best Regards, >>> >>> Heather >>> >>> Heather Laine >>> Customer Services Manager >>> LiveCode Ltd >>> www.livecode.com >>> >>> >>> On 3 Oct 2023, at 09:53, Rolf Kocherhans via use-livecode wrote: @Matthias and the Mothership, My Apple Developer account expired several years ago, and I'm facing a critical issue with one of my LiveCode Apps, Clarify, developed by Trevor DeVore. This app is extremely important to me. Unfortunately, Clarify is no longer actively developed and has started crashing with Sonoma. I am wondering if there's a possibility to resolve this issue by signing the bundles. I am more than willing to invest in a new subscription with Apple if that's what it takes – I can't imagine my work without Clarify. Could someone please test if signing the bundles might make an app functional again? Your assistance in this matter would mean the world to me. Cheers, Rolf Am 30.09.2023 um 18:00 schrieb use-livecode-requ...@lists.runrev.com: Maybe my observation is not the reason for the crash. Would really not make sense, when an unsigned app would crash instead of reporting an alert. But code signing the complete Livecode app bundle would proof it. Did someone btw had a look at the system log file after the crash? ___ 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 > > > ___ > 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: Windows Standalone strands windows tasks
Thanks I'll give that a try. I think I am already quitting the splash stack, because my MacOS works properly, but the second part I never knew about. Unfortunately my Apple laptop is in the shop so I won't be able to test until Monday. Bob S -Original Message- From: use-livecode On Behalf Of Klaus major-k via use-livecode Sent: Thursday, October 12, 2023 9:20 AM To: How to use LiveCode Cc: Klaus major-k Subject: Re: Windows Standalone strands windows tasks Hi Bob, > Am 12.10.2023 um 17:36 schrieb Bob Sneidar via use-livecode > : > > Hi all. > > I have a standalone that uses a splash stack, which upon launch displays a > startup graphic, then hides itself and opens the mainstack of my project. On > MacOS when I "quit" the entire application quits. On Windows however the > splash stack (which is the stack the standalone is built from) keeps running, > and if I re-launch the standalone it creates a second instance of the app in > memory. > > How do I get the standalone to quit when I close the mainstack in Windows? add this to the script your mainstack: - on closestack close stack "your splash stack here" ## do more closestack stuff end closestack - That should do the trick. Hint: To avoid this "Windows feature: >> if I re-launch the standalone it creates a second instance of the app in >> memory. add a dummy handler to your standalone/splash stack script: - on relaunch ## NADA! end relaunch - > Bob S Best Klaus -- Klaus Major https://www.major-k.de https://www.major-k.de/bass kl...@major-k.de ___ 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: Questions on Wasm export, licenses and file siz
ambassa...@fourthworld.com wrote: "JS is the only interactive language included in browsers. The best time to learn it was yesterday. The second best time is today." +1 My today was about 5 years ago. JS has been an asset to my workflow ever since. Being able get JS callbacks and invoke JS from LC has opened many new doors. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net ___ 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: Windows Standalone strands windows tasks
Hi Bob, > Am 12.10.2023 um 17:36 schrieb Bob Sneidar via use-livecode > : > > Hi all. > > I have a standalone that uses a splash stack, which upon launch displays a > startup graphic, then hides itself and opens the mainstack of my project. On > MacOS when I "quit" the entire application quits. On Windows however the > splash stack (which is the stack the standalone is built from) keeps running, > and if I re-launch the standalone it creates a second instance of the app in > memory. > > How do I get the standalone to quit when I close the mainstack in Windows? add this to the script your mainstack: - on closestack close stack "your splash stack here" ## do more closestack stuff end closestack - That should do the trick. Hint: To avoid this "Windows feature: >> if I re-launch the standalone it creates a second instance of the app in >> memory. add a dummy handler to your standalone/splash stack script: - on relaunch ## NADA! end relaunch - > Bob S Best Klaus -- Klaus Major https://www.major-k.de https://www.major-k.de/bass kl...@major-k.de ___ 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: Questions on Wasm export, licenses and file siz
David Bovill wrote: > With the old JavaScript export you had a separation between the engine > and stacks such that you could cache the engine part in the browser to > speed up the loading of the much smaller stacks. Is that the case (or > it is intended to be the case in the future) with the wasm export? A couple years ago Andre outlined the differences between JS and WASM, worth reviewing: https://www.mail-archive.com/use-livecode%40lists.runrev.com/msg08.html With your background you're probably well aware of the differences, but since we see so many conceptualizing WASM as "compiled JavaScript" it's worth taking a moment to review their respective boundaries. Given that WASM has no direct access to the DOM, and therefore no direct manipulation of controls or events, it is not a drop-in replacement for JS. In LC terms, it may be best to think about WASM's relationship to the browser as similar to what externals are to LC. Of course externals are very powerful; most of the v8 bullet points were new externals. But they still need LC Script to interface with our apps. The degree to which LC Ltd will be able to compile the whole engine into WASM is a good question, but it seems clear it will be limited in some ways, and it's unlikely we'll see compilation of LC Script to WASM for the foreseeable future. The good news is that the LC Community has a growing body of knowledge around JavaScript: some of the cooler widgets are just wrappers around a browser instance running JS/HTML/CSS. And given the vast amounts of web-native (JS/HTML/CSS) code out in the world, folks are continually finding new ways to integrate the native web stack with LC stack objects nicely. If web deployment is the goal, I see no downside and much to be gained from spending more time practicing JavaScript. While different from xTalk, it's a good language, and arguably closer to what xTalk might have looked like if HyperCard premiered 10 years later than it did. Being comfortable with JS means being able to fill in gaps between your LC work and LC's web export more easily, and even within LC today it's the gateway to vast components via the browser widget. JS is the only interactive language included in browsers. The best time to learn it was yesterday. The second best time is today. Like AppleScript, PowerShell, bash, and others, learning other languages opens new doors for integrating LC across a wide variety of systems. Bonus: the more you learn JS, the less you need to wait for with the feature completion in LC's web export. As for your question about deployment size, we can expect a WASMified engine to be smaller than its JS version, but there are so many factors that go into that it may just be too early to tell. If you do a web search for "WASM replace JavaScript" you'll not only get deeper discussions than what I've offered here, but also some confounding benchmarks where it's possible to have compiled WASM larger than the source code, and sometimes only slightly small, and then some amazingly smaller. So much will depend on so many implementation details... -- Richard Gaskin Fourth World Systems ___ 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
Windows Standalone strands windows tasks
Hi all. I have a standalone that uses a splash stack, which upon launch displays a startup graphic, then hides itself and opens the mainstack of my project. On MacOS when I "quit" the entire application quits. On Windows however the splash stack (which is the stack the standalone is built from) keeps running, and if I re-launch the standalone it creates a second instance of the app in memory. How do I get the standalone to quit when I close the mainstack in Windows? Bob S ___ 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: Android: Myapp stopped
> Am 12.10.2023 um 15:43 schrieb matthias rebbe via use-livecode > : > > Hm, > just a shot in the dark, did you enable the Development mode on the tablets? sure! A propos dark: At midnight on a graveyard I tapped SEVEN times on the buildnumber, that should have done the trick, right! :-D >> Am 12.10.2023 um 15:35 schrieb Klaus major-k via use-livecode >> : >> >> Hi friends, >> >> I am trying to install my app on the tablets of my bandmembers >> and succeeded on all but one!? >> >> Info: >> Samsung Galaxy Tab S >> Android 6.0.1, API 23 >> >> After installation from LC (Test) I tap on the icon and get the alert: >> -> Leadsheeter stopped (angehalten) >> immediately, no more info. >> >> I already emptied cache and data and whatnot and even restarted >> the device a couple of times, no dice!? >> >> The only info I could get after starting Android Studio was in the >> "Device File Explorer" panel for the device which reads: >> >> data -> app -> com.major-k.de.leadsheeter-1 >> run-as: Could not set capabilities: Operation not permitted >> >> API too old? Anything else I can check in Android Studio? >> >> Any hints very welcome! Best Klaus -- Klaus Major https://www.major-k.de https://www.major-k.de/bass kl...@major-k.de ___ 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: Android: Myapp stopped
Hm, just a shot in the dark, did you enable the Development mode on the tablets? > Am 12.10.2023 um 15:35 schrieb Klaus major-k via use-livecode > : > > Hi friends, > > I am trying to install my app on the tablets of my bandmembers > and succeeded on all but one!? > > Info: > Samsung Galaxy Tab S > Android 6.0.1, API 23 > > After installation from LC (Test) I tap on the icon and get the alert: > -> Leadsheeter stopped (angehalten) > immediately, no more info. > > I already emptied cache and data and whatnot and even restarted > the device a couple of times, no dice!? > > The only info I could get after starting Android Studio was in the > "Device File Explorer" panel for the device which reads: > > data -> app -> com.major-k.de.leadsheeter-1 > run-as: Could not set capabilities: Operation not permitted > > API too old? Anything else I can check in Android Studio? > > Any hints very welcome! > > Thanks a lot in advance. > > > Best > > Klaus > -- > Klaus Major > https://www.major-k.de > https://www.major-k.de/bass > kl...@major-k.de > > > ___ > 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
Android: Myapp stopped
Hi friends, I am trying to install my app on the tablets of my bandmembers and succeeded on all but one!? Info: Samsung Galaxy Tab S Android 6.0.1, API 23 After installation from LC (Test) I tap on the icon and get the alert: -> Leadsheeter stopped (angehalten) immediately, no more info. I already emptied cache and data and whatnot and even restarted the device a couple of times, no dice!? The only info I could get after starting Android Studio was in the "Device File Explorer" panel for the device which reads: data -> app -> com.major-k.de.leadsheeter-1 run-as: Could not set capabilities: Operation not permitted API too old? Anything else I can check in Android Studio? Any hints very welcome! Thanks a lot in advance. Best Klaus -- Klaus Major https://www.major-k.de https://www.major-k.de/bass kl...@major-k.de ___ 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
Questions on Wasm export, licenses and file size
I know that HTML5 export is not quite ready yet - but I’m a patient man :) I would like to know how it works / will work - particularly with regard to the size of the exports. With the old JavaScript export you had a separation between the engine and stacks such that you could cache the engine part in the browser to speed up the loading of the much smaller stacks. Is that the case (or it is intended to be the case in the future) with the wasm export? I’m looking towards a world in which multiple wasm components written in various languages sit on a web page talking to each other. ___ 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
