19

The new KRDC application on 4.2.2. is very nice, but in my case, who work with multiple customers that have multiple environments and server machines, I think a little improvement could be done on KRDC.

Mainly my idea is to make KRDC as a startup launcher for remote access. This includes the already existing rdp, vnc protocols, but I think it should also include the ssh and fish protocols.

My idea:

KRDC instead of having an history folder has Workspaces and sub-workspaces.

Workspaces define a set sub-workspaces that have servers. In my case I would use workspaces for containing customer machines, so machines from one customer are not mixed with machines of other customer on the history folder.

Sub-Workspaces are used for logic division of machines, for example DEVelopment machines, QUALity machines, PRE-production machines, PRODuction machines and so on.

So when I started KRDC I'de get a previously opened Workspace, but In a drop-down box I select another workplace and sub-worspace and only the machines of my interest are shown.

For example if I go to custommer B, I select ClientB workspace and DEV environment because it's there that are the machines I wan't to access. If I go to custommer F I select ClientF, and so on...

Now Workspaces have inside it a set of machine icons, or machine list, that have the machine name (used for identification) and a set of properties. The properties for the icon/item define the kind of access: rdp, vnc and ssh, hostname, credentials, settings X-forwarding, and so on.

Just double click, and access the server according to the protocol by opening the associated application

If I right-click the icon/list item, I can open Dolphin for file transfer with the machine. Dolphin will open the machine with smb/fish protocol.

Of course this idea could be a totally new application named Krash ->Kde Remote Acess SHell

It sounds like this could also be done though a bookmark system: just create folders for each client, with shortcuts to each machine in there.

Angel Blue01 wrote:It sounds like this could also be done though a bookmark system: just create folders for each client, with shortcuts to each machine in there.

Yes, also that can be doable, as long another remote access protocols are also supported.

It appears that KRDC in 4.2.2 already supports bookmarks.

Angel Blue01 wrote:It appears that KRDC in 4.2.2 already supports bookmarks.

Yes,, but it not supports folders and sub-folders on bookmarks as far as I know.

Tag fixed.

BlackCat you mentioned in your intro to this idea that additional protocols would be nice. I have raised this as a seprate idea.
viewtopic.php?f=83&t=62342
Found this idea when looking for duplicates for the additional protocols idea

I love KRDC except for one thing. It does not support file transfer. If that feature is added it would be my only choice for VNC & RDP connections.

kl7k wrote:I love KRDC except for one thing. It does not support file transfer. If that feature is added it would be my only choice for VNC & RDP connections.

KRDC does support file transfer. It uses rdesktop behind the scenes and you can put extra options into the expert options part of e.g. a bookmark:
try:

-r disk:tmp=/home/you/share/