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 756337 - Connections Dialog: Use a Gtk.Stack instead of opening new windows
Connections Dialog: Use a Gtk.Stack instead of opening new windows
Status: RESOLVED DUPLICATE of bug 756344
Product: polari
Classification: Applications
Component: general
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: Polari maintainers
Polari maintainers
Depends on:
Blocks:
 
 
Reported: 2015-10-10 10:40 UTC by Bastian Ilsø
Modified: 2015-10-10 14:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bastian Ilsø 2015-10-10 10:40:54 UTC 
When I press the "Edit Connection" button or the "New Connection" button, a new dialog appears on top of the Connections dialog. We should avoid stacking dialogs on top of each other like that.[0]

It would be better to use a Gtk.Stack and transition.

[0] https://developer.gnome.org/hig/stable/dialogs.html.en
Comment 1 Florian Müllner 2015-10-10 12:21:32 UTC 
(In reply to Bastian Ilsø from comment #0)
> It would be better to use a Gtk.Stack and transition.

Maybe, maybe not. It's worth a try, but I'm a bit skeptical about combining a stack and "external" list controls - IMHO a stack works very well when selecting a list element switches to a details view for that element. On the other hand having a toolbar element move away from underneath your pointer after activating it feels rather odd to me ...

An alternative could be to split the window: turn the existing list into a sidebar, and move the create/edit dialog's content to the right.

It's also closely related to bug 756336, to an extent that it might be better to combine the two into a "overhaul connections dialog" issue.
Comment 2 Bastian Ilsø 2015-10-10 14:05:37 UTC 
Sounds good, I opened a new bug 756344 with that name now.

*** This bug has been marked as a duplicate of bug 756344 ***