Hi list,
I am working on an app for a client who will use it as a standalone.
Basically users will be able to import data such as images, text and
even html from various sources. All these data will self organize in
different groups that the user will be able to select, move around
and organise in
My suggestion would be to have your Standalone create a new stack with
the user's work and save that stack under a customer file extension for
your app.
You can not actually save data in a standalone. you must save it to some
source outside of the standalone - and stack, a text file, a binary
On 5/16/2024 12:58 PM, Paul Dupuis via use-livecode wrote:
save that stack under a customer file extension
That should have said "custom file extension"
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, u
There is much discussion about this on the forum.
The contents of the executable, the actual standalone you make from a stack,
cannot be saved by any OS. I use what is know as the “Splash Stack” method,
alluded to by Paul above.
In the Application Builder of the stack you are making the actual
I did not explicitly mention that any and all of the attached stacks are
savable.
Craig
> On May 16, 2024, at 1:31 PM, Paul Dupuis via use-livecode
> wrote:
>
> On 5/16/2024 12:58 PM, Paul Dupuis via use-livecode wrote:
>> save that stack under a customer file extension
>
> That should have
Craig,
Saving: the stacks within the MacOS package and the Windows Applications
folders can be saved—within that location?
Can new stacks/files be written to those same folders?
Peter
> On May 16, 2024, at 4:26 PM, Craig Newman via use-livecode
> wrote:
>
> I did not explicitly mention that
You can save external stacks or created on the fly stacks where ever you
have *write* (and read) permission on your OS.
Increasingly, whether macOS or Windows, that is not the Applications
(macOS) or Program Files/Program Files (x86) (Windows) folders. I find
the SAFEST place to save something
this is also how levure operates, so if you build with levure, you can just
do this with stacks in the project
On Thu, May 16, 2024 at 5:08 PM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:
> You can save external stacks or created on the fly stacks where ever you
> have *wr
