This is the place for wishes, suggestions and features in order to improve ProMoT in the future.

ProMoT User Interface

• Models in the tree: A differentiation (other than using the tree structure) between exportable models and simple modules (that are usually incorporated into those models) in the tree would be appreciable. For instance, using a different font and/or icon in the tree.

• Special characters in slot-names: It would be very useful if one can use special characters, upper case and hyphenation for the slot-names.

• 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 classes" 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.
  A solution would be the use of "saving scripts":
  

-- the user could set for each ProMoT session a "custom save" by choosing once a file in a directory.
-- this file would contain a list of actions:

        save module1 file1
        save module2 module3 file2
        save-all file3
        ...

-- this "custom save" would be linked to an icon in the GUI allowing a fast saving
-- a confirmation could be asked at the first saving to make sure the user is using the script he intended to.

ProMoT Visual Editor

• Search for elements (Compound, reaction ...): A feature like Edit-> Search would be useful to locate easily a compound or a reaction in a large network/module. The searched element could be showed by a blinking square (like for a warning information but blinking) that would disappear at the next event (next click). It would be nice to allow for the search a string in a slotname (not only an exact slotname).

• Shortcut Activation/Inhibition: Until now all activ and not gates taken to generate the activation/inhibition edges are directed from north to south. And if the edge is from south to north or sidewise, it has to be changed manually. It would be appreciable that the edge direction is detected automatically and the appropriate gates chosen. Since the gate names are quite standardized (activ, activ-lr, activ-du ...), one could check if those classes exist and use them. If they are not available, the default gate could be chosen.

• Copy/Paste? of slots: A context menu in the visual editor containing the copy/paste functions would be useful so that the copied slots can be pasted where the context menu was called. And not in the middle of the middle as it is now.