depau/Purism-Calls
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/calls.git synced 2024-11-17 16:05:36 +00:00
Code Issues Releases Wiki Activity
Purism-Calls/src/ui/new-call-box.ui

139 lines
5.3 KiB
Text
Raw Normal View History

Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated with glade 3.22.0 -->
<interface>
<requires lib="gtk+" version="3.22"/>
Port to libhandy 1 This ports Calls to libhandy 1 and drops the embedded HdyAvatar in favor of the libhandy one. Fixes https://source.puri.sm/Librem5/calls/-/issues/172
2020-09-29 10:22:47 +00:00
<requires lib="libhandy" version="1.0"/>
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
<template class="CallsNewCallBox" parent="GtkBox">
<property name="can_focus">False</property>
<property name="halign">center</property>
<property name="margin_bottom">16</property>
<property name="margin_left">24</property>
<property name="margin_right">24</property>
<property name="margin_top">16</property>
<property name="orientation">vertical</property>
<property name="valign">center</property>
<property name="visible">True</property>
provider: Use GListModel to track origins And adapt to changes It's easier to track changes if we are using GListModel than a GList. Also, eventually we shall have multiple providers, and we can use GtkFlattenListModel to merge multiple origins without manually managing pointers ourself. Since several widgets has APIs to handle GListModels, it will also help us create widgets from GListModels easily.
2021-02-15 05:34:34 +00:00
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
<child>
provider: Use GListModel to track origins And adapt to changes It's easier to track changes if we are using GListModel than a GList. Also, eventually we shall have multiple providers, and we can use GtkFlattenListModel to merge multiple origins without manually managing pointers ourself. Since several widgets has APIs to handle GListModels, it will also help us create widgets from GListModels easily.
2021-02-15 05:34:34 +00:00
<object class="GtkListBox" id="origin_list_box">
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
<property name="visible">True</property>
provider: Use GListModel to track origins And adapt to changes It's easier to track changes if we are using GListModel than a GList. Also, eventually we shall have multiple providers, and we can use GtkFlattenListModel to merge multiple origins without manually managing pointers ourself. Since several widgets has APIs to handle GListModels, it will also help us create widgets from GListModels easily.
2021-02-15 05:34:34 +00:00
<property name="selection-mode">none</property>
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
<child>
provider: Use GListModel to track origins And adapt to changes It's easier to track changes if we are using GListModel than a GList. Also, eventually we shall have multiple providers, and we can use GtkFlattenListModel to merge multiple origins without manually managing pointers ourself. Since several widgets has APIs to handle GListModels, it will also help us create widgets from GListModels easily.
2021-02-15 05:34:34 +00:00
<object class="HdyComboRow" id="origin_list">
<property name="visible">True</property>
</object>
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
</child>
</object>
</child>
provider: Use GListModel to track origins And adapt to changes It's easier to track changes if we are using GListModel than a GList. Also, eventually we shall have multiple providers, and we can use GtkFlattenListModel to merge multiple origins without manually managing pointers ourself. Since several widgets has APIs to handle GListModels, it will also help us create widgets from GListModels easily.
2021-02-15 05:34:34 +00:00
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
<child>
calls-new-call-box: Allow entering of "+" symbol Use the "number" property of the dial pad for the dialed number which takes care of cycling buttons. While we're at it, also make the clear button external to the number entry box, enlarging it and turning it into a backspace button. Closes #12
2019-08-22 15:01:10 +00:00
<object class="GtkBox">
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
<property name="visible">True</property>
calls-new-call-box: Allow entering of "+" symbol Use the "number" property of the dial pad for the dialed number which takes care of cycling buttons. While we're at it, also make the clear button external to the number entry box, enlarging it and turning it into a backspace button. Closes #12
2019-08-22 15:01:10 +00:00
<property name="can_focus">False</property>
<property name="orientation">horizontal</property>
<child>
Replace HdyDialer with HdyKeypad and bump libhandy to 0.0.12 HdyDialer was deprecated and therefore is replaced with HdyKeypad. HdyDialer used a `gchr *` to store the entered phone number. On every button press the entire text of the display entry was replaced with the new string, which messed up selection and cursor position. HdyKeypad connects directly to a GtkEntry and inserts each button press the same way as a keyboard stroke would do. In the case of the `call display` entry every new digit is appended to the end of the input and therefore it also moves the cursor to the end of the entry. Instead of making the Entry not editable, only the events which would remove text form the entry are blocked, via the `delete-text` signal. And the signal `insert-text` is used to block unwanted chars from beeing inserted. Same as for the `call display` entry also the `new call box` entry is made editable and the signal `insert-text` is used to block unwanted chars. All other user action possible on a entry arn't blocked e.g. repositioning the cursor. The advantage of making the Entry editable is that we can show the cursor position. It also allows the user to select the position where new digits are inserted in the `new call box`. On a button press the focus is set to the Entry to give the correct feedback to the user. This centers the text on the entry, as required by the design. This also makes the delete button remove only one char at the time, to move closer to the desired UX. Related: https://source.puri.sm/Librem5/calls/issues/58 Fixes: https://source.puri.sm/Librem5/calls/issues/82
2019-09-17 12:09:33 +00:00
<object class="GtkEntry" id="keypad_entry">
calls-new-call-box: Allow entering of "+" symbol Use the "number" property of the dial pad for the dialed number which takes care of cycling buttons. While we're at it, also make the clear button external to the number entry box, enlarging it and turning it into a backspace button. Closes #12
2019-08-22 15:01:10 +00:00
<property name="visible">True</property>
Replace HdyDialer with HdyKeypad and bump libhandy to 0.0.12 HdyDialer was deprecated and therefore is replaced with HdyKeypad. HdyDialer used a `gchr *` to store the entered phone number. On every button press the entire text of the display entry was replaced with the new string, which messed up selection and cursor position. HdyKeypad connects directly to a GtkEntry and inserts each button press the same way as a keyboard stroke would do. In the case of the `call display` entry every new digit is appended to the end of the input and therefore it also moves the cursor to the end of the entry. Instead of making the Entry not editable, only the events which would remove text form the entry are blocked, via the `delete-text` signal. And the signal `insert-text` is used to block unwanted chars from beeing inserted. Same as for the `call display` entry also the `new call box` entry is made editable and the signal `insert-text` is used to block unwanted chars. All other user action possible on a entry arn't blocked e.g. repositioning the cursor. The advantage of making the Entry editable is that we can show the cursor position. It also allows the user to select the position where new digits are inserted in the `new call box`. On a button press the focus is set to the Entry to give the correct feedback to the user. This centers the text on the entry, as required by the design. This also makes the delete button remove only one char at the time, to move closer to the desired UX. Related: https://source.puri.sm/Librem5/calls/issues/58 Fixes: https://source.puri.sm/Librem5/calls/issues/82
2019-09-17 12:09:33 +00:00
<property name="can_focus">True</property>
<property name="hexpand">True</property>
<property name="xalign">0.5</property>
<property name="margin_right">6</property>
NewCallBox+CallDisplay: UI facelift This adds a style.css file to allow the use of custom css Fixes https://source.puri.sm/Librem5/calls/issues/115: - Making the phone number larger - Moving the delete button to the bottom - Rounding all buttons, and making the grid buttons circular - Making the call button a bit less wide
2020-01-28 15:35:02 +00:00
<style>
<class name="phone-number-entry"/>
</style>
calls-new-call-box: Allow entering of "+" symbol Use the "number" property of the dial pad for the dialed number which takes care of cycling buttons. While we're at it, also make the clear button external to the number entry box, enlarging it and turning it into a backspace button. Closes #12
2019-08-22 15:01:10 +00:00
</object>
</child>
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
</packing>
</child>
<child>
Replace HdyDialer with HdyKeypad and bump libhandy to 0.0.12 HdyDialer was deprecated and therefore is replaced with HdyKeypad. HdyDialer used a `gchr *` to store the entered phone number. On every button press the entire text of the display entry was replaced with the new string, which messed up selection and cursor position. HdyKeypad connects directly to a GtkEntry and inserts each button press the same way as a keyboard stroke would do. In the case of the `call display` entry every new digit is appended to the end of the input and therefore it also moves the cursor to the end of the entry. Instead of making the Entry not editable, only the events which would remove text form the entry are blocked, via the `delete-text` signal. And the signal `insert-text` is used to block unwanted chars from beeing inserted. Same as for the `call display` entry also the `new call box` entry is made editable and the signal `insert-text` is used to block unwanted chars. All other user action possible on a entry arn't blocked e.g. repositioning the cursor. The advantage of making the Entry editable is that we can show the cursor position. It also allows the user to select the position where new digits are inserted in the `new call box`. On a button press the focus is set to the Entry to give the correct feedback to the user. This centers the text on the entry, as required by the design. This also makes the delete button remove only one char at the time, to move closer to the desired UX. Related: https://source.puri.sm/Librem5/calls/issues/58 Fixes: https://source.puri.sm/Librem5/calls/issues/82
2019-09-17 12:09:33 +00:00
<object class="HdyKeypad" id="keypad">
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
<property name="visible">True</property>
Replace HdyDialer with HdyKeypad and bump libhandy to 0.0.12 HdyDialer was deprecated and therefore is replaced with HdyKeypad. HdyDialer used a `gchr *` to store the entered phone number. On every button press the entire text of the display entry was replaced with the new string, which messed up selection and cursor position. HdyKeypad connects directly to a GtkEntry and inserts each button press the same way as a keyboard stroke would do. In the case of the `call display` entry every new digit is appended to the end of the input and therefore it also moves the cursor to the end of the entry. Instead of making the Entry not editable, only the events which would remove text form the entry are blocked, via the `delete-text` signal. And the signal `insert-text` is used to block unwanted chars from beeing inserted. Same as for the `call display` entry also the `new call box` entry is made editable and the signal `insert-text` is used to block unwanted chars. All other user action possible on a entry arn't blocked e.g. repositioning the cursor. The advantage of making the Entry editable is that we can show the cursor position. It also allows the user to select the position where new digits are inserted in the `new call box`. On a button press the focus is set to the Entry to give the correct feedback to the user. This centers the text on the entry, as required by the design. This also makes the delete button remove only one char at the time, to move closer to the desired UX. Related: https://source.puri.sm/Librem5/calls/issues/58 Fixes: https://source.puri.sm/Librem5/calls/issues/82
2019-09-17 12:09:33 +00:00
<property name="column_spacing">16</property>
<property name="row_spacing">10</property>
<property name="halign">center</property>
<property name="margin_top">18</property>
<property name="margin_bottom">18</property>
<property name="entry">keypad_entry</property>
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
</packing>
</child>
<child>
NewCallBox+CallDisplay: UI facelift This adds a style.css file to allow the use of custom css Fixes https://source.puri.sm/Librem5/calls/issues/115: - Making the phone number larger - Moving the delete button to the bottom - Rounding all buttons, and making the grid buttons circular - Making the call button a bit less wide
2020-01-28 15:35:02 +00:00
<object class="GtkBox">
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
<property name="visible">True</property>
NewCallBox+CallDisplay: UI facelift This adds a style.css file to allow the use of custom css Fixes https://source.puri.sm/Librem5/calls/issues/115: - Making the phone number larger - Moving the delete button to the bottom - Rounding all buttons, and making the grid buttons circular - Making the call button a bit less wide
2020-01-28 15:35:02 +00:00
<property name="can_focus">False</property>
<property name="orientation">horizontal</property>
<child type="center">
<object class="GtkButton" id="dial">
<property name="always_show_image">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<property name="visible">True</property>
<signal name="clicked" handler="dial_clicked_cb" swapped="yes"/>
<style>
<class name="suggested-action"/>
<class name="image-button"/>
<class name="dial-button"/>
</style>
<child internal-child="accessible">
<object class="AtkObject" id="a11y-dial">
<property name="accessible-name" translatable="yes">Dial</property>
</object>
</child>
<child>
<object class="GtkImage" id="back_image">
<property name="visible">True</property>
<property name="icon-name">call-start-symbolic</property>
<property name="icon-size">5</property>
</object>
</child>
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
</object>
NewCallBox+CallDisplay: UI facelift This adds a style.css file to allow the use of custom css Fixes https://source.puri.sm/Librem5/calls/issues/115: - Making the phone number larger - Moving the delete button to the bottom - Rounding all buttons, and making the grid buttons circular - Making the call button a bit less wide
2020-01-28 15:35:02 +00:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
</packing>
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
</child>
<child>
NewCallBox+CallDisplay: UI facelift This adds a style.css file to allow the use of custom css Fixes https://source.puri.sm/Librem5/calls/issues/115: - Making the phone number larger - Moving the delete button to the bottom - Rounding all buttons, and making the grid buttons circular - Making the call button a bit less wide
2020-01-28 15:35:02 +00:00
<object class="GtkButton" id="backspace">
<property name="always_show_image">True</property>
<property name="can_focus">True</property>
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
<property name="visible">True</property>
NewCallBox+CallDisplay: UI facelift This adds a style.css file to allow the use of custom css Fixes https://source.puri.sm/Librem5/calls/issues/115: - Making the phone number larger - Moving the delete button to the bottom - Rounding all buttons, and making the grid buttons circular - Making the call button a bit less wide
2020-01-28 15:35:02 +00:00
<property name="focus-on-click">False</property>
<property name="margin_right">15</property>
<property name="valign">center</property>
<property name="halign">center</property>
<signal name="clicked" handler="backspace_clicked_cb" swapped="yes"/>
<child internal-child="accessible">
<object class="AtkObject" id="a11y-backspace">
<property name="accessible-name" translatable="yes">Backspace through number</property>
</object>
</child>
<style>
<class name="delete-button"/>
</style>
<child>
<object class="GtkImage">
<property name="visible">True</property>
<property name="icon-name">edit-clear-symbolic</property>
</object>
</child>
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
</object>
NewCallBox+CallDisplay: UI facelift This adds a style.css file to allow the use of custom css Fixes https://source.puri.sm/Librem5/calls/issues/115: - Making the phone number larger - Moving the delete button to the bottom - Rounding all buttons, and making the grid buttons circular - Making the call button a bit less wide
2020-01-28 15:35:02 +00:00
<packing>
<property name="pack_type">end</property>
</packing>
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
</child>
</object>
</child>
</template>
new-call-box: clear entry on longpress
2020-12-27 11:01:35 +00:00
<object class="GtkGestureLongPress" id="long_press_back_gesture">
<property name="widget">backspace</property>
<signal name="pressed" handler="long_press_back_cb" object="CallsNewCallBox" swapped="true"/>
</object>
Add CallsNewCallBox
2018-08-01 09:41:11 +00:00
</interface>
Reference in a new issue Copy permalink