tms gui needs to expose the "repo-register" and "repo-unregister"..

[JPeterMugaas]

I think the GUI should expose the "tms repo-register" and "tms repo-unregister" commands. Those commands are useful especially as more developers adopt the TMS SmartSetup system and more becomes avaiable to it.

[wlandgraf]

It's a good suggestion for now, but we plan to have a centralized place (remote) where the repository registration will be global to Smart Setup. That will end up making repo-register and repo-unregister not very often used commands.

Thus, I wonder if we should clutter the GUI with "obscure" commands. If one wants to do something low level in Smart Setup, the command-line can always be used.

My suggestion is we wait for this new centralized registration and go back to this to see if it will still really be needed.

[agallero]

Thus, I wonder if we should clutter the GUI with "obscure" commands. If one wants to do something low level in Smart Setup, the command-line can always be used.

I was thinking about that. We have many commands that are could come handy from time to time, but would clutter the GUI if we added them all. The idea is to keep tmsgui simple after all.

But maybe it makes sense to have a "Advanced" button that either displays a menu or a form with less-used, still useful commands? Stuff that I think that menu could have right now:

• open tms command line -> starts a cmd.exe in the correct folder, so we can tell the users "go to advanced->open cmd and type..."
• tms doctor -> just call tms doctor in a cmd window
• tms repo register/unregister -> Now we are back on topic :)
• show log -> calls tms log-view

More stuff could be added in the future. But the idea is not to clutter the UI with thousands of commands, so hiding them under an "Advanced" or similar thing might be an option.

[wlandgraf]

Yep, it might be.

Note that the problem is not only cluttering the UI, but also adding more things to maintain and more potential bugs. :-) repo-register will need an UI to enter the parameters - name of repository, type of VCS (GIT/SVN), etc. - so it's more and more things to do. And, if the command is in "advanced" menu, still how much better it is than "open cmd" and writing it directly? Does it worth the effort to create a GUI for it?

But well, I definitely thing that at the very least "open tms command line" is useful.

[agallero]

Yes, I am aware that the main thing here is the dev time, more than the cluttered UI :) And it is simple for me to speak since I am not doing it...

Still, except repo-register/unregister, all of those are one-liners. Just execute a command. repo-register needs indeed to show a form, but it can be simple too: A combobox with git/svn and an editbox with the url.

And, if the command is in "advanced" menu, still how much better it is than "open cmd" and writing it directly?

I believe it makes a difference, even if little. People are likely to press that "advanced" button just for curiosity, and find a "doctor" there, and press it. If he opens a cmd, he will just get a black screen where he has to type stuff.