Re: New(?) Idea for Standalones
Thanks for clarifying that for me! As far as the license stuff goes on the community version I personally think the community is allowed to supersede LiveCode if they feel like investing the time. It should not be able to be held back just to make sure all of the new features are done by the LiveCode Team. As long as it is kept public like the community version was designed to do. JB > On Mar 28, 2021, at 10:04 PM, Roger Guay via use-livecode > wrote: > > John et al, > > To recap: > > My ultimate goal is to get support for RunRev to provide a LiveCodeLight > download that opens stacks but hides or strips the IDE. I can’t believe this > would be difficult in any way. > > In the meantime, I am trying to recreate the old Standalone app method (See > Jacquelines’ post in this thread) that opens stacks. 2 or more OSs ago this > was extremely easy to do, but because of the increasing complexity of Apple > requirements (and Windows?) it is now quite difficult and I have yet to > succeed at it. Even if it is still possible, I shudder to think what they > will do next to further complicate our efforts to simple collaborate and > share with family and friends. > > Thanks to all who are taking an interest. > > Roger > > > >> On Mar 28, 2021, at 9:14 PM, John Balgenorth via use-livecode >> wrote: >> >> I was thinking one of the reasons people were saying not to provide a >> scaled down version of the development system to do it was because >> they were afraid it would interfere with the license. But since you can >> do it according to some of you is proof you are allowed to automate >> the process and that should not interfere with the user license. >> >> JB >> On Mar 28, 2021, at 9:04 PM, Dev via use-livecode wrote: >>> >>> If it works, the upside is that anyone can do it themselves and coach >>> their family into doing the two step process once on the first time install. >>> >>> If it doesn’t work, we need to get a real developer to make a real app that >>> jumps through Apple’s hoops. And then the developer has to keep it updated >>> every time Apple makes a change. >>> >>> I agree this whole thing is a bother, but as other posts have pointed out, >>> “This is not the good old days and security is not going away” so this >>> whole discussion is trying to find the narrowest point to cross. If the >>> amateurs can do it themselves with a two step magic incantation, then this >>> puts the ball back in their court and allows them into the game with out >>> going through the Apple doorway. >>> >>> Kelly >>> On 28 Mar, 2021, at 9:54 PM, John Balgenorth via use-livecode wrote: I may have got lost on this subject but if his goal was to make it easy for people to open his app by doing something like using a scaled down version of the development system then this one step of doing it twice is a valid reason for using what he wanted because people do not want to be bothered with things like that. JB >> On Mar 28, 2021, at 8:41 PM, scott--- via use-livecode >> wrote: > > > I may have described it incorrectly. After re-testing here on OS 11.2.3 > I found that it required two tries. Trying to open it the first time > meets with failure. But Right clicking and choosing “Open” the second > time gives a second dialog that will allow it to open. > > — > Scott > >> On Mar 28, 2021, at 2:58 PM, Roger Guay via use-livecode >> wrote: >> >> Nope! Right clicking on a standalone I’m trying to share with my wife on >> her iMac w OS 11.2 results in this menu: Open Attachment - Quick Look >> Attachment - Save Attachment…. - Save to Downloads Folder - Share - Copy >> - Speech >> >> Then, clicking on the “Open Attachment” menu item results in the same >> response I reported earlier: a simple screen with this message: You do >> not have permission to open the application “StackOmatic”. “Contact your >> computer or network administrator for assistance” with a simple “OK” >> button. Dead end as before! >> >> Further, at Kelly's suggestion to try and adjust settings in the >> Security and Privacy System Preferences to downgrade standards to allow >> a one time opening, I found nothing of the sort. >> >> So at this point, I think Kelly’s idea of someone with Apple credentials >> building a certified standalone that runs stacks is the only short term >> solution. If it helps, I and probably others, would be willing to pay a >> reasonable fee for such gem. Otherwise, I and anyone else wanting to >> share stacks, will have to jump through the increasingly ridiculous >> hoops that Apple (and Windows?) place before us. OTH…. >> >> Ultimately, I really think that a LiveCodeLight app that runs stacks >> without the IDE would be the best way to go to
Re: New(?) Idea for Standalones
John et al, To recap: My ultimate goal is to get support for RunRev to provide a LiveCodeLight download that opens stacks but hides or strips the IDE. I can’t believe this would be difficult in any way. In the meantime, I am trying to recreate the old Standalone app method (See Jacquelines’ post in this thread) that opens stacks. 2 or more OSs ago this was extremely easy to do, but because of the increasing complexity of Apple requirements (and Windows?) it is now quite difficult and I have yet to succeed at it. Even if it is still possible, I shudder to think what they will do next to further complicate our efforts to simple collaborate and share with family and friends. Thanks to all who are taking an interest. Roger > On Mar 28, 2021, at 9:14 PM, John Balgenorth via use-livecode > wrote: > > I was thinking one of the reasons people were saying not to provide a > scaled down version of the development system to do it was because > they were afraid it would interfere with the license. But since you can > do it according to some of you is proof you are allowed to automate > the process and that should not interfere with the user license. > > JB > >> On Mar 28, 2021, at 9:04 PM, Dev via use-livecode >> wrote: >> >> If it works, the upside is that anyone can do it themselves and coach their >> family into doing the two step process once on the first time install. >> >> If it doesn’t work, we need to get a real developer to make a real app that >> jumps through Apple’s hoops. And then the developer has to keep it updated >> every time Apple makes a change. >> >> I agree this whole thing is a bother, but as other posts have pointed out, >> “This is not the good old days and security is not going away” so this whole >> discussion is trying to find the narrowest point to cross. If the amateurs >> can do it themselves with a two step magic incantation, then this puts the >> ball back in their court and allows them into the game with out going >> through the Apple doorway. >> >> Kelly >> >>> On 28 Mar, 2021, at 9:54 PM, John Balgenorth via use-livecode >>> wrote: >>> >>> I may have got lost on this subject but if his goal was to make it >>> easy for people to open his app by doing something like using a >>> scaled down version of the development system then this one >>> step of doing it twice is a valid reason for using what he wanted >>> because people do not want to be bothered with things like that. >>> >>> JB >>> > On Mar 28, 2021, at 8:41 PM, scott--- via use-livecode > wrote: I may have described it incorrectly. After re-testing here on OS 11.2.3 I found that it required two tries. Trying to open it the first time meets with failure. But Right clicking and choosing “Open” the second time gives a second dialog that will allow it to open. — Scott > On Mar 28, 2021, at 2:58 PM, Roger Guay via use-livecode > wrote: > > Nope! Right clicking on a standalone I’m trying to share with my wife on > her iMac w OS 11.2 results in this menu: Open Attachment - Quick Look > Attachment - Save Attachment…. - Save to Downloads Folder - Share - Copy > - Speech > > Then, clicking on the “Open Attachment” menu item results in the same > response I reported earlier: a simple screen with this message: You do > not have permission to open the application “StackOmatic”. “Contact your > computer or network administrator for assistance” with a simple “OK” > button. Dead end as before! > > Further, at Kelly's suggestion to try and adjust settings in the Security > and Privacy System Preferences to downgrade standards to allow a one time > opening, I found nothing of the sort. > > So at this point, I think Kelly’s idea of someone with Apple credentials > building a certified standalone that runs stacks is the only short term > solution. If it helps, I and probably others, would be willing to pay a > reasonable fee for such gem. Otherwise, I and anyone else wanting to > share stacks, will have to jump through the increasingly ridiculous hoops > that Apple (and Windows?) place before us. OTH…. > > Ultimately, I really think that a LiveCodeLight app that runs stacks > without the IDE would be the best way to go to share stacks with friends, > family and colleagues. > > Roger > > > >>> On Mar 28, 2021, at 12:24 AM, scott--- via use-livecode >>> wrote: >> >> Kelly is correct. While holding down the control key, click and hold (or >> right click) to get an additional menu allowing you to choose to open >> the app. >> — >> Scott > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your >
Re: New(?) Idea for Standalones
I was thinking one of the reasons people were saying not to provide a scaled down version of the development system to do it was because they were afraid it would interfere with the license. But since you can do it according to some of you is proof you are allowed to automate the process and that should not interfere with the user license. JB > On Mar 28, 2021, at 9:04 PM, Dev via use-livecode > wrote: > > If it works, the upside is that anyone can do it themselves and coach their > family into doing the two step process once on the first time install. > > If it doesn’t work, we need to get a real developer to make a real app that > jumps through Apple’s hoops. And then the developer has to keep it updated > every time Apple makes a change. > > I agree this whole thing is a bother, but as other posts have pointed out, > “This is not the good old days and security is not going away” so this whole > discussion is trying to find the narrowest point to cross. If the amateurs > can do it themselves with a two step magic incantation, then this puts the > ball back in their court and allows them into the game with out going through > the Apple doorway. > > Kelly > >> On 28 Mar, 2021, at 9:54 PM, John Balgenorth via use-livecode >> wrote: >> >> I may have got lost on this subject but if his goal was to make it >> easy for people to open his app by doing something like using a >> scaled down version of the development system then this one >> step of doing it twice is a valid reason for using what he wanted >> because people do not want to be bothered with things like that. >> >> JB >> On Mar 28, 2021, at 8:41 PM, scott--- via use-livecode wrote: >>> >>> >>> I may have described it incorrectly. After re-testing here on OS 11.2.3 I >>> found that it required two tries. Trying to open it the first time meets >>> with failure. But Right clicking and choosing “Open” the second time gives >>> a second dialog that will allow it to open. >>> >>> — >>> Scott >>> On Mar 28, 2021, at 2:58 PM, Roger Guay via use-livecode wrote: Nope! Right clicking on a standalone I’m trying to share with my wife on her iMac w OS 11.2 results in this menu: Open Attachment - Quick Look Attachment - Save Attachment…. - Save to Downloads Folder - Share - Copy - Speech Then, clicking on the “Open Attachment” menu item results in the same response I reported earlier: a simple screen with this message: You do not have permission to open the application “StackOmatic”. “Contact your computer or network administrator for assistance” with a simple “OK” button. Dead end as before! Further, at Kelly's suggestion to try and adjust settings in the Security and Privacy System Preferences to downgrade standards to allow a one time opening, I found nothing of the sort. So at this point, I think Kelly’s idea of someone with Apple credentials building a certified standalone that runs stacks is the only short term solution. If it helps, I and probably others, would be willing to pay a reasonable fee for such gem. Otherwise, I and anyone else wanting to share stacks, will have to jump through the increasingly ridiculous hoops that Apple (and Windows?) place before us. OTH…. Ultimately, I really think that a LiveCodeLight app that runs stacks without the IDE would be the best way to go to share stacks with friends, family and colleagues. Roger >> On Mar 28, 2021, at 12:24 AM, scott--- via use-livecode >> wrote: > > Kelly is correct. While holding down the control key, click and hold (or > right click) to get an additional menu allowing you to choose to open the > app. > — > Scott ___ 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: New(?) Idea for Standalones
If it works, the upside is that anyone can do it themselves and coach their family into doing the two step process once on the first time install. If it doesn’t work, we need to get a real developer to make a real app that jumps through Apple’s hoops. And then the developer has to keep it updated every time Apple makes a change. I agree this whole thing is a bother, but as other posts have pointed out, “This is not the good old days and security is not going away” so this whole discussion is trying to find the narrowest point to cross. If the amateurs can do it themselves with a two step magic incantation, then this puts the ball back in their court and allows them into the game with out going through the Apple doorway. Kelly > On 28 Mar, 2021, at 9:54 PM, John Balgenorth via use-livecode > wrote: > > I may have got lost on this subject but if his goal was to make it > easy for people to open his app by doing something like using a > scaled down version of the development system then this one > step of doing it twice is a valid reason for using what he wanted > because people do not want to be bothered with things like that. > > JB > >> On Mar 28, 2021, at 8:41 PM, scott--- via use-livecode >> wrote: >> >> >> I may have described it incorrectly. After re-testing here on OS 11.2.3 I >> found that it required two tries. Trying to open it the first time meets >> with failure. But Right clicking and choosing “Open” the second time gives a >> second dialog that will allow it to open. >> >> — >> Scott >> >>> On Mar 28, 2021, at 2:58 PM, Roger Guay via use-livecode >>> wrote: >>> >>> Nope! Right clicking on a standalone I’m trying to share with my wife on >>> her iMac w OS 11.2 results in this menu: Open Attachment - Quick Look >>> Attachment - Save Attachment…. - Save to Downloads Folder - Share - Copy - >>> Speech >>> >>> Then, clicking on the “Open Attachment” menu item results in the same >>> response I reported earlier: a simple screen with this message: You do not >>> have permission to open the application “StackOmatic”. “Contact your >>> computer or network administrator for assistance” with a simple “OK” >>> button. Dead end as before! >>> >>> Further, at Kelly's suggestion to try and adjust settings in the Security >>> and Privacy System Preferences to downgrade standards to allow a one time >>> opening, I found nothing of the sort. >>> >>> So at this point, I think Kelly’s idea of someone with Apple credentials >>> building a certified standalone that runs stacks is the only short term >>> solution. If it helps, I and probably others, would be willing to pay a >>> reasonable fee for such gem. Otherwise, I and anyone else wanting to share >>> stacks, will have to jump through the increasingly ridiculous hoops that >>> Apple (and Windows?) place before us. OTH…. >>> >>> Ultimately, I really think that a LiveCodeLight app that runs stacks >>> without the IDE would be the best way to go to share stacks with friends, >>> family and colleagues. >>> >>> Roger >>> >>> >>> > On Mar 28, 2021, at 12:24 AM, scott--- via use-livecode > wrote: Kelly is correct. While holding down the control key, click and hold (or right click) to get an additional menu allowing you to choose to open the app. — Scott >>> >>> ___ >>> 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: New(?) Idea for Standalones
I may have got lost on this subject but if his goal was to make it easy for people to open his app by doing something like using a scaled down version of the development system then this one step of doing it twice is a valid reason for using what he wanted because people do not want to be bothered with things like that. JB > On Mar 28, 2021, at 8:41 PM, scott--- via use-livecode > wrote: > > > I may have described it incorrectly. After re-testing here on OS 11.2.3 I > found that it required two tries. Trying to open it the first time meets with > failure. But Right clicking and choosing “Open” the second time gives a > second dialog that will allow it to open. > > — > Scott > >> On Mar 28, 2021, at 2:58 PM, Roger Guay via use-livecode >> wrote: >> >> Nope! Right clicking on a standalone I’m trying to share with my wife on her >> iMac w OS 11.2 results in this menu: Open Attachment - Quick Look Attachment >> - Save Attachment…. - Save to Downloads Folder - Share - Copy - Speech >> >> Then, clicking on the “Open Attachment” menu item results in the same >> response I reported earlier: a simple screen with this message: You do not >> have permission to open the application “StackOmatic”. “Contact your >> computer or network administrator for assistance” with a simple “OK” button. >> Dead end as before! >> >> Further, at Kelly's suggestion to try and adjust settings in the Security >> and Privacy System Preferences to downgrade standards to allow a one time >> opening, I found nothing of the sort. >> >> So at this point, I think Kelly’s idea of someone with Apple credentials >> building a certified standalone that runs stacks is the only short term >> solution. If it helps, I and probably others, would be willing to pay a >> reasonable fee for such gem. Otherwise, I and anyone else wanting to share >> stacks, will have to jump through the increasingly ridiculous hoops that >> Apple (and Windows?) place before us. OTH…. >> >> Ultimately, I really think that a LiveCodeLight app that runs stacks without >> the IDE would be the best way to go to share stacks with friends, family and >> colleagues. >> >> Roger >> >> >> On Mar 28, 2021, at 12:24 AM, scott--- via use-livecode wrote: >>> >>> Kelly is correct. While holding down the control key, click and hold (or >>> right click) to get an additional menu allowing you to choose to open the >>> app. >>> — >>> Scott >> >> ___ >> 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: New(?) Idea for Standalones
I may have described it incorrectly. After re-testing here on OS 11.2.3 I found that it required two tries. Trying to open it the first time meets with failure. But Right clicking and choosing “Open” the second time gives a second dialog that will allow it to open. — Scott > On Mar 28, 2021, at 2:58 PM, Roger Guay via use-livecode > wrote: > > Nope! Right clicking on a standalone I’m trying to share with my wife on her > iMac w OS 11.2 results in this menu: Open Attachment - Quick Look Attachment > - Save Attachment…. - Save to Downloads Folder - Share - Copy - Speech > > Then, clicking on the “Open Attachment” menu item results in the same > response I reported earlier: a simple screen with this message: You do not > have permission to open the application “StackOmatic”. “Contact your computer > or network administrator for assistance” with a simple “OK” button. Dead end > as before! > > Further, at Kelly's suggestion to try and adjust settings in the Security and > Privacy System Preferences to downgrade standards to allow a one time > opening, I found nothing of the sort. > > So at this point, I think Kelly’s idea of someone with Apple credentials > building a certified standalone that runs stacks is the only short term > solution. If it helps, I and probably others, would be willing to pay a > reasonable fee for such gem. Otherwise, I and anyone else wanting to share > stacks, will have to jump through the increasingly ridiculous hoops that > Apple (and Windows?) place before us. OTH…. > > Ultimately, I really think that a LiveCodeLight app that runs stacks without > the IDE would be the best way to go to share stacks with friends, family and > colleagues. > > Roger > > > >> On Mar 28, 2021, at 12:24 AM, scott--- via use-livecode >> wrote: >> >> Kelly is correct. While holding down the control key, click and hold (or >> right click) to get an additional menu allowing you to choose to open the >> app. >> — >> Scott > > ___ > 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
Resources folder on mac, and the good old days
> you may already know this, but this will not work in a standalone!
> We will surely not have write permissions in that folder!
>
> As a workaround I would probably use -> specialfolderpath("temporary")
> Or even write the text to -> the tempname
>
I find this discussions strange - I had the impression most users here were Mac
developers and knew this stuff.
There is no problem writing to the resources folder. That’s the logical place
to put the user-changeable stack files for a standalone, making the auxiliary
files invisible to external fiddling by the user, which a Good Thing (although
that does make the app look different on Windows or Linux).
As for the Good Old Days of free distribution to other Mac (desktop) users,
they haven’t gone. Apple is making it harder for the uninitiated to find out
how to open “unsafe” files, but they don't keep it a secret. And while recent
rumours abound about unnotarized apps not working at all on some future MacOS,
it does seem unlikely that will actually happen, and if they do that’s time for
us all to reboot to Linux.
Neville
___
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: New(?) Idea for Standalones
James, Kelly and Brian, Thanks for sticking with me on this. Perhaps, to smooth out this process, I should look for an uncertified app to download to my own machine, instead of working off of her machine. Have you any suggestions for that? Answers to some of your question: I emailed a standalone app to my wife called StackOmatic that opens stacks (works on my machine) I tried double and right clicking from the email then... I saved it to her Desktop and also to her Downloads where I tired both double clicking and right clicking again In every case, I end up with the dreaded "You do not have permission to open the application “StackOmatic”. “Contact your computer or network administrator for assistance” with a simple “OK” button. HTH, Roger > On Mar 28, 2021, at 6:20 PM, james--- via use-livecode > wrote: > > Hi Roger, > > You wrote: > >> Nope! Right clicking on a standalone I?m trying to share with my wife on her >> iMac w OS 11.2 results in this menu: Open Attachment - Quick Look Attachment >> - Save Attachment?. - Save to Downloads Folder - Share - Copy - Speech > > This list of menu options looks like those that appear if you are > right-clicking on an attachment in Mail. > > The right-click menu being referred to here is only available when you are in > the Finder. > So the app you sent to your wife’s machine (apparently by Mail) needs to be > downloaded first. Then, in the Finder, locate the downloaded file and > right-click on it. > > The menu that appears will have as the first two options “Open” and “Show > Package Contents”. > If the second option offered is not “Show Package Options” but “Open With” > then you have not transferred an app but a document (perhaps the LC stack?) > > Try this with other apps and documents on your wife’s mac to confirm the two > types of option menus that come up. > > Choosing “Open” for an application Finder context menu will, for unnotorized > apps, will then bring up the dlog asking if you really do want to open this > app. This only needs to be done the first time the app is opened. > > 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 ___ 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: New(?) Idea for Standalones
Hi Roger, You wrote: > Nope! Right clicking on a standalone I?m trying to share with my wife on her > iMac w OS 11.2 results in this menu: Open Attachment - Quick Look Attachment > - Save Attachment?. - Save to Downloads Folder - Share - Copy - Speech This list of menu options looks like those that appear if you are right-clicking on an attachment in Mail. The right-click menu being referred to here is only available when you are in the Finder. So the app you sent to your wife’s machine (apparently by Mail) needs to be downloaded first. Then, in the Finder, locate the downloaded file and right-click on it. The menu that appears will have as the first two options “Open” and “Show Package Contents”. If the second option offered is not “Show Package Options” but “Open With” then you have not transferred an app but a document (perhaps the LC stack?) Try this with other apps and documents on your wife’s mac to confirm the two types of option menus that come up. Choosing “Open” for an application Finder context menu will, for unnotorized apps, will then bring up the dlog asking if you really do want to open this app. This only needs to be done the first time the app is opened. 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: New(?) Idea for Standalones
> Richard G. wrote: > > I raise my whiskey > to toast your whisky. Sláinte! 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: New(?) Idea for Standalones
So how are you getting it on to her machine? Drag and drop across the net in your house? Email? AirDrop? Lets start from the beginning and sort this out, because I think you ought to be able to do it. Kelly > On 28 Mar, 2021, at 5:46 PM, Roger Guay via use-livecode > wrote: > > I feel bad that you guys are sticking with me to no avail. Saving it first to > Downloads or Desktop does not work. > > Sorry to be such a bother, > > Roger > >> On Mar 28, 2021, at 4:26 PM, Dev via use-livecode >> wrote: >> >> Agreed. Save to the desktop and then try the right click Open command. >> >> Kelly >> >> Sent from my iPhone >> >>> On Mar 28, 2021, at 5:04 PM, Brian Milby via use-livecode >>> wrote: >>> >>> I think the “attachment” is part of the issue. Save to downloads first? >>> >>> Sent from my iPhone >>> On Mar 28, 2021, at 6:00 PM, Roger Guay via use-livecode wrote: Nope! Right clicking on a standalone I’m trying to share with my wife on her iMac w OS 11.2 results in this menu: Open Attachment - Quick Look Attachment - Save Attachment…. - Save to Downloads Folder - Share - Copy - Speech Then, clicking on the “Open Attachment” menu item results in the same response I reported earlier: a simple screen with this message: You do not have permission to open the application “StackOmatic”. “Contact your computer or network administrator for assistance” with a simple “OK” button. Dead end as before! Further, at Kelly's suggestion to try and adjust settings in the Security and Privacy System Preferences to downgrade standards to allow a one time opening, I found nothing of the sort. So at this point, I think Kelly’s idea of someone with Apple credentials building a certified standalone that runs stacks is the only short term solution. If it helps, I and probably others, would be willing to pay a reasonable fee for such gem. Otherwise, I and anyone else wanting to share stacks, will have to jump through the increasingly ridiculous hoops that Apple (and Windows?) place before us. OTH…. Ultimately, I really think that a LiveCodeLight app that runs stacks without the IDE would be the best way to go to share stacks with friends, family and colleagues. Roger >> On Mar 28, 2021, at 12:24 AM, scott--- via use-livecode >> wrote: > > Kelly is correct. While holding down the control key, click and hold (or > right click) to get an additional menu allowing you to choose to open the > app. > — > Scott ___ 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: New(?) Idea for Standalones
Alex Tweedly wrote: > On 27/03/2021 02:43, Richard Gaskin via use-livecode wrote: >> This makes the Community Edition a natural fit for a generic player, >> since the proliferation the license explicitly encourages would be >> very much with the grain of its goals. >> >> But then we have to ask: how many of those who might enjoy a generic >> player embrace the GPL with the stacks they'd like to distribute it >> with? > > hmmm - I don't get that bit. > > The generic player would be built with Community Edition - and hence > must be GPL-compliant. > > However, the stacks it "plays" are merely documents. GPL is (afaiu) > clear that documents viewed (or indeed created) by GPL apps are not > covered by the GPL - i.e. it does not proliferate into the stacks. > The stacks are not in any way derivative of the player. > > So I could build a stack with my Indy license, and distribute that > under any restrictive licensing terms I choose, but use the CE/GPL > compliant player app to run them. > > Of course, the source of the stacks would be visible, but there > wouldn't seem to be any requirement on which licensing terms I apply > to that stack. > > Or, I may be misunderstanding GPL again - I have done on many > occasions since I first hired a developer to work on gcc back in the > mid-80s :-) The GPL is intentionally vague on what constitutes "derivative work" with regard to license inheritance, acknowledging the vast and ever-growing number of ways code can comingle at runtime. LC's interpretation is similar to Wordpress, Drupal, Joomla, and others which regard code running inside their process. Those CMS' regard all templates, plugins, widgets, themes, etc. as "derivative works" inheriting all rights and responsibilities of the CMS framework's GPL. When in doubt about how any license applies to anything, it's always best to check with the owner of the property. One of Mark Waddingham's more complete set of comments on GPL and LC Community is here: http://lists.runrev.com/pipermail/use-livecode/2016-March/224276.html The most relevant part may be this: If you don't wish to pay for a commercial license of some sort, then your option is to enter the GPL ecosystem of LiveCode Community and abide by its rules. If you do decide to pay for a commercial license then you can walk in both. I, personally, think that is entirely fair and reasonable. So in a sense we're both right, at least as far as meeting the company's expectations: As long as you maintain a current license to a proprietary edition, you can "walk in both"; if your license expires, distribution is GPL. This still leaves two questions: 1. Can a proprietary licensee choose ANY license for stacks distributed with the GPL engine, or must it be at least GPL-compatible (such as MIT)? 2. What if I write something in a licensed proprietary edition this morning, distribute it for use with a Community engine this afternoon, and then let my proprietary LC license lapse tomorrow? Does the license of what I've already sent out into the field somehow transform into GPL? How could any user know? The simplest way to avoid any questions about attempting to mix license types is to simply not mix them. GPL is pretty clear, and only becomes complex with efforts to circumvent its terms through mixing with other licenses. Here I follow one simple rule: I embrace the GPL where sharing under its terms is my goal; I avoid it where my goals are otherwise, including any potentially-gray area not already clarifed by the copyright owner. > I won't even start on that until I've finished fulminating over your > misspelling of whisky - but a response (or two) will come. My family is from Ireland and I live in the States. I raise my whiskey to toast your whisky, in the kinship of two related but regionally-distinct liquors, each spelled correctly. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.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: New(?) Idea for Standalones
I feel bad that you guys are sticking with me to no avail. Saving it first to Downloads or Desktop does not work. Sorry to be such a bother, Roger > On Mar 28, 2021, at 4:26 PM, Dev via use-livecode > wrote: > > Agreed. Save to the desktop and then try the right click Open command. > > Kelly > > Sent from my iPhone > >> On Mar 28, 2021, at 5:04 PM, Brian Milby via use-livecode >> wrote: >> >> I think the “attachment” is part of the issue. Save to downloads first? >> >> Sent from my iPhone >> >>> On Mar 28, 2021, at 6:00 PM, Roger Guay via use-livecode >>> wrote: >>> >>> Nope! Right clicking on a standalone I’m trying to share with my wife on >>> her iMac w OS 11.2 results in this menu: Open Attachment - Quick Look >>> Attachment - Save Attachment…. - Save to Downloads Folder - Share - Copy - >>> Speech >>> >>> Then, clicking on the “Open Attachment” menu item results in the same >>> response I reported earlier: a simple screen with this message: You do not >>> have permission to open the application “StackOmatic”. “Contact your >>> computer or network administrator for assistance” with a simple “OK” >>> button. Dead end as before! >>> >>> Further, at Kelly's suggestion to try and adjust settings in the Security >>> and Privacy System Preferences to downgrade standards to allow a one time >>> opening, I found nothing of the sort. >>> >>> So at this point, I think Kelly’s idea of someone with Apple credentials >>> building a certified standalone that runs stacks is the only short term >>> solution. If it helps, I and probably others, would be willing to pay a >>> reasonable fee for such gem. Otherwise, I and anyone else wanting to share >>> stacks, will have to jump through the increasingly ridiculous hoops that >>> Apple (and Windows?) place before us. OTH…. >>> >>> Ultimately, I really think that a LiveCodeLight app that runs stacks >>> without the IDE would be the best way to go to share stacks with friends, >>> family and colleagues. >>> >>> Roger >>> >>> >>> > On Mar 28, 2021, at 12:24 AM, scott--- via use-livecode > wrote: Kelly is correct. While holding down the control key, click and hold (or right click) to get an additional menu allowing you to choose to open the app. — Scott >>> >>> ___ >>> 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: New(?) Idea for Standalones
Agreed. Save to the desktop and then try the right click Open command. Kelly Sent from my iPhone > On Mar 28, 2021, at 5:04 PM, Brian Milby via use-livecode > wrote: > > I think the “attachment” is part of the issue. Save to downloads first? > > Sent from my iPhone > >> On Mar 28, 2021, at 6:00 PM, Roger Guay via use-livecode >> wrote: >> >> Nope! Right clicking on a standalone I’m trying to share with my wife on >> her iMac w OS 11.2 results in this menu: Open Attachment - Quick Look >> Attachment - Save Attachment…. - Save to Downloads Folder - Share - Copy - >> Speech >> >> Then, clicking on the “Open Attachment” menu item results in the same >> response I reported earlier: a simple screen with this message: You do not >> have permission to open the application “StackOmatic”. “Contact your >> computer or network administrator for assistance” with a simple “OK” button. >> Dead end as before! >> >> Further, at Kelly's suggestion to try and adjust settings in the Security >> and Privacy System Preferences to downgrade standards to allow a one time >> opening, I found nothing of the sort. >> >> So at this point, I think Kelly’s idea of someone with Apple credentials >> building a certified standalone that runs stacks is the only short term >> solution. If it helps, I and probably others, would be willing to pay a >> reasonable fee for such gem. Otherwise, I and anyone else wanting to share >> stacks, will have to jump through the increasingly ridiculous hoops that >> Apple (and Windows?) place before us. OTH…. >> >> Ultimately, I really think that a LiveCodeLight app that runs stacks without >> the IDE would be the best way to go to share stacks with friends, family and >> colleagues. >> >> Roger >> >> >> On Mar 28, 2021, at 12:24 AM, scott--- via use-livecode wrote: >>> >>> Kelly is correct. While holding down the control key, click and hold (or >>> right click) to get an additional menu allowing you to choose to open the >>> app. >>> — >>> Scott >> >> ___ >> 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: New(?) Idea for Standalones
I think the “attachment” is part of the issue. Save to downloads first? Sent from my iPhone > On Mar 28, 2021, at 6:00 PM, Roger Guay via use-livecode > wrote: > > Nope! Right clicking on a standalone I’m trying to share with my wife on her > iMac w OS 11.2 results in this menu: Open Attachment - Quick Look Attachment > - Save Attachment…. - Save to Downloads Folder - Share - Copy - Speech > > Then, clicking on the “Open Attachment” menu item results in the same > response I reported earlier: a simple screen with this message: You do not > have permission to open the application “StackOmatic”. “Contact your computer > or network administrator for assistance” with a simple “OK” button. Dead end > as before! > > Further, at Kelly's suggestion to try and adjust settings in the Security and > Privacy System Preferences to downgrade standards to allow a one time > opening, I found nothing of the sort. > > So at this point, I think Kelly’s idea of someone with Apple credentials > building a certified standalone that runs stacks is the only short term > solution. If it helps, I and probably others, would be willing to pay a > reasonable fee for such gem. Otherwise, I and anyone else wanting to share > stacks, will have to jump through the increasingly ridiculous hoops that > Apple (and Windows?) place before us. OTH…. > > Ultimately, I really think that a LiveCodeLight app that runs stacks without > the IDE would be the best way to go to share stacks with friends, family and > colleagues. > > Roger > > > >> On Mar 28, 2021, at 12:24 AM, scott--- via use-livecode >> wrote: >> >> Kelly is correct. While holding down the control key, click and hold (or >> right click) to get an additional menu allowing you to choose to open the >> app. >> — >> Scott > > ___ > 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: New(?) Idea for Standalones
Nope! Right clicking on a standalone I’m trying to share with my wife on her iMac w OS 11.2 results in this menu: Open Attachment - Quick Look Attachment - Save Attachment…. - Save to Downloads Folder - Share - Copy - Speech Then, clicking on the “Open Attachment” menu item results in the same response I reported earlier: a simple screen with this message: You do not have permission to open the application “StackOmatic”. “Contact your computer or network administrator for assistance” with a simple “OK” button. Dead end as before! Further, at Kelly's suggestion to try and adjust settings in the Security and Privacy System Preferences to downgrade standards to allow a one time opening, I found nothing of the sort. So at this point, I think Kelly’s idea of someone with Apple credentials building a certified standalone that runs stacks is the only short term solution. If it helps, I and probably others, would be willing to pay a reasonable fee for such gem. Otherwise, I and anyone else wanting to share stacks, will have to jump through the increasingly ridiculous hoops that Apple (and Windows?) place before us. OTH…. Ultimately, I really think that a LiveCodeLight app that runs stacks without the IDE would be the best way to go to share stacks with friends, family and colleagues. Roger > On Mar 28, 2021, at 12:24 AM, scott--- via use-livecode > wrote: > > Kelly is correct. While holding down the control key, click and hold (or > right click) to get an additional menu allowing you to choose to open the app. > — > Scott ___ 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: [bug] strange memory leak in LC
Big Sur 11.0.1, LC 9.6rc3 LiveCode seems to become unresponsive when my iMac goes to sleep and then wakes up and logs in. Don’t have any recipe for it, but when I when I left it overnight it had completely taken over my machine this morning. https://www.dropbox.com/s/cl2htkbe6a3e7y8/memory_leak.png?dl=0 I have 40GB of physical RAM, but LC was trying to use almost 300GB (virtual?) —Andrew Bell > > From: Phil Davis > To: How to use LiveCode > Subject: Re: [bug] strange memory leak in LC > Message-ID: <968340be-831e-f86f-7f1e-9cda1ed22...@pdslabs.net> > Content-Type: text/plain; charset=utf-8 > > I created a little "leak test" stack that runs the "leaks" shell command > against the processID of the LC engine that runs the stack. It checks > for new leaks every 60 seconds and lists the number and size of each new > leak found. I'm running it in LC 9.6.1 on 3 Macs right now - Catalina, > High Sierra and Big Sur. > > After about 30 minutes: > - LC on Big Sur (M1) has 10 leaks for a total of 688 bytes. > - LC on Catalina (Intel) has no leaks. > - LC on High Sierra (Intel) has no leaks. > > Just FYI - > Phil Davis > > > On 3/26/21 7:33 PM, John Balgenorth via use-livecode wrote: >> I am not personally using Bug Sur but if you make a standalone does >> it leak memory too or is this only with the development system? >> >> JB >> >>> On Mar 26, 2021, at 7:29 PM, scott--- via use-livecode >>> wrote: >>> >>> ?I?m running Big Sur and just got a warning from the OS that I was out of >>> application memory. Livecode was using 133.52 GB of memory. It had been >>> open for a couple days but it wasn?t doing anything. >>> -- >>> Scott Morrow >>> >>> Elementary Software >>> (Now with 20% less chalk dust!) >>> web https://elementarysoftware.com/ >>> email sc...@elementarysoftware.com >>> booth1-360-734-4701 >>> -- >>> On Mar 26, 2021, at 6:53 AM, Andre Garzia via use-livecode wrote: Sean, The stack was not running anything. It was simply opened. I don?t believe it would leak like that. Anyway, I?m monitoring to see if it happens again. A >> On 26 Mar 2021, at 13:01, Sean Cole (Pi) via use-livecode >> wrote: > Wow, Andre, that's impressive. That amounts to about 34MB per minute over > 48hrs. I've had a pretty massive stack (226MB file at the moment) on my > Mac > sitting here over the last week. Looking in the activity monitor, LC has > 987MB associated with it. and watching it over a period of time it remains > stable and even went down a tiny bit. > > I wonder if this is more an issue with Rosetta2 in this instance. Maybe > something in LC leaks because of the Rosetta transformation of the binary. > Perhaps, as a test, open the same stack on a non-AppleSilicon Mac and > watch > them both for how much memory they expend over a period of time. > > All the best with that. > > Sean > > On Fri, 26 Mar 2021 at 10:03, Andre Garzia via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> I have no idea what happened. I?m running LC 9.6.2-rc-3 on macOS Big Sur >> on M1 ISA (so it is running under Rosetta 2). I kept the IDE opened for a >> couple days, I was working on a gaziliion stacks at the same time and was >> not yet ready to close them. >> >> The stacks were not doing anything, they were not running ?send in time? >> commands or doing any kind of processing, they were just opened. Then >> macOS >> showed me a dialog I have never ever seen on macOS 10.x, a memory >> exhaustion dialog. Looking closer at it, LiveCode was using 100 GB of >> memory, as in Gigabyte, as can be seen on this screenshot: >> >> http://andregarzia.com/img/shots/lc-memory-leak.png < >> http://andregarzia.com/img/shots/lc-memory-leak.png> >> >> I remember things like the ?default button? causing leaks due to the >> animation and so on, but all I had was a bunch of custom stacks open and >> the script editor focused. Thats it. It was open since yesterday. >> ___ >> 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
Re: Unreliable File Deletion
> 28. mar. 2021 kl. 22:55 skrev J. Landman Gay via use-livecode > : > > Interesting. Does it also work on a different machine where you aren't the > owner? If so, everything we've heard is wrong. I haven’t tried on a machine where I am not the owner. This may be why it worked. When I come to think of it I am not certain I have been writing to the resource folder in any of the apps I have given my students, but I am quite certain I have read from such files. Tore ___ 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: Unreliable File Deletion
> 28. mar. 2021 kl. 21:20 skrev J. Landman Gay via use-livecode
> :
>
>
> Desktop and documents folders are okay, and it may be possible to read from
> the resources folder, but do you actually write to it? I don't know any OS
> that allows altering an executable, which includes Mac bundles.
I set up an application with the following code in the stack script:
on preOpenStack
put specialFolderPath("resources")& "/testfolder/" into tURL
create folder tURL
end preOpenStack
In the script of a button I put the following:
on mouseUp
ask "Write something to go into the resource folder:"
put it into tText
put "file:" & specialFolderPath("resources") & "/testfolder/test.txt" into tURL
put url tURL into tData
put tText & return after tData
put textEncode(tData,"UTF-8") into url tURLanswer url tURL
end mouseUp
I then build a standalone for Mac and started the application. After running
the script from the button three times I did find the file test.txt in the
folder named «testfolder» inside the _MacOS folder in the contents folder of
the app bundle. The file contained the exact three lines I had written. Whether
or not this will work on windows I don’t know as I do not have any computer
running Windows to try it on.
Best regards
Tore
___
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: Unreliable File Deletion
On 3/28/21 1:55 PM, Tore Nilsen via use-livecode wrote: I just made a test application where I am able to create a folder in the resources folder on preOpenStack. I then am able to read from and write to a document in this folder without any problem. This is on macOS Big Sur. The path to my folder in the resources folder in the app bundle is «Contents/_MacOS/testfolder/« and the application can write to this folder without any questions about permissions. Interesting. Does it also work on a different machine where you aren't the owner? If so, everything we've heard is wrong. -- 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: Unreliable File Deletion
R.H. wrote:
> The similar or same problem as you have: I want to delete the text
> file. The command I issue is "detele file ". The error it
> returns: "Can't delete file".
LC's result will tell you only the general fact that a file I/O
operation failed, but not why.
The syserror() function will tell you why, delivering the specific
integer code for the error the OS reported back to LC.
Establishing a habit of always including a call to sysError when
reporting a non-empty result will save you countless hours of diagnostic
time, e.g.:
delete file tFile
if the result is not empty then
answer the result &" ("& sysError() &")"
end if
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
ambassa...@fourthworld.comhttp://www.FourthWorld.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: Unreliable File Deletion
On 3/28/21 12:28 PM, ELS Prothero via use-livecode wrote: Folks, This alarms me. In my app, I write a file to specialFolderpath(“desktop”). What are the conditions to make this work on Apple or Windows standalones? Desktop works fine, every user has permissions to alter files there. -- 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: Unreliable File Deletion
On 3/28/21 1:40 PM, Tore Nilsen via use-livecode wrote: In MacOS the resources folder is part of the application bundle and resides within the content folder in that bundle. I have never encountered any problem with this folder even when using un-notarized and unsigned apps. I give away small apps to my students (both Mac and Windows) all the time and I use resources, desktop and documents as the main folders to write to and read from. All of these folders work OK. Desktop and documents folders are okay, and it may be possible to read from the resources folder, but do you actually write to it? I don't know any OS that allows altering an executable, which includes Mac bundles. -- 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: Help with androidStartAudioPlayingInBackground()
I've seen similar issues when trying to read other file types from the resources folder in an
Android standalone. Try copying the file to specialFolderPath("documents") and play it from
there. It's likely a permissions problem that I wish didn't exist.
On 3/28/21 1:24 PM, Derek Bump via use-livecode wrote:
Hello Everyone,
I was wondering if anyone has insight into the usage of
"androidStartAudioPlayingInBackground()", or can confirm that it works?
I setup a test stack that attempts to play a public domain MP3 using the following script but
nothing plays. I receive nothing from the function, and I'm getting the following in logcat:
LiveCode: JNI exception thrown when calling native method
on mouseUp
local tFile
put specialFolderPath("engine") & "/" & "spring_song.mp3" into tFile
if there is not a file tFile then
answer "File not found:" && tFile
end if
put androidStartAudioPlayingInBackground(tFile) into card field "result"
-- logcat: LiveCode: JNI exception thrown when calling native method
end mouseUp
I've tested this build using Community 9.6.2 (rc3) and 9.0.5, on an Android 9.0 Virtual Device
and a Android 9.0 phone. Same result across the board, nothing plays.
I did test and confirm the ability to play the audio file with "mobilePlaySoundOnChannel", but
I need background playback for my project to work. Also, I searched the LiveCode Quality
Control site for existing bugs (no results) and searched the forum a bit.
Does anyone have any ideas? Here is my test stack if you're willing to give it a shot on your
end: https://www.speedbump.io/shared/backgroundPlayTest.minimal.zip
Thank you in advance,
Derek Bump
___
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
--
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: Unreliable File Deletion
> 28. mar. 2021 kl. 20:40 skrev Tore Nilsen via use-livecode
> :
>
>
>
>> 28. mar. 2021 kl. 19:22 skrev Klaus major-k via use-livecode
>> :
>>
>> Hi friends,
>>
>>> Am 28.03.2021 um 19:11 schrieb R.H. via use-livecode
>>> :
>>> ...
>>> ... put specialfolderpath("resources") &"/temp.txt" into tFilePath
>>> ... put tOut into URL("binfile:")
>>> ...
>>
>> you may already know this, but this will not work in a standalone!
>> We will surely not have write permissions in that folder!
>>
>
>
> To the best of my knowledge, I think this is wrong. In MacOS the resources
> folder is part of the application bundle and resides within the content
> folder in that bundle. I have never encountered any problem with this folder
> even when using un-notarized and unsigned apps. I give away small apps to my
> students (both Mac and Windows) all the time and I use resources, desktop and
> documents as the main folders to write to and read from. All of these folders
> work OK. The user will be asked if they want to give the application
> permission to access these folders, but other than that I don’t know of any
> hiccups.
>
> I know that there are several restrictions when you deploy to various mobile
> platforms. These are explained in the Dictionary.
>
I just made a test application where I am able to create a folder in the
resources folder on preOpenStack. I then am able to read from and write to a
document in this folder without any problem. This is on macOS Big Sur. The path
to my folder in the resources folder in the app bundle is
«Contents/_MacOS/testfolder/« and the application can write to this folder
without any questions about permissions.
Best regards
Tore
___
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: Unreliable File Deletion
> 28. mar. 2021 kl. 19:22 skrev Klaus major-k via use-livecode
> :
>
> Hi friends,
>
>> Am 28.03.2021 um 19:11 schrieb R.H. via use-livecode
>> :
>> ...
>> ... put specialfolderpath("resources") &"/temp.txt" into tFilePath
>> ... put tOut into URL("binfile:")
>> ...
>
> you may already know this, but this will not work in a standalone!
> We will surely not have write permissions in that folder!
>
To the best of my knowledge, I think this is wrong. In MacOS the resources
folder is part of the application bundle and resides within the content folder
in that bundle. I have never encountered any problem with this folder even when
using un-notarized and unsigned apps. I give away small apps to my students
(both Mac and Windows) all the time and I use resources, desktop and documents
as the main folders to write to and read from. All of these folders work OK.
The user will be asked if they want to give the application permission to
access these folders, but other than that I don’t know of any hiccups.
I know that there are several restrictions when you deploy to various mobile
platforms. These are explained in the Dictionary.
Best regards
Tore Nilsen
___
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
Help with androidStartAudioPlayingInBackground()
Hello Everyone,
I was wondering if anyone has insight into the usage of
"androidStartAudioPlayingInBackground()", or can confirm that it works?
I setup a test stack that attempts to play a public domain MP3 using the
following script but nothing plays. I receive nothing from the function,
and I'm getting the following in logcat: LiveCode: JNI exception thrown
when calling native method
on mouseUp
local tFile
put specialFolderPath("engine") & "/" & "spring_song.mp3" into tFile
if there is not a file tFile then
answer "File not found:" && tFile
end if
put androidStartAudioPlayingInBackground(tFile) into card field "result"
-- logcat: LiveCode: JNI exception thrown when calling native method
end mouseUp
I've tested this build using Community 9.6.2 (rc3) and 9.0.5, on an
Android 9.0 Virtual Device and a Android 9.0 phone. Same result across
the board, nothing plays.
I did test and confirm the ability to play the audio file with
"mobilePlaySoundOnChannel", but I need background playback for my
project to work. Also, I searched the LiveCode Quality Control site for
existing bugs (no results) and searched the forum a bit.
Does anyone have any ideas? Here is my test stack if you're willing to
give it a shot on your end:
https://www.speedbump.io/shared/backgroundPlayTest.minimal.zip
Thank you in advance,
Derek Bump
___
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: Unreliable File Deletion
Folks,
This alarms me.
In my app, I write a file to specialFolderpath(“desktop”).
What are the conditions to make this work on Apple or Windows standalones?
Bill
William Prothero
https://earthlearningsolutions.org
> On Mar 28, 2021, at 10:22 AM, Klaus major-k via use-livecode
> wrote:
>
> Hi friends,
>
>> Am 28.03.2021 um 19:11 schrieb R.H. via use-livecode
>> :
>> ...
>> ... put specialfolderpath("resources") &"/temp.txt" into tFilePath
>> ... put tOut into URL("binfile:")
>> ...
>
> you may already know this, but this will not work in a standalone!
> We will surely not have write permissions in that folder!
>
> As a workaround I would probably use -> specialfolderpath("temporary")
> Or even write the text to -> the tempname
>
> Both are available on all platform and you do not have to think about
> deleting that file later, the OS will take care of this. :-)
>
>
> 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: Unreliable File Deletion
Hi friends,
> Am 28.03.2021 um 19:11 schrieb R.H. via use-livecode
> :
> ...
> ... put specialfolderpath("resources") &"/temp.txt" into tFilePath
> ... put tOut into URL("binfile:")
> ...
you may already know this, but this will not work in a standalone!
We will surely not have write permissions in that folder!
As a workaround I would probably use -> specialfolderpath("temporary")
Or even write the text to -> the tempname
Both are available on all platform and you do not have to think about
deleting that file later, the OS will take care of this. :-)
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: Unreliable File Deletion
@ Peter Reid
Your message found my attention.
Also I am working on Windows 10 and have the same problem using LC 9.6.1
Indy version.
The problem with copying text to the clipboard and then pasting it into
other applications results in inserting double lines. I think there was a
discussion about the clipboard on the forum or here recently. Instead of
directly copying the text, I create a temp file temp.txt, insert the text
to be copied, then read the file and then I can paste the text reliably.
The file is then deleted.
The similar or same problem as you have: I want to delete the text file.
The command I issue is "detele file ". The error it returns:
"Can't delete file".
So, I tried using a forced Shell command which did not work (probably it
needs Admin rights). But the standard Shell command deletes the file.
Here is the script snippet:
// The original purpose of using this script as part of a larger script is
to copy column names of a database table to the clipboard and insert them
anywhere.
## Script snippet calling Shell (Windows 10/64)
// Save data to external file to get rid of wrong carriage returns in
Windows
// Copy data as text to the clipboard
// Space are replaced by "." for this message list
// A temporary text file is created and shall be deleted after usage
// tOut contains the resulting data from before...
// myMsg is a separate custom message handler that directs messages either
to the message box, writes to a log file or places the message into a
field, or all together...)
... local tOut
... local tFilePath
... local tResult
... local tCmd
... put specialfolderpath("resources") &"/temp.txt" into tFilePath
... put tOut into URL("binfile:")
... put URL("binfile:") into tOut
... set the clipboarddata["text"] to tOut
... // Delete temp file
... delete file ("binfile:")
... put the result into tResult
... if "can't delete that file" is in tResult then
.. myMSG tHInfo & "File could not be deleted." & tFilePath --> My
message handler
.. if the platform is "win32" then
. set the hideConsoleWindows to true
. replace "/" with "\" in tFilePath
. put quote & tFilePath & quote into tFilePath
. put "del " into tCmd -- this shell command works for me
. put shell(tCmd) into tResult
. put CR& the result after tResult
. /* Comment: Error messages appear when using "rmdir /s /q"
. to force delete the file
. Error message: Invalid switch - "Users". */
. myMSG tHInfo & tResult --> My message handler
.. end if
... end if
##/ End script snipped
So, if other users have the problem that a file cannot be deleted with the
"delete file" command (even though it he file tit is not flagged as part of
another process or flagged as "cant delete") then this seems to be a bug.
I would report it if I am not the only one seeing the problem.
Roland
___
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: New(?) Idea for Standalones
Kelly is correct. While holding down the control key, click and hold (or right click) to get an additional menu allowing you to choose to open the app. — Scott > On Mar 27, 2021, at 8:33 PM, Dev via use-livecode > wrote: > > Roger > > On your wife’s machine - if you right click the app and choose Open from the > context menu, do you get more options about opening? > > If you adjust settings in the Security and Privacy System Preferences can you > downgrade standards to allow a one time opening? > > If neither of these work, then it seems that the player app will need to be > notarized and perhaps even stapled. If one of the already certified > developers were to make such an app using their credentials, perhaps the rest > of us could just download it from their site and play our own stacks with it. > > Interested in anyone else’s thoughts on work arounds to Apple’s security. > > Kelly > >> On 27 Mar, 2021, at 9:10 PM, Roger Guay via use-livecode >> wrote: >> >> >> Here is a report on the back door approach to opening a standalone on MAC OS >> 11.2: >> >> I built a stack precisely as Jacqueline specified and made a Mac standalone >> of it. I checked to make sure it worked on my own computer. I then sent the >> standalone to my wife’s computer – another Mac running the same OS 11.2. >> Double-clicking the standalone on her computer, resulted is a simple screen >> with this message: You do not have permission to open the application >> “StackOmatic”. “Contact your computer or network administrator for >> assistance” with a single “OK” button. >> >> I then checked System Preferences - Security & Privacy - General Tab. There >> was no “Open Anyway” button. >> >> Dead in the water! >> >> I humbly submit that we need a LiveCodeLight app from a certified developer >> that runs stacks without the IDE >> >> Roge >> >> >> >> ___ >> 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
