New(?) Idea for Standalones

Mon Mar 29 14:20:42 EDT 2021

Roger.

For about eight users in my business I distribute standalones for desktop only, both Mac and Windows versions. These are developed on a Mac. Simple to update and make, simple to give away, simple to use.

That is the aspect of this thread that I do not understand, perhaps misreading that it is somehow problematic to do what I do without issue. I am certain I simply have this wrong.

I do all this in the Community version. I do not sell apps at all, though I own an Indy license just as a way to help LC a little. So I wonder if I am a scofflaw. If everyone was on a Mac, I might have simply distributed updated stacks, and have LC resident on all the other machines. But of course, the fact that most use Windows makes that impossible, and I will not use a Windows machine unless I have to. Anyway, leaving the IDE open is risky.

Someone not too long ago wondered why we could not give standalones to friends for use on their phones, that is, what difference does the platform make, if it is only for acquaintances. In mobile, I certainly see how this might be abused.

Craig

> On Mar 29, 2021, at 9:45 AM, Craig Newman <craig at starfirelighting.com> wrote:
> 
> I have been following this thread with interest, and have no idea what anyone is talking about.
> 
> I make and update standalones regularly on my Mac, and distribute them to many Windows and Mac desktop users in my company. All for “personal’ use.
> 
> Somewhere in the middle of all this, I thought that the issue was distributing to mobile, and saw the problem, but then noticed that the issue was distributing to desktop, and became confused
> 
> So though I may be breaking the law, what prevents anyone from doing what i do?
> 
> What am i missing?
> 
> Craig
> 
>> On Mar 29, 2021, at 1:17 AM, John Balgenorth via use-livecode <use-livecode at lists.runrev.com> wrote:
>> 
>> 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 <use-livecode at lists.runrev.com> 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 <use-livecode at lists.runrev.com> 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 <use-livecode at lists.runrev.com> 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 <use-livecode at lists.runrev.com> 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 <use-livecode at lists.runrev.com> 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 <use-livecode at lists.runrev.com> 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 <use-livecode at lists.runrev.com> 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 at 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 at 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 at 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 at 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 at 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 at 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 at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 