Perhaps the best way to describe it is to show a rough sketch of the directory structure.
project
|---- app1
|
|---- app2
|
|---- app3
|
|---- javascript-libaries
|
|---- rapydscript-imports
The app directories house the RapydScript code of the main application file, the resultant Javascript, ML code for the HTML file and the resultant HTML file.
The javascript libraries directory houses RapydSript code and resultant Javascript code for separately compiled library modules which are pulled in by script tags in the HTML file.
The rapydsscript-imports directory is a place where I want to house uncompiled Rapydscript code for importable modules which can be used in all the applications and are, in effect, pulled in by the Rapydscript compiler.
At the moment I have only two or three small importable RapydScript modules, used in only one application, so they currently reside in the relevant app directory However, I would like to import them into the other application as well but do not really want to duplicate them in each app directory. Nor do I want to put them in the rapyscript/src/lib directory of my RapydScript installation. I also envisage making more use of importable modules in the future. So what I'm looking for is some way to give the RapydScript compiler a path to be searched for the relevant .pyj files when it comes across an import statement.
I did have a look at the compiler code but concluded that rapydscript/src/lib was the only place searched for imports. My suggestion of a compile flag seemed a possibly easy way to give the compiler an additional search path but there are obviously other ways it could be done, for instance via an environment variable, which is one of the ways which Python uses for a similar purpose.
I hope that makes the purpose of the post clear. It is not a desperately urgent problem but a suggestion for something to be thought about for the future.