| 22 | * '''Custom save:''' Saving several modules in different files (as it should be) is quite laborious. For each module (or set of modules), the user has to select the module(s) to save, then click on "save selected modules" and finally choose the appropriate file. The longer the list, the more exhausting it gets. And finally the user usually prefers to save all modules in one file. Which does not fit to the modularisation concept.[[BR]] |
| 23 | A solution would be the use of "saving scripts":[[BR]] |
| 24 | -- the user could set for each ProMoT session a "custom save" by choosing once a file in a directory.[[BR]] |
| 25 | -- this file would contain a list of actions: |
| 26 | {{{ |
| 27 | save module1 file1 |
| 28 | save module2 module3 file2 |
| 29 | save-all file3 |
| 30 | ... |
| 31 | }}} |
| 32 | -- this "custom save" would be linked to an icon in the GUI allowing a fast saving[[BR]] |
| 33 | -- a confirmation could be asked at the first saving to make sure the user is using the script he intended to. |
| 34 | |