As part or testing I made a shared code module read only, the IDE gave the expected error messages, but the code complied and ran.
It feels right to be able to make the shared modules read only so you don't inadvertently change it while working on one app and make it unusable for others.
But I'm not sure of the knock on's, or how it would be correctly integrated.
Note that there is a "safety mechanism" for shared modules. The IDE checks whether the file was externally modified and if yes then it asks you whether you want to overwrite changes (before saving the file). This is especially important when the same module is open in two instances of the IDE.
I was thinking more along the lines of trying to avoid the situation where code could be amended in the shared module, then 3 weeks later compiling a different project that also uses the shared code that won't work anymore.
I know it's down to developers to manage their own code, but being able to plug these potential holes would be useful.
When exporting a project as a zip file the shared modules are not added to the zip file.
Could you add an option to add them to the zip file or not add them.
This would be intesting for posting projects in the forum.
Now as we have shared modules is there an advantage to compile modules to libraries ?
I imagine that for Classes it might be an advantage.
And also to reduce the number of modules in the IDE.
Shared modules can be used instead of compiled libraries in many cases.
However there are cases that a compiled library might be more suitable. Consider HttpUtils2 for example. It is made of two modules and depends on other libraries as well. It is easier to add it as a library with a single click.