Bug 375631

Summary:	UX "Monitor Remote Machine" should always be available in File Menu
Product:	[Unmaintained] ksysguard	Reporter:	Tom <twshield>
Component:	ksysguard	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	wishlist	CC:	lueck, nate, richard.llom
Priority:	NOR	Keywords:	usability
Version First Reported In:	5.9.0
Target Milestone:	---
Platform:	Other
OS:	All
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Tom 2017-01-27 21:48:24 UTC

I found the fact that the Monitor Remote Machine item in the File menu is only available once a new tab has been created to be confusing.  I've made a suggestion to the documentation maintainers about this, but if the entry was always in the file Menu, I probably would have not had to look in the documentation at all.

So my suggestion is to have the "Monitor Remote Machine" item always in the File Menu and if a user created tab does not exist, then either prompt to create one or just create one before the Remote Machine dialog is displayed.  Because deleting a tab is so simple, it's probably fine to just create a new tab if no user tabs exist.

Thanks, Tom.

Comment 1 Tom 2017-01-29 17:41:03 UTC

Let me also say that I did not know ksysguard did remote hosts until I found it in a list of remote monitoring programs via google search.  Having Monitor Remote Machine always visible in the file menu would also be good advertising for what your nice program can do.

Comment 2 Christoph Feck 2019-03-11 16:18:00 UTC

Richard, please only set the Usability flag if you need feedback from the Usability team. Otherwise, just add the "usability" keyword.

Comment 3 Richard Llom 2019-03-11 16:25:09 UTC

ah yeah, mixed it up...
fixed

Comment 4 Richard Llom 2019-03-11 18:40:41 UTC

Issue is still in v 5.15

Comment 5 Christoph Cullmann 2024-09-23 21:01:27 UTC

ksysguard is no longer maintained, in Plasma 6 there is the Plasma system monitor for this task.

If your wish is still valid for the Plasma 6 replacement, please re-open and we can move this bug to the new product, thanks!