nettika/geary
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
geary/ui/composer-widget.ui

528 lines
28 KiB
Text
Raw Normal View History

Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<?xml version="1.0" encoding="UTF-8"?>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<!-- Generated with glade 3.22.0 -->
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<interface>
Swap position of UL and OL lists, to be in that order.
2017-12-12 23:31:27 +11:00
<requires lib="gtk+" version="3.20"/>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<template class="ComposerWidget" parent="GtkEventBox">
<property name="visible">True</property>
Swap position of UL and OL lists, to be in that order.
2017-12-12 23:31:27 +11:00
<property name="can_focus">False</property>
<signal name="drag-data-received" handler="on_drag_data_received" swapped="no"/>
<signal name="drag-drop" handler="on_drag_drop" swapped="no"/>
<signal name="drag-leave" handler="on_drag_leave" swapped="no"/>
<signal name="drag-motion" handler="on_drag_motion" swapped="no"/>
Composer.Widget: Add focused_input_widget property Support tracking the last focused input widget so that text can be inserted into it as needed.
2020-07-08 16:07:38 +10:00
<signal name="set-focus-child" handler="on_set_focus_child" after="yes" swapped="no"/>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<child>
<object class="GtkBox" id="composer_container">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<child>
<object class="GtkBox" id="header_area">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkBox" id="hidden_on_attachment_drag_over">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<object class="GtkBox" id="hidden_on_attachment_drag_over_child">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<property name="spacing">6</property>
<child>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<object class="GtkBox" id="recipients">
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="margin_start">6</property>
<property name="margin_end">6</property>
<property name="margin_top">6</property>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="orientation">vertical</property>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<child>
composer: Move formatting buttons to new toolbar Splits the toolbar at the top of the composer into two action bars at the bottom. One is always visible and contains undo, redo, spellcheck, a menu, and a button to toggle the other action bar. The other action bar contains the formatting buttons. Also cleans up the margins around the fields at the top. Implemented according to the mockups at https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png
2020-01-04 02:09:38 -06:00
<object class="GtkBox" id="from_row">
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="margin_bottom">6</property>
<property name="spacing">6</property>
<child>
<object class="GtkLabel" id="from_label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
Composer.Widget: Do not set double dot after 'From' label We do not set double dots after the other labels so remove it for the 'From' label as well. Therefore, adjust the .ui file to have the right label (with the mnemonic underscore) and remove the adjustment of it in code.
2020-03-28 12:07:16 +01:00
<property name="label" translatable="yes" comments="Geary account mail will be sent from">_From</property>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="use_underline">True</property>
<property name="justify">right</property>
<property name="mnemonic_widget">to_box</property>
<property name="xalign">1</property>
<style>
<class name="dim-label"/>
</style>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkBox" id="from_container">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="hexpand">True</property>
<property name="orientation">vertical</property>
<child>
<object class="GtkLabel" id="from_single">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkComboBoxText" id="from_multiple">
<property name="visible">True</property>
<property name="can_focus">False</property>
<signal name="changed" handler="on_envelope_changed" swapped="no"/>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
</object>
<packing>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">12</property>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
</packing>
</child>
<child>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<object class="GtkBox" id="to_row">
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="margin_bottom">6</property>
<property name="spacing">6</property>
<child>
<object class="GtkLabel" id="to_label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes" comments="Address(es) e-mail is to be sent to">_To</property>
<property name="use_underline">True</property>
<property name="justify">right</property>
<property name="mnemonic_widget">to_box</property>
<property name="xalign">1</property>
<style>
<class name="dim-label"/>
</style>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkBox" id="to_box">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="hexpand">True</property>
<child>
<placeholder/>
</child>
<child>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<object class="GtkToggleButton" id="show_extended_fields">
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<property name="tooltip_text" translatable="yes">Show Cc, Bcc, and Reply-To fields</property>
<property name="action_name">win.show-extended-headers</property>
<child>
<object class="GtkImage">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="icon_name">view-more-horizontal-symbolic</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="pack_type">end</property>
<property name="position">1</property>
</packing>
</child>
<style>
<class name="linked"/>
</style>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
</object>
<packing>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">13</property>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
</packing>
</child>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<child>
<object class="GtkBox" id="filled_fields">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
</object>
</child>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<child>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<object class="GtkRevealer" id="extended_fields_revealer">
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<child>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<object class="GtkBox" id="extended_fields_box">
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<child>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<object class="GtkBox" id="cc_row">
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="visible">True</property>
<property name="can_focus">False</property>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<property name="margin_bottom">6</property>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="spacing">6</property>
<child>
<object class="GtkLabel" id="cc_label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">_Cc</property>
<property name="use_underline">True</property>
<property name="justify">right</property>
<property name="mnemonic_widget">to_box</property>
<property name="xalign">1</property>
<style>
<class name="dim-label"/>
</style>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<object class="GtkBox" id="cc_box">
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="hexpand">True</property>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<style>
<class name="linked"/>
</style>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<object class="GtkBox" id="bcc_row">
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">6</property>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<property name="margin_bottom">6</property>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<child>
<object class="GtkLabel" id="bcc_label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">_Bcc</property>
<property name="use_underline">True</property>
<property name="justify">right</property>
<property name="mnemonic_widget">to_box</property>
<property name="xalign">1</property>
<style>
<class name="dim-label"/>
</style>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<object class="GtkBox" id="bcc_box">
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="hexpand">True</property>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<style>
<class name="linked"/>
</style>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
<child>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<object class="GtkBox" id="reply_to_row">
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">6</property>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<property name="margin_bottom">6</property>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<child>
<object class="GtkLabel" id="reply_to_label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">_Reply-To</property>
<property name="use_underline">True</property>
<property name="justify">right</property>
<property name="mnemonic_widget">to_box</property>
<property name="xalign">1</property>
<style>
<class name="dim-label"/>
</style>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<object class="GtkBox" id="reply_to_box">
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="hexpand">True</property>
composer: Do not hide nonempty extended fields This way, you won't forget about an important field (such as CC) if the extended fields are hidden. Fixes #675.
2020-01-21 13:14:31 -06:00
<style>
<class name="linked"/>
</style>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">2</property>
</packing>
</child>
</object>
</child>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
</object>
<packing>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">14</property>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
</packing>
</child>
<child>
composer: Move formatting buttons to new toolbar Splits the toolbar at the top of the composer into two action bars at the bottom. One is always visible and contains undo, redo, spellcheck, a menu, and a button to toggle the other action bar. The other action bar contains the formatting buttons. Also cleans up the margins around the fields at the top. Implemented according to the mockups at https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png
2020-01-04 02:09:38 -06:00
<object class="GtkBox" id="subject_row">
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="spacing">6</property>
composer: Move formatting buttons to new toolbar Splits the toolbar at the top of the composer into two action bars at the bottom. One is always visible and contains undo, redo, spellcheck, a menu, and a button to toggle the other action bar. The other action bar contains the formatting buttons. Also cleans up the margins around the fields at the top. Implemented according to the mockups at https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png
2020-01-04 02:09:38 -06:00
<property name="margin-bottom">6</property>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<child>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<object class="GtkLabel" id="subject_label">
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="halign">end</property>
<property name="label" translatable="yes">_Subject</property>
<property name="use_underline">True</property>
<property name="justify">right</property>
<property name="mnemonic_widget">subject_entry</property>
<property name="xalign">1</property>
<style>
<class name="dim-label"/>
</style>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<object class="GtkEntry" id="subject_entry">
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<property name="visible">True</property>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="can_focus">True</property>
<property name="hexpand">True</property>
<property name="invisible_char">•</property>
<signal name="changed" handler="on_subject_changed" swapped="no"/>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
<packing>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">15</property>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
</packing>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
Reenable undo/redo composer actions. * src/client/composer/composer-web-view.vala (ComposerWebView): Add new ::command_stack_changed signal to manage undo/redo enabled state, hook it up to a JS callback. Add ::is_empty property as a non-functioning shim in lieu of can_undo going away. Remove ::can_undo and ::can_redo, replace them with methods to actually fire an undo and redo. * src/client/composer/composer-widget.vala (ComposerWidget): Use ClientWebView::is_empty rather inplace of can_redo for determining editing state. Remove old undo/redo signal hookups, replace with ::command_stack_changed and manage action enable state from there. (ComposerWidget::action_entries): Add explicit actions for undo/redo, since they need some custom code over on on the web process side. (ComposerWidget::on_compose_as_html_toggled): Explciitly manage the visibility of rich text toolbar buttons, don't rely on obscure GtkBuilder magic that Glade doesn't support. * ui/composer-web-view.js: Add a mutation observer for the message body and explcit methods for firing undo/redo commands, so we can keep track of how the command stack changes. As it does, fire commandStackChanged messages back to the client process. Explicity set the message body as content-editable after the document has been mutated for quotes, etc. * ui/composer-widget.ui: Add bonus undo/redo toobar buttons for the composer.
2017-01-04 18:53:28 +11:00
<property name="position">0</property>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
</packing>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
<child>
<object class="GtkBox" id="visible_on_attachment_drag_over">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<object class="GtkBox" id="visible_on_attachment_drag_over_child">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="valign">center</property>
<property name="orientation">vertical</property>
<property name="spacing">6</property>
<child>
<object class="GtkLabel" id="label1">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="valign">center</property>
<property name="label" translatable="yes">Drop files here</property>
<attributes>
<attribute name="weight" value="bold"/>
</attributes>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label2">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="valign">center</property>
<property name="label" translatable="yes">To add them as attachments</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">1</property>
</packing>
</child>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
Reenable undo/redo composer actions. * src/client/composer/composer-web-view.vala (ComposerWebView): Add new ::command_stack_changed signal to manage undo/redo enabled state, hook it up to a JS callback. Add ::is_empty property as a non-functioning shim in lieu of can_undo going away. Remove ::can_undo and ::can_redo, replace them with methods to actually fire an undo and redo. * src/client/composer/composer-widget.vala (ComposerWidget): Use ClientWebView::is_empty rather inplace of can_redo for determining editing state. Remove old undo/redo signal hookups, replace with ::command_stack_changed and manage action enable state from there. (ComposerWidget::action_entries): Add explicit actions for undo/redo, since they need some custom code over on on the web process side. (ComposerWidget::on_compose_as_html_toggled): Explciitly manage the visibility of rich text toolbar buttons, don't rely on obscure GtkBuilder magic that Glade doesn't support. * ui/composer-web-view.js: Add a mutation observer for the message body and explcit methods for firing undo/redo commands, so we can keep track of how the command stack changes. As it does, fire commandStackChanged messages back to the client process. Explicity set the message body as content-editable after the document has been mutated for quotes, etc. * ui/composer-widget.ui: Add bonus undo/redo toobar buttons for the composer.
2017-01-04 18:53:28 +11:00
<property name="position">0</property>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
</packing>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">2</property>
</packing>
</child>
<child>
Scope composer editor shortcuts to the toolbar and web view only This prevents something like Ctrl+I being typed in the subject line triggering italic in the editor.
2019-02-13 22:58:01 +11:00
<object class="GtkGrid" id="editor_container">
Composer.Widget: Split email body editing code out into separate widget Create a new Composer.Editor widget and move all body web view and action bar related code from the main widget there. This helps to clearly delineate concerns of the two classes, it substantially reduces the complexity of the main widget, and should reduce the odds of further breakage like that fixed by the previous commit less likely in the future.
2020-08-28 17:56:55 +10:00
<property name="orientation">vertical</property>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
</object>
<packing>
Scope composer editor shortcuts to the toolbar and web view only This prevents something like Ctrl+I being typed in the subject line triggering italic in the editor.
2019-02-13 22:58:01 +11:00
<property name="expand">False</property>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
<property name="fill">True</property>
ui/composer-widget.ui: Make action bars child of the editor box Editor actions are defined on the editor box, so action bars need to be decedents of that to pick up the actions.
2020-08-28 14:06:27 +10:00
<property name="position">3</property>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
</packing>
</child>
<child>
<object class="GtkBox" id="attachments_box">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<child>
<placeholder/>
</child>
Composer.Widget: Place composer action bars into their own container Use CSS instead of widget props to ensure widgets have sufficient white space. This will allow adding additional action bars (e.g. by plugins) in a more straight-forward manner.
2020-07-07 16:25:05 +10:00
<style>
<class name="geary-attachments-box"/>
</style>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
Composer.Widget: Place composer action bars into their own container Use CSS instead of widget props to ensure widgets have sufficient white space. This will allow adding additional action bars (e.g. by plugins) in a more straight-forward manner.
2020-07-07 16:25:05 +10:00
<property name="position">5</property>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
</packing>
</child>
</object>
</child>
</template>
composer: Better UI for Cc/Bcc/Reply-To fields Implemented according to the mockups at <https://gitlab.gnome.org/Teams/Design/app-mockups/raw/master/mail/composer.png>. - Use an animated revealer rather than instantly showing/hiding the fields - Include Cc in the "extended fields" - Use a toggle button instead of a menu item to show/hide these fields, for better discoverability
2020-01-01 19:25:54 -06:00
<object class="GtkSizeGroup" id="field_labels">
<widgets>
<widget name="from_label"/>
<widget name="to_label"/>
<widget name="cc_label"/>
<widget name="bcc_label"/>
<widget name="reply_to_label"/>
<widget name="subject_label"/>
</widgets>
</object>
Use GLib.Actions in the composer. Bug 770356. Now using these instead of the old composer's actions. This led to quite some changes: * Use GLib.ActionEntry instead of Gtk.ActionEntry in composer-widget.vala * Action names can now be specified in the UI files. * Use templates for the ComposerHeaderBar. Remove Pillbar as superclass, since that was no longer necessary. * Merge ComposerToolbar into ComposerWidget. * Since actions can now be parameterized, some methods could be merged (e.g. font size methods). * The menu button in the composer now automatically uses a popover. * Some methods and classes really deserved more comments. * necessary POTFILES.in changes Signed-off-by: Niels De Graef <nielsdegraef@gmail.com>
2016-08-22 11:09:25 +02:00
</interface>
Reference in a new issue Copy permalink