In-Browser edition does not install files if not in @lib$

[circe]

INSTALL @lib$+"custom\useful" (for example) fails "File or Path not Found". Works OK in BBCSDL. INSTALL @lib$+"useful" seems OK.

Earlier editions of BBCSDL did not support sub-folders of @lib$ as I recall. Did In-Browser edition get missed out?

The folder "custom" is a linked folder, although this may not be relevant.

[Richard Russell]

Earlier editions of BBCSDL did not support sub-folders of @lib$ as I recall. Did In-Browser edition get missed out?

On a very simplistic test, sub-folders of @lib$ do seem to be working in the in-browser version here. This is what I did:

1. Created a sub-directory test in my local @lib$ folder.
2. Copied a dummy .bbc file (it could have been anything) into that directory.
3. Built a trivial web app (which simply exits to immediate mode) with the dummy file embedded.
4. Ran the app in my browser, navigated to @lib$/test in immediate mode.
5. The embedded file was seemingly present.

You can try running the app I created here. In immediate mode enter *cd /home/web_user/lib/test - do you see the file memusage.bbc there?

INSTALL @lib$+"custom\useful" (for example) fails "File or Path not Found". Works OK in BBCSDL. INSTALL @lib$+"useful" seems OK.

If that's literally what you wrote, it will inevitably fail: non-Windows operating systems don't recognise \ as a directory delimiter! You must always use /, fortunately that's accepted in Windows as well so there's no cause to do anything different. Your code as listed would fail in MacOS, Linux, Android and iOS too.

[Richard Russell]

non-Windows operating systems don't recognise \ as a directory delimiter!

That is called out in the differences document where it says this:

3. File System
   a. To ensure cross-platform compatibility, a forward-slash (/) should always be used as the
      directory delimiter, not a backslash (\).