Namespace NMF.Glsp.Protocol.ModelData

ExportSvgAction: The client sends an ExportSvgAction to indicate that the diagram, which represents the current model state, should be exported in SVG format. The action only provides the diagram SVG as plain string. The expected result of executing an ExportSvgAction is a new file in SVG-format on the underlying filesystem. However, other details like the target destination, concrete file name, file extension etc. are not specified in the protocol. So it is the responsibility of the action handler to process this information accordingly and export the result to the underlying filesystem.

RequestExportSvgAction: A RequestExportSvgAction is sent by the client (or the server) to initiate the SVG export of the current diagram. The handler of this action is expected to retrieve the diagram SVG and should send an ExportSvgAction as response. Typically the ExportSvgAction is handled directly on client side.

RequestModelAction: Sent from the client to the server in order to request a graphical model. Usually this is the first message that is sent from the client to the server, so it is also used to initiate the communication. The response is a SetModelAction or an UpdateModelAction.

SaveModelAction: Sent from the client to the server in order to persist the current model state back to the source model. A new fileUri can be defined to save the model to a new destination different from its original source model.

SetDirtyAction: The server sends a SetDirtyStateAction to indicate to the client that the current model state on the server does not correspond to the persisted model state of the source model. A client may ignore such an action or use it to indicate to the user the dirty state.

SetEditModeAction: Sent from the client to the server to set the model into a specific editor mode, allowing the server to react to certain requests differently depending on the mode. A client may also listen to this action to prevent certain user interactions preemptively.

SetModelAction: ent from the server to the client in order to set the model. If a model is already present, it is replaced.

SourceModelChangedAction: Sent from the server to the client in order to indicate that the source model has changed. The source model denotes the data source from which the diagram has been originally derived (such as a file, a database, etc.). Typically clients would react to such an action by asking the user whether she wants to reload the diagram or ignore the changes and continue editing. If the editor has no changes (i.e. is not dirty), clients may also choose to directly refresh the editor by sending a RequestModelAction.

UpdateModelAction: Sent from the server to the client in order to update the model. If no model is present yet, this behaves the same as a SetModelAction. The transition from the old model to the new one can be animated.