How to in LC for Desktop and the Web?

Paul Dupuis paul at
Thu Dec 9 18:33:28 EST 2021

Following up (in case someone has an answer):

I see in the description for SpecialFolderPath(), that under HTML5 
(platform) the following are available:
"temporary": A folder where temporary files can be placed
"engine": The folder where the standalone initial file system is extracted
"resources": The resources folder where files or folders specified in 
the Standalone Builder are located.

But where do these point to:

1) When the HTML5 app is running from the local file system (say 
Windows) in a browser


2) When the HTML5 app is running from a server URL in a browser

If no one knows the answers, I can always run a set of tests to 
determine the values.

On 11/24/2021 7:15 PM, Paul Dupuis via use-livecode wrote:
> I have an LC application that currently runs on Window and macOS, that 
> I want to try to get running under LC 10 for the web. One 
> characteristic of the app is that it opens a number of external 
> stacks. On desktop platforms, these external stacks (outside the .EXE 
> (windows) or .app package (macOS) are found in a folder at the same 
> level as the installed application.
> So if the app is installed at C:\Program Files\MyApp\MyApp.exe
> The the folder containing the external stacks is at C"\Program 
> Files\MyApp\FolderOfStacks\
> I get the path of the mainstack and use it to construct the path to 
> the folder
> If I build for Web, is there some equivalent model for external stacks?
> I get that I may need to have a:
> switch platform()
>   case "Win32"
>   case "macOS"
>      -- load external stacks the way I do now
>      break
>   case "web"
>      -- load external stacks some other way
>     break
> end switch
> but what is the web best practice for that 'some other way"? And is it 
> different if I am testing locally vs hosting MyApp on a server?
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your 
> subscription preferences:

More information about the use-livecode mailing list