After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 762255 - gtkplacesview: selecting a recent server should connect immediately
gtkplacesview: selecting a recent server should connect immediately
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
3.22.x
Other Linux
: Normal enhancement
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-02-18 09:39 UTC by romu
Modified: 2018-05-02 16:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gtkplacesview: connect on recent server selection (858 bytes, patch)
2016-10-12 12:00 UTC, Ernestas Kulik
none Details | Review

Description romu 2016-02-18 09:39:11 UTC
Hi,
Small enhancement to make Nautilus even more efficient.

Use case: connect to an external server
1. Click on "+ Other Locations"
2. Type or choose an address in the "Connect to server" field
3. Click on "Connect" to effectively start the connection

Why this last step? My suggestion is when the user chooses a server address in the list, the connection should be initiated immediately. This would remove the need to click on "Connect".
Comment 1 Ernestas Kulik 2016-10-12 12:00:49 UTC
Created attachment 337507 [details] [review]
gtkplacesview: connect on recent server selection

Currently, selecting a recent server only populates the URI entry.
Connecting to it as well is more efficient.
Comment 2 António Fernandes 2017-08-28 12:05:28 UTC
(In reply to romu from comment #0)
> Why this last step?
It may be useful to edit URI before connecting. See bug 753550 for an example.
Comment 3 GNOME Infrastructure Team 2018-05-02 16:57:47 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/599.