Another, possible simpler solution:
a) what you change the standalone setting in the standalones, you can, if
wanted, test building, the app *without* being forced to save the stack.
b) Somehow you would have to address the Standalone setting in RAM or save to
some *.temp file ... when you cre
On 8/3/19 7:53 AM, Brian Milby via use-livecode wrote:
No, that is a required file for the app and needs to be in the repo.
Ah. My bad. I assumed the .app was the standalone itself.
--
Mark Wieder
ahsoftw...@gmail.com
___
use-livecode mailing list
No, that is a required file for the app and needs to be in the repo.
Thanks,
Brian
On Aug 3, 2019, 10:40 AM -0400, Mark Wieder via use-livecode
, wrote:
> On 8/3/19 7:14 AM, Sannyasin Brahmanathaswami via use-livecode wrote:
> > When working collaborately with a framework on Git Hub. There is alw
On 8/3/19 7:14 AM, Sannyasin Brahmanathaswami via use-livecode wrote:
When working collaborately with a framework on Git Hub. There is always an
issue of the stack that will be made the standalone for the app.
No changes are made to binary MyMainStack.app other than settings in the
standalone,
When working collaborately with a framework on Git Hub. There is always an
issue of the stack that will be made the standalone for the app.
No changes are made to binary MyMainStack.app other than settings in the
standalone, which you may does simply for testing.
Now, if you "pull" the project
