https://bugs.kde.org/show_bug.cgi?id=461085
--- Comment #11 from Markus Wernig <pub...@wernig.net> --- (In reply to tcanabrava from comment #10) > I did indeed consider a less intrusive way to develop the plugin, but then > I realized that a lot of people that answered my request to "how do you use > profiles in konsole" were using the *profile* manager as a way to interact > with different SSH connections (some of them having over 20 - 40 profiles > that differed only in name and the ssh command. This made me think that a > plugin *for* ssh was needed. OK, so there already *was* a way to manage SSH connections in a graphical interface (albeit not perfect). >From my point of view, this approach only lacked the possibility to separate the connections into groups/categories, else it was quite viable (and less error-prone than the current plugin approach). So a (presumably) lightweight CSS update to the Konsole Profiles widget could have achieved much of the same effect the sshmanager plugin strives for. I still do not understand how the profile hack people were using to manage SSH lead to the intrusive approach that was taken with the plugin. Even if there was a general need for a SSH plugin, why choose to make it compulsory for all Konsole users and even make it parse the command line (which, in my opinion, was a less than wise design choice)? After all, Konsole is a TERMINAL emulator, not a SHELL. As such, it should respond only to defined control/escape sequences, and nothing else. > I do understand your concerns and I plan to implement a way to disable / > unload plugins in the future, I would very, very much appreciate that! But using that approach would require writing an entire plugin manager for Konsole, which seems rather unlikely to happen (given that there are no more than two "plugins" at the moment). So I would rather suggest a flag to be stored in the global section of konsolesshconfig, which should tell the plugin whether to be active or not: [Global plugin config] manageProfile=false -> enablePlugin=true|false > *I* ould personally accept a patch that allows to unload plugins (such the > one in kate) so people can use the plugins if they want, and not being > forced to. I have no meaningful experience in graphical widget frameworks more recent than BorlandC and MFC. But I will try to support any of your efforts to remedy the current situation by all means available to me. Best /m -- You are receiving this mail because: You are watching all bug changes.
