Skip to content

Latest commit

 

History

History
42 lines (25 loc) · 2.62 KB

path.md

File metadata and controls

42 lines (25 loc) · 2.62 KB

Models

Path

The Path atom helps to organize (global/static) file- and directory paths. Once a path has been specified, it can be used as a variable within other paths. This way it is possible to reuse already existing paths and to specify relative paths. If you would like to adapt a path in future, you only have to change it once, instead of going through all places where the path is applied.

The GenericInput atom also allows to specify paths. Those paths might be varied within Studies. On the other hand, the (global/static) paths within the Path atom ar thought to be constant for a distinct user/computer.

(Instead of using the Path atom it would also be possible to define paths as pure JavaScript string variables in the source code. Those variables could also be concatenated to mimic relative paths. However, that approach would have a disadvantage: If the source code is imported to the Tree View and later re-exported to the Editor View, the dependencies between the paths are lost. You would end up with absolute paths instead of the originally related (relative) paths. Therefore, we recomment to use the Path atom to organize your (global/static) file- and directory paths.)

Source code

./src/model/path/path.js

Construction

A new Path atom is created either

  • from the context menu of an existing Models atom in the Tree View or

  • by calling the corresponding factory method of the Models atom in the source code of the Editor View:

    ...
    let path = models.createPath();	   
    path.createDirectoryPathVariable('workingDirectory', 'D:\treez');
    path.createFilePathVariable('inputFile', '{$workingDirectory$}\input.txt');

Child atoms

The context menu of the Path atom allows to add child atoms:

GenericInput GenericInput