Changes between Version 3 and Version 4 of ModelingProjects


Ignore:
Timestamp:
Jan 10, 2007, 3:56:13 PM (19 years ago)
Author:
mirschel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ModelingProjects

    v3 v4  
    11== Modeling Projects ==
    22
    3 ProMoT started as a tool working purely based on source-code in MDL files.
    4 but over the years graphical use in complex modeling projects has become much more important.
    5 To reflect this changes in mode of operation is is suggested to organize
     3ProMoT started as a tool working purely based on source-code in MDL-files.
     4But over the years graphical facilities in complex modeling projects has become much more important.
     5To reflect this changes in mode of operation it is suggested to organize
    66modeling in ModelingProjects, that help to keep the main classes, icons and
    77source files together.
    … …  
    1313- What is the current state of modeling in ProMoT? -
    1414
    15 Modeling in ProMoT takes place based on source files or is done with the help of the
     15Modeling in ProMoT takes place based on source files (MDL-files) or is done with the help of the
    1616graphical user-interface. The sources are loaded into ProMoT, translated to class-objects
    17 (ModelingEntities) and changed by graphical editors in memory.
     17(ModelingEntities) and changed by the graphical editors in memory (temporarily).
    1818
    19 The ModelingEntities can be saved as MDL-code via Save All Classes and Save Selected Classes
    20 in the File-Menu. There is no simple Save, which saves the classes to the files they
     19The ModelingEntities can be saved as MDL-code via the options "Save All Classes" and "Save Selected Classes"
     20in the File-Menu. There is no simple option "Save", which saves the classes to the files they
    2121originally come from.
    2222
    23 Users often work with LOAD.mdl files which do not define new classes themselfes but
     23Users often work with LOAD.mdl files which do not define new classes themselves but
    2424
    25   * include libraries defining general classes
     25  * include libraries defining general classes (e.g. logical library including logical operator classes)
    2626  * include files containing own ModelingEntities
    2727  * adjust settings for finding the correct versions
    2828    of these files and the correct icons
     29  * easy control of comment out and in of model parts
    2930
    3031The LOAD.mdl files constitute implicitly modeling projects, but have to be changed
    31 only on the source level.
     32only on the source level not within the GUI.
    3233
    3334=== What is a Project? ===
    … …  
    3536A project is a data-object in ProMoT that keeps and tracks all
    3637ModelingEntities and associated data for a modeling project on a specific
    37 topic in the real world. It should facilitate the organization and
    38 general configuration of ProMoT for a specific task.
     38topic in the real world (e.g. logical model of the EGF signaling pathway).
     39It should facilitate the organization and general configuration of ProMoT
     40for this specific task.
    3941
    4042=== What should a Project provide? ===
    … …  
    4345
    4446  * It should know a base-directory for the project, where specific sources, icons and
    45     generation-results are kept in subdirectories.
    46   * The project should keep track of all global settings, which affect the behaviour of the Gui,
     47    generation-results are kept in a meaningful subdirectory structure.
     48  * The project should keep track of all global settings, which affect the behavior of the GUI,
    4749    the model-generation process and others. Currently these settings are kept globally in the
    4850    home-directory of the user.
    … …  
    5557    different classes and a LOAD.mdl which includes the sources and defines the project.
    5658  * It allows higher level operations like exporting all necessary files to share
    57     the sources and icons with another user or split a project if a part of it has become too big.
     59    the sources, icons and settings with another user or split a project if a part of it has become too big.
     60  * It should remember the currently defined Visual Scenarios to retain the visual appearance of the model
     61    in a consistent way.
    5862
    5963==== What are Open Questions for the Implementation? ====
    6064
    61   * Should there be only one Project open in ProMoT at the time or is it necessary to have multiple?
     65  * Should there be only ONE project open in ProMoT at the time or is it necessary to have multiple?
    6266  * If classes are saved to their originating source-files, is it then necessary to keep the
    6367    comments inside these files?
    64   * Are classes defined exclusively for one Project or are they used in a shared way.
     68  * Are classes defined exclusively for ONE project or are they used in a shared way.
    6569
    6670====== Space for comments ======