Saving data in standalone

[jbv via use-livecode]

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 a layout, and finally export as a pdf file.
The problem is that all this work will be done in successive sessions,
and between each step there will be the need to temporary save the
work to retrieve it in the next session.
And I'm not sure about the best way to save groups within an LC
standalone and retrieve everything in a similar layout in the
next session, or even if it's possible.
Any idea and suggestion are welcome.

Thank you in advance.
jbv

___
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: Saving data in standalone

[Paul Dupuis via use-livecode]

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 
file, a remote database, etc. - whatever works for your app.



On 5/16/2024 12:51 PM, jbv via use-livecode wrote:

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 a layout, and finally export as a pdf file.
The problem is that all this work will be done in successive sessions,
and between each step there will be the need to temporary save the
work to retrieve it in the next session.
And I'm not sure about the best way to save groups within an LC
standalone and retrieve everything in a similar layout in the
next session, or even if it's possible.
Any idea and suggestion are welcome.

Thank you in advance.
jbv

___
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: Saving data in standalone

[Paul Dupuis via use-livecode]

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, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Saving data in standalone

[Craig Newman via use-livecode]

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 standalone 
from, you can add any number of stack files. These are files that contain any 
number of stack and substacks.

My standalone is never used for anything but navigating to other stacks 
attached to it. Once navigation is effected, the splash stack hides itself, its 
entire purpose fulfilled.

Takes just little practice. You can make one right now with two stacks in two 
separate stack files. Have the executable one go to the other one, and you are 
on your way.

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 said "custom file extension"
> 
> ___
> 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: Saving data in standalone

[Craig Newman via use-livecode]

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 said "custom file extension"
> 
> ___
> 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: Saving data in standalone

[Peter Bogdanoff via use-livecode]

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 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 said "custom file extension"
>> 
>> ___
>> 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: Saving data in standalone

[Paul Dupuis via use-livecode]

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 is using 
specialFolderPath("documents") and then create a folder structure for 
your company or app in the user's Documents folder. OSes are becoming 
more and more "sandboxed" to prevent malware and dumb user mistakes from 
wrecking apps or the OS itself.



On 5/16/2024 4:43 PM, Peter Bogdanoff via use-livecode wrote:

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 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 said "custom file extension"

___
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: Saving data in standalone

[Mike Kerner via use-livecode]

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 *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 is using
> specialFolderPath("documents") and then create a folder structure for
> your company or app in the user's Documents folder. OSes are becoming
> more and more "sandboxed" to prevent malware and dumb user mistakes from
> wrecking apps or the OS itself.
>
>
> On 5/16/2024 4:43 PM, Peter Bogdanoff via use-livecode wrote:
> > 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 <
> use-livecode@lists.runrev.com> wrote:
> >>
> >> 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 <
> use-livecode@lists.runrev.com> 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 said "custom file extension"
> >>>
> >>> ___
> >>> 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
>


-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
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: Saving data in standalone

[Tom Glod via use-livecode]

I have a plugin that is not complete which can save livecode groups and all
of their properties, custom properties and scripts.  If you'd like I'll
send you some of the code. PM me.
Should be super easy to find the code u need, and then inverse it.
If you did that it would help me complete the plugin and I could release it.

On Thu, May 16, 2024 at 8:05 PM Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:

> 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 *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 is using
> > specialFolderPath("documents") and then create a folder structure for
> > your company or app in the user's Documents folder. OSes are becoming
> > more and more "sandboxed" to prevent malware and dumb user mistakes from
> > wrecking apps or the OS itself.
> >
> >
> > On 5/16/2024 4:43 PM, Peter Bogdanoff via use-livecode wrote:
> > > 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 <
> > use-livecode@lists.runrev.com> wrote:
> > >>
> > >> 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 <
> > use-livecode@lists.runrev.com> 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 said "custom file extension"
> > >>>
> > >>> ___
> > >>> 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
> >
>
>
> --
> On the first day, God created the heavens and the Earth
> On the second day, God created the oceans.
> On the third day, God put the animals on hold for a few hours,
>and did a little diving.
> And God said, "This is good."
> ___
> 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: Saving data in standalone

[Bob Sneidar via use-livecode]

Including datagrids? I have a save and restore method for Datagrids, but I 
don’t think I back up ALL the properties, just the critical ones.

Bob S


On May 20, 2024, at 5:58 PM, Tom Glod via use-livecode 
 wrote:

I have a plugin that is not complete which can save livecode groups and all
of their properties, custom properties and scripts.  If you'd like I'll
send you some of the code. PM me.
Should be super easy to find the code u need, and then inverse it.
If you did that it would help me complete the plugin and I could release it.

On Thu, May 16, 2024 at 8:05 PM Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:

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 *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 is using
specialFolderPath("documents") and then create a folder structure for
your company or app in the user's Documents folder. OSes are becoming
more and more "sandboxed" to prevent malware and dumb user mistakes from
wrecking apps or the OS itself.

___
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: Saving data in standalone

[Tom Glod via use-livecode]

Hey Bob, I just tested it and it captured the controls and properties and
custom property sets it would take extra work to "restore" a datagrid,
because we have to package the template stack.. but i think it will
work.  Unless there is a property that the datagrid control has that is
unique to it and is not captured.  I can see the hierarchy of controls
...etc.

PM me I can send you the stack if you want to take a look


On Tue, May 21, 2024 at 11:06 AM Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Including datagrids? I have a save and restore method for Datagrids, but I
> don’t think I back up ALL the properties, just the critical ones.
>
> Bob S
>
>
> On May 20, 2024, at 5:58 PM, Tom Glod via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> I have a plugin that is not complete which can save livecode groups and all
> of their properties, custom properties and scripts.  If you'd like I'll
> send you some of the code. PM me.
> Should be super easy to find the code u need, and then inverse it.
> If you did that it would help me complete the plugin and I could release
> it.
>
> On Thu, May 16, 2024 at 8:05 PM Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com>
> wrote:
>
> 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 *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 is using
> specialFolderPath("documents") and then create a folder structure for
> your company or app in the user's Documents folder. OSes are becoming
> more and more "sandboxed" to prevent malware and dumb user mistakes from
> wrecking apps or the OS itself.
>
> ___
> 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: Saving data in standalone

[Richard Gaskin via use-livecode]

When I've used a group as a document view, sometimes I just copy the group to 
an invisible stackfile for storage.

The engine handles stackfiles efficiently and robustly.

If we had viewers it'd save me the copy step.
https://quality.livecode.com/show_bug.cgi?id=2786

Richard Gaskin
FourthWorld.com



Bob Sneidar wrote:
>
> Including datagrids? I have a save and restore method for
> Datagrids, but I don’t think I back up ALL the properties,
> just the critical ones.
>
> Bob S
>
>
>> On May 20, 2024, at 5:58 PM, Tom Glod wrote:
>>
>> I have a plugin that is not complete which can save livecode
>> groups and all of their properties, custom properties and
>> scripts.

___
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