- Aug 07, 2017
-
-
Georges Basile Stavracas Neto authored
Following the design decision on other panels, make the central column of the Network panel cover at most a third of the window, or more depending on the width of the window. https://bugzilla.gnome.org/show_bug.cgi?id=785581
-
Georges Basile Stavracas Neto authored
The last remaining network device to be updated is the VPN device, and this patch is the result of this effort. The changes were mostly towards cleaning up and removing unecessary code. By removing the info labels, many getters were removed as well. In order to achieve a listbox-like UI, a couple of UI refactorings. https://bugzilla.gnome.org/show_bug.cgi?id=785581
-
Georges Basile Stavracas Neto authored
Since each VPN will be a row in a listbox, we can't rely on NetVPN:add_to_stack() to handle the header. This header must, then, be handled by the panel itself. For now, we just open the already available dialog to add connections, when the ideal approach (to be implemented yet) is to move the contents of this dialog in a built-in popover. https://bugzilla.gnome.org/show_bug.cgi?id=785581
-
Georges Basile Stavracas Neto authored
If we build with strict compile check, the pointer alignment gets messed up. So just cast to gpointer to satisfy the compiler. https://bugzilla.gnome.org/show_bug.cgi?id=785581
-
Georges Basile Stavracas Neto authored
According to the lastest mockups [1], the Proxy section is now composed of a row with the state of the proxy, and a settings button that leads to a dialog where one can configure the different proxy settings. This commit ports the current code to do that, and various changes took place to made this happen. Namely: * A new ProxyMode enum was added to improve readability and improve the semantic of the code. No more random numbers are present. * The current widgets for editing proxy settings were repacked into a GtkStack (so that we keep an homogeneous sizing), and the GtkStack itself was moved into a new dialog. With that, we can just set the stack page, rather than controlling the visibility of all individual widgets. * Many unused widgets were removed. * The combo box was replaced by 3 radio buttons. Now, there's no need to deal with GtkTreeIters anymore. Another refactoring of the code that led to more readable and smaller code. Overall, these changes made the code be more readable, smaller codebase with a smaller surface for mistakes. https://bugzilla.gnome.org/show_bug.cgi?id=785581
-
Georges Basile Stavracas Neto authored
When calling for the wireless security widgets, the code simply assumes that the corresponding GType is initialized. This may not always be true, which leads to a nasty crash every time e.g. we open the network connection editor dialog. This commit fixes that by introducing a new standard macro wrapping wireless_security_get_type(), and ensuring the type is initializing when calling wireless_security_init(), thus protecting every code path from this crash. This commit also makes CePageSecurity use the new macro for better legibility. https://bugzilla.gnome.org/show_bug.cgi?id=785581
-
Georges Basile Stavracas Neto authored
The current "Wired" section UI is still optimized for the old, multi-page panel layout. Recent work [1], however, suggest that this should change and the standard widgets be rearranged. This commit, then, implements this new UI for the wired devices UI by using a listbox row when there's only one profile (ditching out the old info labels), and moving and deleting the bottom action buttons. https://bugzilla.gnome.org/show_bug.cgi?id=785581
-
Georges Basile Stavracas Neto authored
After introducing the new single-column layout, we can easily hit the case where there are too many connections and/or devices and the panel gets way too tall. To fix that, wrap all the widgets inside a scrolled window that only scrolls vertically. https://bugzilla.gnome.org/show_bug.cgi?id=785581
-
Georges Basile Stavracas Neto authored
The current Network panel is composed of a single stack and a treeview to select the currently visible stack page. Each stack page represents a connection or device. The new Network panel, however, has none of the concept of selectable pages. In the new layout, all connections and devices appear all at once in a more compact and simpler fashion. This commit, then, starts moving towards a unified, pageless panel by adding all the connections and devices to different stacks. These different stacks are transient to the network object, and are added at appropriate boxes, giving the panel a unified layout. This has some serious implications in the design of the current code. Most of the code removals were related to the treeview and different pages handling. No more tree model madness is present, and the devices are now stored in a plain simple GPtrArray. After this patch, NetObject:add_to_stack isn't a good code design choice anymore. This will be addressed in a future patch. https://bugzilla.gnome.org/show_bug.cgi?id=785581
-
Georges Basile Stavracas Neto authored
The current Network panel class relies on GtkBuilder when it could use a more modern feature that is the template class. By making it a template class, not only the Network panel is slightly more performant, but it's also simpler and easier to read. This commit, then, turns the Network panel into a template class, and cleans up the code to make it work. https://bugzilla.gnome.org/show_bug.cgi?id=785581
-
Georges Basile Stavracas Neto authored
The Network panel UI file uses deprecated widgets and has many lines of needless code. This commit just cleans it up, as a preparation for turning the Network panel into a template class. https://bugzilla.gnome.org/show_bug.cgi?id=785581
-
Georges Basile Stavracas Neto authored
This should be in the Wi-Fi patchset... https://bugzilla.gnome.org/show_bug.cgi?id=785581
-
Georges Basile Stavracas Neto authored
The Network panel is not really a deriverable type, and since after 61d7abe7 we can use the utility macros. Thus, this commit removes all the boilerplate code and turns CcNetworkPanel into a final class. https://bugzilla.gnome.org/show_bug.cgi?id=785581
-
Georges Basile Stavracas Neto authored
The Network panel does not deal with Wi-Fi devices anymore, and does not make sense to have the Airplane Mode switch in there, since it is now available at the Wi-Fi panel. This commit then removes the Airplane Mode switch from the Network panel. https://bugzilla.gnome.org/show_bug.cgi?id=785581
-
-
-
Matej Urbančič authored
-
- Aug 05, 2017
-
-
- Aug 03, 2017
-
-
Marek Cernocky authored
-
Marek Cernocky authored
-
- Aug 02, 2017
-
-
Jordi Mas authored
-
- Aug 01, 2017
-
-
-
-
Marek Cernocky authored
-
- Jul 31, 2017
-
-
- Jul 27, 2017
-
-
- Jul 26, 2017
-
-
- Jul 25, 2017
-
-
-
-
Piotr Drąg authored
-
Felipe Borges authored
This is a typo related to the fix at commit 7d254442.
-
Georges Basile Stavracas Neto authored
All the new panels have a standard 24px margin now, so since we're already splitting the info pages into separate panels, also fix this minor annoyance. https://bugzilla.gnome.org/show_bug.cgi?id=779216
-
Georges Basile Stavracas Neto authored
This commit only fixes some very minor cosmetic changes like int → gint, simplifies the code by using g_autofoo, et cetera. https://bugzilla.gnome.org/show_bug.cgi?id=779216
-
This commit shall show the panels separate. Some panels are hidden in current design, while some other panels are hidden in new shell design. https://bugzilla.gnome.org/show_bug.cgi?id=779216
-
Some panels shall be shown only in current design, And some other panels shall be shown only in new Shell design. So let's have a code that would help us do that https://bugzilla.gnome.org/show_bug.cgi?id=779216
-
The displayed panel should always match the selection in the panel list. That implies that after swapping out the list (for instance by browsing Devices or Details), we need to update the panel rather than keeping the old one around until the user manually selects a row. The easiest way to achieve that is to activate the panel list after a view change when appropriate. https://bugzilla.gnome.org/show_bug.cgi?id=783429
-
For shortcuts that support multiple bindings, the disabled state is expressed as an empty list rather than a list with a single empty element. While the latter certainly works as expected as far as the actual keybinding is concerned, the shortcut will show up as modified even if it is disabled by default. Explicitly setting bindings to the empty list when a shortcut is disabled fixes this. https://bugzilla.gnome.org/show_bug.cgi?id=784620
-