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

227 lines
8.9 KiB
Text
Raw Permalink 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.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<!-- Generated with glade 3.22.2 -->
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
<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="orientation">vertical</property>
<child>
Composer.Widget: Rename some structural widgets to make more sense
2021-01-26 21:54:14 +11:00
<object class="GtkBox" id="header_container">
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>
<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>
<child>
<object class="GtkBox" id="hidden_on_attachment_drag_over_child">
<property name="visible">True</property>
<property name="orientation">vertical</property>
<property name="spacing">6</property>
<child>
Composer.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<object class="GtkGrid" id="email_headers">
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="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.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<object class="GtkBox" id="filled_headers">
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.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<property name="margin_top">6</property>
<property name="orientation">vertical</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.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<placeholder/>
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>
<child>
Composer.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<placeholder/>
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>
<child>
Composer.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<placeholder/>
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>
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.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<property name="left_attach">0</property>
<property name="top_attach">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>
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>
Composer.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<object class="GtkRevealer" id="extended_headers_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>
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.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<object class="GtkBox" id="extended_headers">
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="orientation">vertical</property>
<child>
Composer.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<placeholder/>
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>
<child>
Composer.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<placeholder/>
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>
<child>
Composer.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<placeholder/>
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>
</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.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<property name="left_attach">0</property>
<property name="top_attach">1</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>
<child>
<object class="GtkBox" id="visible_on_attachment_drag_over_child">
<property name="visible">True</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="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="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">
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.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<property name="orientation">vertical</property>
<child>
<placeholder/>
</child>
<child>
<placeholder/>
</child>
<child>
<placeholder/>
</child>
<child>
<placeholder/>
</child>
<child>
<placeholder/>
</child>
<child>
<placeholder/>
</child>
<child>
<placeholder/>
</child>
<child>
<placeholder/>
</child>
<child>
<placeholder/>
</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>
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="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.Widget: Rework to use common header row widget Add private HeaderRow and EntryHeaderRow widgets for displaying editable headers in the composer, convert to using that to wrap up common properties and functionality for each of the header rows.
2021-01-27 00:10:49 +11:00
<object class="GtkToggleButton" id="show_extended_headers">
<property name="visible">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="icon_name">view-more-horizontal-symbolic</property>
</object>
</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>
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