GNOME Bugzilla – Bug 339133
Add "Connected Servers" history to "Connect to Server" dialog
Last modified: 2010-08-07 09:42:54 UTC
"Connect to Server" of the panel menubar should remember the last entered connection data by the user. It is inconvenient if one makes a typo when setting up a connection and has to enter everything again. The connection data should be saved for each connection method (SFTP/WebDAV/etc.) the user chooses. If one makes a typo and wants to fix this, the natural way of doing so would be over the context menu of the created icon for the connection on the desktop and to choose "Properties". IMHO it would be a good idea to somehow integrate the "Connect to Server" interface into the properties-GUI for a server-connection. PS: I am sorry if the category of this feature request is wrong, but I did not find a better one.
Thanks for your bug report! I don't think users are likely to create two subsequent server connections with almost identical data, so don't really like the idea of caching old data unless we provide a whole history of connections. We should rather have editable server connections, as proposed under bug 316403. Would you be OK with that solution as well?
Editable server connections are exactly what I've had in mind, so thats OK to me! A connection history would be far better than the suggestion I have made. Is something like this already planned?
> A connection history would be far better than the suggestion I have made. > Is something like this already planned? No, it is not yet planned, if you have some time feel free to hack away and come up with a patch :). For now, it might be enough to provide the user with the currently connected servers that could be used as a pattern for a new server, i.e. duplicated.
I would very much like to do this, but unfortunately I have not much time at hand. The earliest date I could start working on this would be at the beginning of July. So if there is nobody working on it until then, I would do it.
Access to a list of recent servers is covered by bug 139105. Closing this as a duplicate. Please reopen if I got this wrong though, and thanks for the report. :) *** This bug has been marked as a duplicate of bug 139105 ***