Thanks for that (I updated the link here so it can be read easily).
That discussion is as I suspected (a good thing, one less documentation element that needs updating <g>), about bringing a stack's script into the execution context on the server. It makes no attempt to deliver it to the browser, simply part of a larger discussion of options for using stacks as script containers on the server.
One reason that I thought would be usefull to distribute stacks this way, is that I need a lot of users to have access to a program that I make changes very often during a week or even a day, and would be very usefull in order to all of them have always the update.
HTML export in LC is challenged, for reasons far too complicated to get into here. If we instead focus on your goal, your option of using a standalone to download it from a web server is by far the best for both you and your users. Bonus points that it's also the simplest.
Another reason is that I dont want to distribute the whole stack file for security reasons.(I know there is the option to password protect but...)
What are those security concerns?
If you had been successful in delivering a copy of your stack to the browser, like anything else in the browser the user would have a copy of it and could save it, examine it, etc.
Let's take a look at what you need to protect and we can find a good way to handle that.
Also If I make a SPLASH standalone app that loads a stack from a webserver, then I didnt manage to save the stack back after the user makes changes.
The good news is that you don't actually want to do that.
After all, if someone using a web browser can alter the contents of a file on your server, anyone with a web browser could do so, including the bad guys (the Internet is full of 'em).
liveme touched on that in his reply above. Good thoughts there. Let's learn more about what you want to save back to the server, and we can find a good way to make that happen safely and securely for both your user's data and your server resources.
But generally was somehow a test, because I found the above lesson,and sounded quite handy to me. Sorry if I missunderstood the writings in it.
No worries. In fact, the distinction between client and server is not clear to many in our community. Questions like yours come up all the time. I've been discussing the possibility of co-authoring a short ebook on the topic of getting oriented to LC client-server work, and if that moves forward questions like yours are very valuable in guiding our table of contents.
Please never feel shy about asking anything here. Over the years I've seen that for every question asked, there's at least 20 others with the same question who didn't post it. Every question here helps others.