Closed jbsarrodie closed 7 years ago
In English:
Merci ;-)
From this discussion
- Archi Save action saves the "temp.archimate" file as usual, but also triggers a Grafico export in the working tree. So there's no more need for a Save action as part of the plugin.
- Publish action:
- checks if model has to be saved or if a commit is needed (uncommited changes in the working tree). If yes then ask the user if he agrees to do so (a "no" answer means cancelling the publication). If user answers "yes" then go through the commit action described below.
- shows a dialog to the user that explain what "publish" means and asks for a confirmation
- proceeds with the publication itself (is confirmed by user)
- Commit action:
- shows a dialog to the user that explain what "commit" means and asks for a commit comment (which can't be empty). User can cancel of continue.
- saves model (which triggers a Grafico export)
- proceeds with the commit.
What's the Refresh story?
I have:
Should we offer to do a commit or not? Or just do a Grafico export?
Done in a local document (in french). I now have to write it on a wiki page (in english)... moving it to Sprint #2
Done in a new wiki page.
Define workflow associated with each actions. For example: "Save" could check if remote model is accessible and if yes synchronise everything in the background (if no: save changes locally and remind user to synchronise later)
Actions identified for the moment are: ~Add/Open/Remove Bookmark, Save Model~
(in french, will be translated soon)