applications/gnome-control-center
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
gnome-control-center/panels/network/connection-editor/ip4-page.ui

374 lines
18 KiB
Text
Raw Normal View History

network: Break out wifi details code and add editing support This code is fairly independent of the rest, and we don't want net-device-wifi.c to become too massive and unmaintainable. The code in connection-editor/ is fairly similar to nm-connection-editor, with some simplification because we currently only edit wireless connections. The code in wireless-security/ is almost a straight copy of the same code in nm-connection-editor, with some changes to the .ui files to make them fit better in the new design.
2012-12-09 19:38:32 -05:00
<?xml version="1.0" encoding="UTF-8"?>
<interface>
<!-- interface-requires gtk+ 3.0 -->
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<template class="CEPageIP4" parent="AdwBin">
network: Break out wifi details code and add editing support This code is fairly independent of the rest, and we don't want net-device-wifi.c to become too massive and unmaintainable. The code in connection-editor/ is fairly similar to nm-connection-editor, with some simplification because we currently only edit wireless connections. The code in wireless-security/ is almost a straight copy of the same code in nm-connection-editor, with some changes to the .ui files to make them fit better in the new design.
2012-12-09 19:38:32 -05:00
<child>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<object class="GtkScrolledWindow">
<property name="hscrollbar_policy">never</property>
network: Break out wifi details code and add editing support This code is fairly independent of the rest, and we don't want net-device-wifi.c to become too massive and unmaintainable. The code in connection-editor/ is fairly similar to nm-connection-editor, with some simplification because we currently only edit wireless connections. The code in wireless-security/ is almost a straight copy of the same code in nm-connection-editor, with some changes to the .ui files to make them fit better in the new design.
2012-12-09 19:38:32 -05:00
<child>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<object class="GtkViewport">
network: Break out wifi details code and add editing support This code is fairly independent of the rest, and we don't want net-device-wifi.c to become too massive and unmaintainable. The code in connection-editor/ is fairly similar to nm-connection-editor, with some simplification because we currently only edit wireless connections. The code in wireless-security/ is almost a straight copy of the same code in nm-connection-editor, with some changes to the .ui files to make them fit better in the new design.
2012-12-09 19:38:32 -05:00
<child>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<object class="GtkGrid" id="main_box">
<property name="margin_start">24</property>
<property name="margin_end">24</property>
<property name="margin_top">24</property>
<property name="margin_bottom">24</property>
network: Break out wifi details code and add editing support This code is fairly independent of the rest, and we don't want net-device-wifi.c to become too massive and unmaintainable. The code in connection-editor/ is fairly similar to nm-connection-editor, with some simplification because we currently only edit wireless connections. The code in wireless-security/ is almost a straight copy of the same code in nm-connection-editor, with some changes to the .ui files to make them fit better in the new design.
2012-12-09 19:38:32 -05:00
<property name="orientation">vertical</property>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<property name="row-spacing">6</property>
<property name="column-spacing">6</property>
<child>
<object class="GtkLabel">
<property name="label" translatable="yes">IPv_4 Method</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">disabled_radio</property>
<property name="xalign">0.0</property>
<layout>
<property name="row">0</property>
<property name="column">0</property>
</layout>
<attributes>
<attribute name="weight" value="bold"/>
</attributes>
</object>
</child>
<child>
<object class="GtkCheckButton" id="automatic_radio">
<property name="label" translatable="yes">Automatic (DHCP)</property>
network: keep track of radio buttons in connection editor with action Hooking to all the toggled signals from all the buttons for executing the same action is inneficient, and can potenticall end up in a segmentation fault due to some race in the signal emmission, where the active button gets deactivated before the clicked button is activated Looking at the GTK4 code, in a radio group: - The button which was previously active gets de-activated, emitting its corresponding toggled signal. - The active property for the clicked button gets set. - The clicked button emits its toggled signal. Therefore, if the first toggle signal gets processed before the active property is set, there can be a race condition. We are seeing this downstream at pmOS: https://gitlab.com/postmarketOS/pmaports/-/issues/1816 Instead of this racy behavior, follow upstream recommendation and keep track of the state through a stateful signal.
2022-12-12 17:44:51 +01:00
<property name="action-name">ip4page.ip4method</property>
<property name="action-target">'automatic'</property>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<layout>
<property name="row">0</property>
<property name="column">1</property>
</layout>
</object>
</child>
<child>
<object class="GtkCheckButton" id="local_radio">
<property name="label" translatable="yes">Link-Local Only</property>
network: keep track of radio buttons in connection editor with action Hooking to all the toggled signals from all the buttons for executing the same action is inneficient, and can potenticall end up in a segmentation fault due to some race in the signal emmission, where the active button gets deactivated before the clicked button is activated Looking at the GTK4 code, in a radio group: - The button which was previously active gets de-activated, emitting its corresponding toggled signal. - The active property for the clicked button gets set. - The clicked button emits its toggled signal. Therefore, if the first toggle signal gets processed before the active property is set, there can be a race condition. We are seeing this downstream at pmOS: https://gitlab.com/postmarketOS/pmaports/-/issues/1816 Instead of this racy behavior, follow upstream recommendation and keep track of the state through a stateful signal.
2022-12-12 17:44:51 +01:00
<property name="action-name">ip4page.ip4method</property>
<property name="action-target">'local'</property>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<layout>
<property name="row">0</property>
<property name="column">2</property>
</layout>
</object>
</child>
<child>
<object class="GtkCheckButton" id="manual_radio">
<property name="label" translatable="yes">Manual</property>
network: keep track of radio buttons in connection editor with action Hooking to all the toggled signals from all the buttons for executing the same action is inneficient, and can potenticall end up in a segmentation fault due to some race in the signal emmission, where the active button gets deactivated before the clicked button is activated Looking at the GTK4 code, in a radio group: - The button which was previously active gets de-activated, emitting its corresponding toggled signal. - The active property for the clicked button gets set. - The clicked button emits its toggled signal. Therefore, if the first toggle signal gets processed before the active property is set, there can be a race condition. We are seeing this downstream at pmOS: https://gitlab.com/postmarketOS/pmaports/-/issues/1816 Instead of this racy behavior, follow upstream recommendation and keep track of the state through a stateful signal.
2022-12-12 17:44:51 +01:00
<property name="action-name">ip4page.ip4method</property>
<property name="action-target">'manual'</property>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<layout>
<property name="row">1</property>
<property name="column">1</property>
</layout>
</object>
</child>
<child>
<object class="GtkCheckButton" id="disabled_radio">
<property name="label" translatable="yes">Disable</property>
network: keep track of radio buttons in connection editor with action Hooking to all the toggled signals from all the buttons for executing the same action is inneficient, and can potenticall end up in a segmentation fault due to some race in the signal emmission, where the active button gets deactivated before the clicked button is activated Looking at the GTK4 code, in a radio group: - The button which was previously active gets de-activated, emitting its corresponding toggled signal. - The active property for the clicked button gets set. - The clicked button emits its toggled signal. Therefore, if the first toggle signal gets processed before the active property is set, there can be a race condition. We are seeing this downstream at pmOS: https://gitlab.com/postmarketOS/pmaports/-/issues/1816 Instead of this racy behavior, follow upstream recommendation and keep track of the state through a stateful signal.
2022-12-12 17:44:51 +01:00
<property name="action-name">ip4page.ip4method</property>
<property name="action-target">'disabled'</property>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<layout>
<property name="row">1</property>
<property name="column">2</property>
</layout>
</object>
</child>
<child>
<object class="GtkCheckButton" id="shared_radio">
<property name="label" translatable="yes">Shared to other computers</property>
network: keep track of radio buttons in connection editor with action Hooking to all the toggled signals from all the buttons for executing the same action is inneficient, and can potenticall end up in a segmentation fault due to some race in the signal emmission, where the active button gets deactivated before the clicked button is activated Looking at the GTK4 code, in a radio group: - The button which was previously active gets de-activated, emitting its corresponding toggled signal. - The active property for the clicked button gets set. - The clicked button emits its toggled signal. Therefore, if the first toggle signal gets processed before the active property is set, there can be a race condition. We are seeing this downstream at pmOS: https://gitlab.com/postmarketOS/pmaports/-/issues/1816 Instead of this racy behavior, follow upstream recommendation and keep track of the state through a stateful signal.
2022-12-12 17:44:51 +01:00
<property name="action-name">ip4page.ip4method</property>
<property name="action-target">'shared'</property>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<layout>
<property name="row">2</property>
<property name="column">1</property>
</layout>
</object>
</child>
network: Break out wifi details code and add editing support This code is fairly independent of the rest, and we don't want net-device-wifi.c to become too massive and unmaintainable. The code in connection-editor/ is fairly similar to nm-connection-editor, with some simplification because we currently only edit wireless connections. The code in wireless-security/ is almost a straight copy of the same code in nm-connection-editor, with some changes to the .ui files to make them fit better in the new design.
2012-12-09 19:38:32 -05:00
<child>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<object class="GtkBox" id="content_box">
network: Break out wifi details code and add editing support This code is fairly independent of the rest, and we don't want net-device-wifi.c to become too massive and unmaintainable. The code in connection-editor/ is fairly similar to nm-connection-editor, with some simplification because we currently only edit wireless connections. The code in wireless-security/ is almost a straight copy of the same code in nm-connection-editor, with some changes to the .ui files to make them fit better in the new design.
2012-12-09 19:38:32 -05:00
<property name="orientation">vertical</property>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<property name="spacing">6</property>
<layout>
<property name="row">3</property>
<property name="column">0</property>
<property name="column-span">3</property>
</layout>
network: Break out wifi details code and add editing support This code is fairly independent of the rest, and we don't want net-device-wifi.c to become too massive and unmaintainable. The code in connection-editor/ is fairly similar to nm-connection-editor, with some simplification because we currently only edit wireless connections. The code in wireless-security/ is almost a straight copy of the same code in nm-connection-editor, with some changes to the .ui files to make them fit better in the new design.
2012-12-09 19:38:32 -05:00
<child>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<object class="GtkBox" id="address_box">
<property name="orientation">vertical</property>
network: Use a table-like widget in address editor According to the latest mockups for the connection editor dialog [1], the IPv4 and IPv6 pages are supposed to use a table-like editor to manage the addresses, in a similar fashion of what was done to the routes editor. This way of editing is not only easier to comprehend, but also improves the size of the dialog, requiring much less vertical space to present the routes. The current implementation, however, uses a vertical layout and a toolbar, which is inefficient in its usage of space. Fix that by implementing the table-like editor widget, both in IPv4 and IPv6 pages. [1] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/system-settings/network/aday2/network-wires.png https://bugzilla.gnome.org/show_bug.cgi?id=779841
2017-05-23 15:02:45 -03:00
<child>
<object class="GtkLabel">
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<property name="xalign">0</property>
<property name="label" translatable="yes">Addresses</property>
<property name="margin_top">24</property>
<property name="margin_bottom">8</property>
network: Use a table-like widget in address editor According to the latest mockups for the connection editor dialog [1], the IPv4 and IPv6 pages are supposed to use a table-like editor to manage the addresses, in a similar fashion of what was done to the routes editor. This way of editing is not only easier to comprehend, but also improves the size of the dialog, requiring much less vertical space to present the routes. The current implementation, however, uses a vertical layout and a toolbar, which is inefficient in its usage of space. Fix that by implementing the table-like editor widget, both in IPv4 and IPv6 pages. [1] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/system-settings/network/aday2/network-wires.png https://bugzilla.gnome.org/show_bug.cgi?id=779841
2017-05-23 15:02:45 -03:00
<attributes>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<attribute name="weight" value="bold"/>
network: Use a table-like widget in address editor According to the latest mockups for the connection editor dialog [1], the IPv4 and IPv6 pages are supposed to use a table-like editor to manage the addresses, in a similar fashion of what was done to the routes editor. This way of editing is not only easier to comprehend, but also improves the size of the dialog, requiring much less vertical space to present the routes. The current implementation, however, uses a vertical layout and a toolbar, which is inefficient in its usage of space. Fix that by implementing the table-like editor widget, both in IPv4 and IPv6 pages. [1] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/system-settings/network/aday2/network-wires.png https://bugzilla.gnome.org/show_bug.cgi?id=779841
2017-05-23 15:02:45 -03:00
</attributes>
</object>
</child>
<child>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<object class="GtkBox">
<property name="orientation">horizontal</property>
<child>
network/ce: Fix address label ids on ip4-page In https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/861d762ce5c1538fda2167eacf6b8e3fe1a98dbd, the address labels on the IPv4 page were renamed, however the corresponding change was not made in the respective .ui file, which results in a crash upon construction of the page. This change fixes that.
2022-06-12 21:41:45 +02:00
<object class="GtkLabel" id="address_address_label">
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<property name="hexpand">True</property>
<property name="label" translatable="yes">Address</property>
<style>
<class name="dim-label" />
</style>
<attributes>
<attribute name="scale" value="0.8"/>
</attributes>
</object>
</child>
<child>
network/ce: Fix address label ids on ip4-page In https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/861d762ce5c1538fda2167eacf6b8e3fe1a98dbd, the address labels on the IPv4 page were renamed, however the corresponding change was not made in the respective .ui file, which results in a crash upon construction of the page. This change fixes that.
2022-06-12 21:41:45 +02:00
<object class="GtkLabel" id="address_netmask_label">
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<property name="hexpand">True</property>
<property name="label" translatable="yes">Netmask</property>
<style>
<class name="dim-label" />
</style>
<attributes>
<attribute name="scale" value="0.8"/>
</attributes>
</object>
</child>
<child>
network/ce: Fix address label ids on ip4-page In https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/861d762ce5c1538fda2167eacf6b8e3fe1a98dbd, the address labels on the IPv4 page were renamed, however the corresponding change was not made in the respective .ui file, which results in a crash upon construction of the page. This change fixes that.
2022-06-12 21:41:45 +02:00
<object class="GtkLabel" id="address_gateway_label">
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<property name="hexpand">True</property>
<property name="label" translatable="yes">Gateway</property>
<style>
<class name="dim-label" />
</style>
<attributes>
<attribute name="scale" value="0.8"/>
</attributes>
</object>
</child>
<!-- This invisible box is used to add some width in the
end of the header row, assuming the space used by the
delete button in the rows -->
<child>
<object class="GtkBox" id="address_stub_box">
</object>
</child>
</object>
</child>
</object>
</child>
<child>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<object class="GtkBox" id="dns_box">
<property name="orientation">vertical</property>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<property name="spacing">6</property>
<child>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<object class="GtkBox">
<property name="margin_top">24</property>
<property name="spacing">6</property>
<child>
<object class="GtkLabel" id="dns4_label">
<property name="hexpand">True</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">DNS</property>
<attributes>
<attribute name="weight" value="bold"/>
</attributes>
</object>
</child>
<child>
<object class="GtkLabel" id="auto_dns_label">
<property name="hexpand">True</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Automatic</property>
</object>
</child>
<child>
<object class="GtkSwitch" id="auto_dns_switch">
<property name="halign">end</property>
<property name="valign">center</property>
<accessibility>
<property name="label" translatable="yes">Automatic DNS</property>
</accessibility>
</object>
</child>
network: Use a table-like widget in address editor According to the latest mockups for the connection editor dialog [1], the IPv4 and IPv6 pages are supposed to use a table-like editor to manage the addresses, in a similar fashion of what was done to the routes editor. This way of editing is not only easier to comprehend, but also improves the size of the dialog, requiring much less vertical space to present the routes. The current implementation, however, uses a vertical layout and a toolbar, which is inefficient in its usage of space. Fix that by implementing the table-like editor widget, both in IPv4 and IPv6 pages. [1] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/system-settings/network/aday2/network-wires.png https://bugzilla.gnome.org/show_bug.cgi?id=779841
2017-05-23 15:02:45 -03:00
</object>
</child>
<child>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<object class="GtkEntry" id="dns_entry">
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<accessibility>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<property name="label" translatable="yes">DNS server address(es)</property>
<relation name="described-by">dns_multiple_help</relation>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
</accessibility>
network: Use a table-like widget in address editor According to the latest mockups for the connection editor dialog [1], the IPv4 and IPv6 pages are supposed to use a table-like editor to manage the addresses, in a similar fashion of what was done to the routes editor. This way of editing is not only easier to comprehend, but also improves the size of the dialog, requiring much less vertical space to present the routes. The current implementation, however, uses a vertical layout and a toolbar, which is inefficient in its usage of space. Fix that by implementing the table-like editor widget, both in IPv4 and IPv6 pages. [1] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/system-settings/network/aday2/network-wires.png https://bugzilla.gnome.org/show_bug.cgi?id=779841
2017-05-23 15:02:45 -03:00
</object>
</child>
network: Use a table-like widget to edit routes According to the latest mockups for the connection editor dialog [1], the IPv4 and IPv6 pages are supposed to use a table-like editor to manage the routes. This editor is not only easier to comprehend, but also improves the size of the dialog, requiring much less vertical space to present the routes. The current implementation, however, uses a vertical layout and a toolbar, which is inefficient in its usage of space. Fix that by implementing the table-like editor widget, both in IPv4 and IPv6 pages. [1] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/system-settings/network/aday2/network-wires.png https://bugzilla.gnome.org/show_bug.cgi?id=779841
2017-05-23 13:04:52 -03:00
<child>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<object class="GtkLabel" id="dns_multiple_help">
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<property name="xalign">0</property>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<property name="label" translatable="yes">Separate IP addresses with commas</property>
<style>
<class name="dim-label" />
</style>
network: Use a table-like widget to edit routes According to the latest mockups for the connection editor dialog [1], the IPv4 and IPv6 pages are supposed to use a table-like editor to manage the routes. This editor is not only easier to comprehend, but also improves the size of the dialog, requiring much less vertical space to present the routes. The current implementation, however, uses a vertical layout and a toolbar, which is inefficient in its usage of space. Fix that by implementing the table-like editor widget, both in IPv4 and IPv6 pages. [1] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/system-settings/network/aday2/network-wires.png https://bugzilla.gnome.org/show_bug.cgi?id=779841
2017-05-23 13:04:52 -03:00
<attributes>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<attribute name="scale" value="0.8"/>
network: Use a table-like widget to edit routes According to the latest mockups for the connection editor dialog [1], the IPv4 and IPv6 pages are supposed to use a table-like editor to manage the routes. This editor is not only easier to comprehend, but also improves the size of the dialog, requiring much less vertical space to present the routes. The current implementation, however, uses a vertical layout and a toolbar, which is inefficient in its usage of space. Fix that by implementing the table-like editor widget, both in IPv4 and IPv6 pages. [1] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/system-settings/network/aday2/network-wires.png https://bugzilla.gnome.org/show_bug.cgi?id=779841
2017-05-23 13:04:52 -03:00
</attributes>
</object>
</child>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
</object>
</child>
<child>
<object class="GtkBox" id="routes_box">
<property name="orientation">vertical</property>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<property name="spacing">6</property>
network: Use a table-like widget to edit routes According to the latest mockups for the connection editor dialog [1], the IPv4 and IPv6 pages are supposed to use a table-like editor to manage the routes. This editor is not only easier to comprehend, but also improves the size of the dialog, requiring much less vertical space to present the routes. The current implementation, however, uses a vertical layout and a toolbar, which is inefficient in its usage of space. Fix that by implementing the table-like editor widget, both in IPv4 and IPv6 pages. [1] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/system-settings/network/aday2/network-wires.png https://bugzilla.gnome.org/show_bug.cgi?id=779841
2017-05-23 13:04:52 -03:00
<child>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<object class="GtkBox">
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<property name="margin_top">24</property>
<property name="spacing">6</property>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<child>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<object class="GtkLabel">
<property name="xalign">0</property>
<property name="hexpand">True</property>
<property name="label" translatable="yes">Routes</property>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<attributes>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<attribute name="weight" value="bold"/>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
</attributes>
</object>
</child>
<child>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<object class="GtkLabel" id="auto_routes_label">
<property name="hexpand">True</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Automatic</property>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
</object>
</child>
<child>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<object class="GtkSwitch" id="auto_routes_switch">
<property name="halign">end</property>
<property name="valign">center</property>
<accessibility>
<property name="label" translatable="yes">Automatic Routes</property>
</accessibility>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
</object>
</child>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
</object>
</child>
<child>
<object class="GtkBox" id="route_config_box">
<property name="orientation">vertical</property>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
<child>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<object class="GtkBox">
<property name="orientation">horizontal</property>
<child>
<object class="GtkLabel" id="routes_address_label">
<property name="label" translatable="yes">Address</property>
<style>
<class name="dim-label" />
</style>
<attributes>
<attribute name="scale" value="0.8"/>
</attributes>
</object>
</child>
<child>
<object class="GtkLabel" id="routes_netmask_label">
<property name="label" translatable="yes">Netmask</property>
<style>
<class name="dim-label" />
</style>
<attributes>
<attribute name="scale" value="0.8"/>
</attributes>
</object>
</child>
<child>
<object class="GtkLabel" id="routes_gateway_label">
<property name="label" translatable="yes">Gateway</property>
<style>
<class name="dim-label" />
</style>
<attributes>
<attribute name="scale" value="0.8"/>
</attributes>
</object>
</child>
<child>
<object class="GtkLabel" id="routes_metric_label">
<property name="label" translatable="yes" comments="Translators: Please see https://en.wikipedia.org/wiki/Metrics_(networking)">Metric</property>
<style>
<class name="dim-label" />
</style>
<attributes>
<attribute name="scale" value="0.8"/>
</attributes>
</object>
</child>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<!-- This invisible box is used to add some width in the
end of the header row, assuming the space used by the
delete button in the rows -->
<child>
<object class="GtkBox" id="routes_stub_box">
</object>
</child>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
</object>
</child>
network: Use a table-like widget to edit routes According to the latest mockups for the connection editor dialog [1], the IPv4 and IPv6 pages are supposed to use a table-like editor to manage the routes. This editor is not only easier to comprehend, but also improves the size of the dialog, requiring much less vertical space to present the routes. The current implementation, however, uses a vertical layout and a toolbar, which is inefficient in its usage of space. Fix that by implementing the table-like editor widget, both in IPv4 and IPv6 pages. [1] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/system-settings/network/aday2/network-wires.png https://bugzilla.gnome.org/show_bug.cgi?id=779841
2017-05-23 13:04:52 -03:00
</object>
</child>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
<child>
<object class="GtkCheckButton" id="never_default_check">
<property name="label" translatable="yes">Use this connection _only for resources on its network</property>
<property name="use_underline">True</property>
</object>
</child>
network: Port to GTK4 Boy this was hard. To ease the pain of porting wireless-security to GTK4, add a new WsFileChooserButton class that mimics the behavior of a button that triggers a filechooser, as per the migration guide suggests. There were lots of GtkGrids, so the diff is particularly horrendous. Sorry. This needs serious testing before landing.
2021-11-29 10:37:01 -03:00
</object>
</child>
network: Break out wifi details code and add editing support This code is fairly independent of the rest, and we don't want net-device-wifi.c to become too massive and unmaintainable. The code in connection-editor/ is fairly similar to nm-connection-editor, with some simplification because we currently only edit wireless connections. The code in wireless-security/ is almost a straight copy of the same code in nm-connection-editor, with some changes to the .ui files to make them fit better in the new design.
2012-12-09 19:38:32 -05:00
</object>
</child>
</object>
</child>
</object>
</child>
</object>
</child>
network: Convert CEPage widgets to GtkTemplate
2019-11-06 17:16:54 +13:00
</template>
network-connection-editor: Align Routes labels Even though the routes_metric_label is in a GtkSizeGroup with the GtkEntry for the metric, its size was set too big after adding the entry to the size group. To fix this, add all the other labels and corresponding entries to size groups as well. The hexpand can then be removed as well on the labels. Fixes #1235
2023-10-18 22:20:46 +02:00
<object class="GtkSizeGroup" id="routes_address_sizegroup">
<property name="mode">horizontal</property>
<widgets>
<widget name="routes_address_label" />
</widgets>
</object>
<object class="GtkSizeGroup" id="routes_netmask_sizegroup">
<property name="mode">horizontal</property>
<widgets>
<widget name="routes_netmask_label"/>
</widgets>
</object>
<object class="GtkSizeGroup" id="routes_gateway_sizegroup">
<property name="mode">horizontal</property>
<widgets>
<widget name="routes_gateway_label" />
</widgets>
</object>
network: Use a table-like widget to edit routes According to the latest mockups for the connection editor dialog [1], the IPv4 and IPv6 pages are supposed to use a table-like editor to manage the routes. This editor is not only easier to comprehend, but also improves the size of the dialog, requiring much less vertical space to present the routes. The current implementation, however, uses a vertical layout and a toolbar, which is inefficient in its usage of space. Fix that by implementing the table-like editor widget, both in IPv4 and IPv6 pages. [1] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/system-settings/network/aday2/network-wires.png https://bugzilla.gnome.org/show_bug.cgi?id=779841
2017-05-23 13:04:52 -03:00
<object class="GtkSizeGroup" id="routes_metric_sizegroup">
<property name="mode">horizontal</property>
<widgets>
<widget name="routes_metric_label" />
</widgets>
</object>
<object class="GtkSizeGroup" id="routes_sizegroup">
<property name="mode">horizontal</property>
<widgets>
<widget name="routes_stub_box" />
</widgets>
</object>
network: Use a table-like widget in address editor According to the latest mockups for the connection editor dialog [1], the IPv4 and IPv6 pages are supposed to use a table-like editor to manage the addresses, in a similar fashion of what was done to the routes editor. This way of editing is not only easier to comprehend, but also improves the size of the dialog, requiring much less vertical space to present the routes. The current implementation, however, uses a vertical layout and a toolbar, which is inefficient in its usage of space. Fix that by implementing the table-like editor widget, both in IPv4 and IPv6 pages. [1] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/system-settings/network/aday2/network-wires.png https://bugzilla.gnome.org/show_bug.cgi?id=779841
2017-05-23 15:02:45 -03:00
<object class="GtkSizeGroup" id="address_sizegroup">
<property name="mode">horizontal</property>
<widgets>
<widget name="address_stub_box" />
</widgets>
</object>
network: Break out wifi details code and add editing support This code is fairly independent of the rest, and we don't want net-device-wifi.c to become too massive and unmaintainable. The code in connection-editor/ is fairly similar to nm-connection-editor, with some simplification because we currently only edit wireless connections. The code in wireless-security/ is almost a straight copy of the same code in nm-connection-editor, with some changes to the .ui files to make them fit better in the new design.
2012-12-09 19:38:32 -05:00
</interface>
network: fix sensitivity of DNS and route configuration widgets When the IP method is "disabled" or "shared" then everything else is supposed to be insensitive. This currently fails if you toggle between the two, because it's implemented using property bindings that are just not smart enough to handle this task. Handle sensitivity only in method_changed() to avoid this. Additionally, not all of the widgets are being consistently disabled/enabled when appropriate. E.g. when the method is "local" then only the DNS entry, route entries, and default route checkboxes become insensitive, leaving the other widgets, including notably the Automatic switches, sensitive. They should all become insensitive, as when the method is "disabled" or "shared." Fix this by organizing all the related widgets into boxes and setting the sensitivity of the entire box. (Note the strategy followed here does not exactly match nm-connection-editor, which always allows editing addresses. We only allow that in Manual mode. I'm not sure if this is advisable or not, so won't touch that.) Finally, the Automatic DNS and Automatic Routes toggles should only be sensitive when the method is "Automatic".
2023-10-13 14:03:43 -05:00
Reference in a new issue Copy permalink