LiveCode Forums.

Hi Bogs,
Depends your context, I use these two options:
External files storing option
I use external files if I want the user can see easy or if I have to manage a big collections (> 3500 png files for 155 Mo)

Stack storing option
I use external stacks to allows a modular approach for OSX and Windows ("modular stack" can be downloaded). For this use I store some contents in stack.
Unfortunatly Apple consider stack as code and doesn't agree stacks download for an iOS app on AppleStore).

Of course you can do that by iTunes if your app allows "file sharing"

Best regards
Jean-Marc

bidgeeman wrote: I don't feel stupid for asking basic questions just slightly uninformed

I sure hope I didn't imply anything like you (or anyone) being stupid bidge, as that absolutely was not my intent. I was just offering a pov, your question was not stupid at all and your own proposed solution wasn't terrible either. I am extremely sorry if you took my reply as any kind of slam, it certainly wasn't intended as such.

I myself am a noob to Lc, and unlike your question I have asked quite a few that I am sure seem pretty stupid to others. Questions are and always will be the starting point to learning, you keep right on asking in whatever format helps *you*.

@ Jean-Marc,
both points show an excellent contrast for use, I should have pointed out that my statement was to clarify the different kinds of external "files" that could be used with this statement

Klaus wrote:Remember that standalones can NOT save themselfes!
You will always need an external file for this.

My bad for being 'murky'

I also forgot to mention that url "file:x" could just as easily be url "binfile:x" if he does not wish easy access.

back @ bidge -
Hopefully again to help,
file - plain, easily readable/editable to you and your end user, from what your explanation looks like to me, not what you want to use.
binfile - binary format, as you said earlier will not stop anyone determined to see it, but will stop most ordinary 'users'.
saving using splashstack - as Jean-Marc points out, allows you to save that stack in a modular way, you can just add it to other projects further down the road, is binary and, if I understand it correctly, can be encrypted as well even in the community vers.

Something that isn't full proof, but again, helps with people who just use your program and are not determined to crack it -
...test for existence of the file you are checking, and don't create it in code. If the file doesn't exist at the location your looking for it, the program has (probably) been copied or moved.

Oh dear no...I did not take it as a slam bogs
Just wanted to share what it is like as a beginner when it comes to trying to decipher what is going on in LC code. Sometimes we just miss the basics You are a great support and I really thank you for your comments on this thread.

Bidge

Boy am I glad to hear that Bidge, especially as written responses are so easily misunderstood and my style of writing isn't the greatest around

Hi All,
I remember there is a way to prepar a standalone as we want.
We can catch "savingStandalone" message to reset properties of all controls before building the standalone.
Best regards
Jean-Marc