Open sf-migrator-bot opened 8 years ago
HI Zibi, we agree at DESY with the names you propose. Many thanks. Ah!, only one detail, you have mistyped the name of the diffractometeralignment macro, but I suppose it was just in the e-mail.
Regards,
Teresa
Original comment by: teresanunez (http://sf.net/u/tere29)
Diff:
--- old
+++ new
@@ -15,7 +15,7 @@
Furthermore we are going to add new ones when SEP4 gets integrated:
* ubmatrix
-* diffractometeralighment
+* diffractometeralignment
* hklscan
I this feature-request I would like to discuss the eventual renaming of the scrpts. I propose the following names (in parentheses the old name):
@@ -30,7 +30,7 @@
* sardanah5toascii (h5toascii)
* sardanah5tospec (h5tospec)
* sardanaubmatrix
-* sardanadiffractometeralighment
+* sardanadiffractometeralignment
* sardanahklscan
In order to maintain the backwards compatibility we should leave the possibility to run the scripts with the old names during few releases (to be agreed how long and how should we do that e.g. symbolic links or duplicated scripts, etc...).
Original comment by: reszelaz (http://sf.net/u/zreszela)
Actually even better would be to use sardana command with subcommands similarly as it was done in taurus. Implementation could be done with click (it is already used for showscan command).
The solution to avoid Taurus logs discussed in taurus-org/taurus#1190 should be also considered when implementing the Sardana CLI.
Hello,
In the following email Frederic had raised an issue of sardana scripts' names. Up to now sardana redistributes the following sctipts:
Furthermore we are going to add new ones when SEP4 gets integrated:
I this feature-request I would like to discuss the eventual renaming of the scrpts. I propose the following names (in parentheses the old name):
In order to maintain the backwards compatibility we should leave the possibility to run the scripts with the old names during few releases (to be agreed how long and how should we do that e.g. symbolic links or duplicated scripts, etc...).
We should keep in mind that the change of the Tango Device Server executable names will have an impact on the already defined server instances in the Database (Starter requires the exact names of the executable and the server name).
Reported by: reszelaz ( http://sf.net/u/zreszela )
Original Ticket: sardana/tickets/441