nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Improve "load()" instruction

medini_1036016653

Dear Jan,

currently "load()" is able to handle relative paths using ".", "..". It would be useful to be able to reference the script base directory (or some other fixed level) using "~", as is done in UNIX.

Usecase: Typically start off script development in some test.js in the highest level of the script folder structure. When I'm satisfied with my script I rename it and move it to some sub-folder. During that step I need to pay attention to adapt all the "load()" instructions by prepending "../" the correct number of times, so that the helper libraries are still found during script execution.

Best regards

Peter

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

I got it,

should be fairly straight to implement.

Thanks for the idea

Jan

All comments

medini_1024169437

Hi Peter,

I think I understand the problem but not the proposed solution.

The ~ parameter is interpreted as "find the file anywhere in the scripts folder"?

In Linux its typically the home folder right? So if we use that as "home" you anyway would have to change the load path, right?

Btw. load() also accepts absolute paths and URLs.

Happy Scripting

Jan

medini_1036016653

Hi Jan,

I wish for a way to reference to the project's base, not knowing the location of the project in my overall filesystem (as that might also change).

Example:

- script a is located in "scripts/FMEDA/a.js"

- script b is located in "scripts/b.js"

- library is located in "scripts/.lib/factory.js"

In script a and b I want to use the same command to load factory.js, for example "load(~/.lib/factory.js)". "__filedir" is not of direct use, as it would be either "scripts/FMEDA" or "scripts", so I would need extra logic to find out, whether/how deep the script is nested.

Best regards

Peter

medini_1036016653

The proposed solution missed quotes, so here again (as editing posts is not possible here):

load("~/.lib/factory.js");

This instruction would work for both scripts, independent on their location in the scripts folder structure. Yes, in Linux "~" references the home directory (quick search resulted in this explanation at StackOverflow).

medini_1024169437

I got it,

should be fairly straight to implement.

Thanks for the idea

Jan

medini_1024169437

Peter, just to mention that this is now available with 2020 R2.0

Happy Scripting

Jan

medini_1036016653

Hi Jan, thank you. Good to know!

medini_1033829014

Hi Jan,

is there also any way (e.g. in the project settings) to set a user variable like SCRIPTS_BASE_DIR, or is it still a fixed space (e.g. config/scripts) within the current project?

In particular for the libraries (and I think this was the question in this case) it would be good if I can set it to any location on my disk, not just within the current project). Assume I have 20 medini projects, all with scripts (all the same or different ones, this does not matter), and most of them refer to library scripts like factory.js or finder.js. And now imagine that you find a bug in finder.js and deploy a new version on the download page. I would have to replace 20 finder.js scripts. Rather I'd like to have one separate folder (e.g. C:\mediniwork\scriptlibrary) and make a setting (e.g. SCRIPT_LIBRARY) in the medini project to let medini know this folder. And then use something like

load ("$SCRIPT_LIBRARY$\finder.js");

Would this be possible, or a handy extension?

Bernhard

medini_1024169437

Hi Bernhard,

the load function can do already some more, you can pass URLs but also absolute paths.

Its not documented because it is assumed that you want to write scripts residing in the project and thus using relative paths at all times.

load("http://myspace.org/fancy-script.js");

should work as well as

load("C:\\MyScripts\\fancy-script.js");

You may define your own SCRIPT_LIBRARY prefix.

Happy Scripting

Jan

medini_1024169437

PS: Maybe at some day we can post the libraries to a server so scripts can include them similar to famous public JS and CSS files like jQuery or Bootstrap.

Jan

medini_1033829014

Thanks, that's a good idea!

I could have imagined that it works that way (if it works with relative paths, why not so with abolute ones?) but sometimes you just need someone to tell you...

So I would write

var SCRIPT_LIBRARY = "C:\\myfancystuff\\lib\\"

load(SCRIPT_LIBRARY + "finder.js");

Bernhard

medini_1024169437

Exactly :-)