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

914 lines
46 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"?>
Replace composer keyboard shortcut with standard widget action scoping Rather than adding and removing shortcuts when the composer's web view gains and loses focus to avoid invoking main window shortcuts, just rely on standard GTK action scoping rules. This fixes editing shortcuts like Ctrl+I breaking when clicking on toolbar buttons, a crasher because the composer left the undo button enabled after it was closed, and allows Escape to close the composer from anywherre. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=774651, https://bugzilla.gnome.org/show_bug.cgi?id=785187, and https://bugzilla.gnome.org/show_bug.cgi?id=741741
2019-02-13 22:19:44 +11:00
<!-- Generated with glade 3.22.1 -->
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"/>
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>
<property name="spacing">2</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>
<object class="GtkGrid" id="recipients">
<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>
<property name="column_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>
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="margin_top">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
<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>
<style>
<class name="dim-label"/>
</style>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="cc_label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</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="margin_top">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
<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>
<style>
<class name="dim-label"/>
</style>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkEventBox" id="to_box">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="hexpand">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkEventBox" id="cc_box">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="hexpand">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkEntry" id="subject_entry">
<property name="visible">True</property>
<property name="can_focus">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="margin_top">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
<property name="hexpand">True</property>
<property name="invisible_char">•</property>
Fix TRUE/FALSE listed as composer drafts status. * src/client/composer/composer-widget.vala (Composer): Replace use of inappropriate public properties and obtuse property bindings with a subject_changed signal and private properties that update the info label in their setter, so it's obvious how the whole thing works. Move code for managing a detached compoer's window title to the ComposerWindow class.
2018-04-14 12:37:22 +10:00
<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="left_attach">1</property>
<property name="top_attach">5</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="subject_label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</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="margin_top">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
<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>
<style>
<class name="dim-label"/>
</style>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">5</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="bcc_label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</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="margin_top">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
<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>
<style>
<class name="dim-label"/>
</style>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">3</property>
</packing>
</child>
<child>
<object class="GtkEventBox" id="bcc_box">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="hexpand">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">3</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="reply_to_label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</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="margin_top">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
<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>
<style>
<class name="dim-label"/>
</style>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">4</property>
</packing>
</child>
<child>
<object class="GtkEventBox" id="reply_to_box">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="hexpand">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">4</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="from_label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes" comments="Geary account mail will be sent from">From</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="use_underline">True</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="justify">right</property>
<property name="mnemonic_widget">to_box</property>
<style>
<class name="dim-label"/>
</style>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkBox" id="from_container">
<property name="visible">True</property>
<property name="can_focus">False</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>
Ensure draft is saved when envelope (from, to, etc) changes. Bug 726290. * src/client/composer/composer-widget.vala (ComposerWidget): Rename subject changed handler to something more generic, hook that up to the to/cc/bcc & reply_to entries. * ui/composer-widget.ui: Hook up multiple to on_envelope_changed, make subject entry use that as well.
2017-01-16 15:40:29 +11:00
<signal name="changed" handler="on_envelope_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>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</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">
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>
<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="GtkBox" id="composer_toolbar">
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>
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="margin_start">6</property>
<property name="margin_end">6</property>
Add margin_bottom padding to composer_toolbar
2019-02-18 00:16:22 +00:00
<property name="margin_bottom">4</property>
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="spacing">6</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
<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="GtkBox" id="command_buttons">
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="visible">True</property>
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="can_focus">False</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
<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="GtkButton">
Fix composer UI brokenness when compiled under vala 0.36. Don't rely ComposerState::state notify and property bindings firing when the value hasn't actually changed to update the composer's UI. This is works around Vala Bug 631267 landing. * src/client/composer/composer-headerbar.vala (ComposerHeaderbar): Add signal and methods to be called explicity on state changes, rather than relying on being notified of ComposerWidget::state changing. * src/client/composer/composer-widget.vala (ComposerWidget): Hook up new ComposerHeaderbar signal and method. Remove notify and property bindings on ::state property, move related code to new ::update_composer_view method and call that as needed. Remove overridden ::show_all, because the UI state should now always be consistent with ::state. Clean up various methods. * src/client/composer/email-entry.vala (EmailEntry::EmailEntry): Make widget visible by default, since we are no longer calling ComposerWidget::show_all(). * src/client/application/geary-controller.vala: Don't call show all on new composers, they now manage their visibility properly. * ui/composer-headerbar.ui: Make toolbar icons visible by default. * ui/composer-widget.ui: Make toolbar icons visible by default, set Send button icon here rather than in the class.
2017-03-04 13:42:53 +11:00
<property name="visible">True</property>
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="can_focus">True</property>
<property name="focus_on_click">False</property>
<property name="receives_default">False</property>
Remove shortcuts from composer tooltips These are rendundant now that the shortcut overlay exists.
2019-11-18 18:31:59 +11:00
<property name="tooltip_text" translatable="yes">Undo last edit</property>
Rework action names groups across the client Introduce a new standard edit action group "edt" for editing actions such as copy and undo, separate from the "win" window action group, so that editing actions can be scoped to specific widgets and overridden by children. Add new Action namespace with sub-namespaces for the app, win and edt namespaces and move consts from GearyApplication there. Update call sites and UI files, use consistent approach to setting up action groups across all classes that use them.
2019-11-07 11:47:41 +11:00
<property name="action_name">edt.undo</property>
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="always_show_image">True</property>
<child>
<object class="GtkImage">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="pixel_size">16</property>
<property name="icon_name">edit-undo-symbolic</property>
</object>
</child>
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
</object>
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
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
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
</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
<child>
<object class="GtkButton">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="focus_on_click">False</property>
<property name="receives_default">False</property>
Remove shortcuts from composer tooltips These are rendundant now that the shortcut overlay exists.
2019-11-18 18:31:59 +11:00
<property name="tooltip_text" translatable="yes">Redo last edit</property>
Rework action names groups across the client Introduce a new standard edit action group "edt" for editing actions such as copy and undo, separate from the "win" window action group, so that editing actions can be scoped to specific widgets and overridden by children. Add new Action namespace with sub-namespaces for the app, win and edt namespaces and move consts from GearyApplication there. Update call sites and UI files, use consistent approach to setting up action groups across all classes that use them.
2019-11-07 11:47:41 +11:00
<property name="action_name">edt.redo</property>
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="always_show_image">True</property>
<child>
<object class="GtkImage">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="pixel_size">16</property>
<property name="icon_name">edit-redo-symbolic</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
<style>
<class name="linked"/>
</style>
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
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</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="GtkBox" id="font_style_buttons">
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="visible">True</property>
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="can_focus">False</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
<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="GtkToggleButton" id="bold_button">
Fix composer UI brokenness when compiled under vala 0.36. Don't rely ComposerState::state notify and property bindings firing when the value hasn't actually changed to update the composer's UI. This is works around Vala Bug 631267 landing. * src/client/composer/composer-headerbar.vala (ComposerHeaderbar): Add signal and methods to be called explicity on state changes, rather than relying on being notified of ComposerWidget::state changing. * src/client/composer/composer-widget.vala (ComposerWidget): Hook up new ComposerHeaderbar signal and method. Remove notify and property bindings on ::state property, move related code to new ::update_composer_view method and call that as needed. Remove overridden ::show_all, because the UI state should now always be consistent with ::state. Clean up various methods. * src/client/composer/email-entry.vala (EmailEntry::EmailEntry): Make widget visible by default, since we are no longer calling ComposerWidget::show_all(). * src/client/application/geary-controller.vala: Don't call show all on new composers, they now manage their visibility properly. * ui/composer-headerbar.ui: Make toolbar icons visible by default. * ui/composer-widget.ui: Make toolbar icons visible by default, set Send button icon here rather than in the class.
2017-03-04 13:42:53 +11:00
<property name="visible">True</property>
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="can_focus">True</property>
<property name="focus_on_click">False</property>
<property name="receives_default">False</property>
Remove shortcuts from composer tooltips These are rendundant now that the shortcut overlay exists.
2019-11-18 18:31:59 +11:00
<property name="tooltip_text" translatable="yes">Bold text</property>
Rework action names groups across the client Introduce a new standard edit action group "edt" for editing actions such as copy and undo, separate from the "win" window action group, so that editing actions can be scoped to specific widgets and overridden by children. Add new Action namespace with sub-namespaces for the app, win and edt namespaces and move consts from GearyApplication there. Update call sites and UI files, use consistent approach to setting up action groups across all classes that use them.
2019-11-07 11:47:41 +11:00
<property name="action_name">edt.bold</property>
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="always_show_image">True</property>
<child>
<object class="GtkImage" id="bold_image">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="pixel_size">16</property>
<property name="icon_name">format-text-bold-symbolic</property>
</object>
</child>
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
</object>
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
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
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
</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>
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="GtkToggleButton" id="italics_button">
Fix composer UI brokenness when compiled under vala 0.36. Don't rely ComposerState::state notify and property bindings firing when the value hasn't actually changed to update the composer's UI. This is works around Vala Bug 631267 landing. * src/client/composer/composer-headerbar.vala (ComposerHeaderbar): Add signal and methods to be called explicity on state changes, rather than relying on being notified of ComposerWidget::state changing. * src/client/composer/composer-widget.vala (ComposerWidget): Hook up new ComposerHeaderbar signal and method. Remove notify and property bindings on ::state property, move related code to new ::update_composer_view method and call that as needed. Remove overridden ::show_all, because the UI state should now always be consistent with ::state. Clean up various methods. * src/client/composer/email-entry.vala (EmailEntry::EmailEntry): Make widget visible by default, since we are no longer calling ComposerWidget::show_all(). * src/client/application/geary-controller.vala: Don't call show all on new composers, they now manage their visibility properly. * ui/composer-headerbar.ui: Make toolbar icons visible by default. * ui/composer-widget.ui: Make toolbar icons visible by default, set Send button icon here rather than in the class.
2017-03-04 13:42:53 +11:00
<property name="visible">True</property>
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="can_focus">True</property>
<property name="focus_on_click">False</property>
<property name="receives_default">False</property>
Remove shortcuts from composer tooltips These are rendundant now that the shortcut overlay exists.
2019-11-18 18:31:59 +11:00
<property name="tooltip_text" translatable="yes">Italic text</property>
Rework action names groups across the client Introduce a new standard edit action group "edt" for editing actions such as copy and undo, separate from the "win" window action group, so that editing actions can be scoped to specific widgets and overridden by children. Add new Action namespace with sub-namespaces for the app, win and edt namespaces and move consts from GearyApplication there. Update call sites and UI files, use consistent approach to setting up action groups across all classes that use them.
2019-11-07 11:47:41 +11:00
<property name="action_name">edt.italic</property>
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="always_show_image">True</property>
<child>
<object class="GtkImage" id="italics_image">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="pixel_size">16</property>
<property name="icon_name">format-text-italic-symbolic</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
</object>
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
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
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>
<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="GtkToggleButton" id="underline_button">
Fix composer UI brokenness when compiled under vala 0.36. Don't rely ComposerState::state notify and property bindings firing when the value hasn't actually changed to update the composer's UI. This is works around Vala Bug 631267 landing. * src/client/composer/composer-headerbar.vala (ComposerHeaderbar): Add signal and methods to be called explicity on state changes, rather than relying on being notified of ComposerWidget::state changing. * src/client/composer/composer-widget.vala (ComposerWidget): Hook up new ComposerHeaderbar signal and method. Remove notify and property bindings on ::state property, move related code to new ::update_composer_view method and call that as needed. Remove overridden ::show_all, because the UI state should now always be consistent with ::state. Clean up various methods. * src/client/composer/email-entry.vala (EmailEntry::EmailEntry): Make widget visible by default, since we are no longer calling ComposerWidget::show_all(). * src/client/application/geary-controller.vala: Don't call show all on new composers, they now manage their visibility properly. * ui/composer-headerbar.ui: Make toolbar icons visible by default. * ui/composer-widget.ui: Make toolbar icons visible by default, set Send button icon here rather than in the class.
2017-03-04 13:42:53 +11:00
<property name="visible">True</property>
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="can_focus">True</property>
<property name="focus_on_click">False</property>
<property name="receives_default">False</property>
Remove shortcuts from composer tooltips These are rendundant now that the shortcut overlay exists.
2019-11-18 18:31:59 +11:00
<property name="tooltip_text" translatable="yes">Underline text</property>
Rework action names groups across the client Introduce a new standard edit action group "edt" for editing actions such as copy and undo, separate from the "win" window action group, so that editing actions can be scoped to specific widgets and overridden by children. Add new Action namespace with sub-namespaces for the app, win and edt namespaces and move consts from GearyApplication there. Update call sites and UI files, use consistent approach to setting up action groups across all classes that use them.
2019-11-07 11:47:41 +11:00
<property name="action_name">edt.underline</property>
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="always_show_image">True</property>
<child>
<object class="GtkImage" id="underline_image">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="pixel_size">16</property>
<property name="icon_name">format-text-underline-symbolic</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
</object>
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
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">2</property>
</packing>
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>
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
<child>
<object class="GtkToggleButton" id="strikethrough_button">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="focus_on_click">False</property>
<property name="receives_default">False</property>
Remove shortcuts from composer tooltips These are rendundant now that the shortcut overlay exists.
2019-11-18 18:31:59 +11:00
<property name="tooltip_text" translatable="yes">Strikethrough text</property>
Rework action names groups across the client Introduce a new standard edit action group "edt" for editing actions such as copy and undo, separate from the "win" window action group, so that editing actions can be scoped to specific widgets and overridden by children. Add new Action namespace with sub-namespaces for the app, win and edt namespaces and move consts from GearyApplication there. Update call sites and UI files, use consistent approach to setting up action groups across all classes that use them.
2019-11-07 11:47:41 +11:00
<property name="action_name">edt.strikethrough</property>
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="always_show_image">True</property>
<child>
<object class="GtkImage" id="strikethrough_image">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="pixel_size">16</property>
<property name="icon_name">format-text-strikethrough-symbolic</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">3</property>
</packing>
</child>
<style>
<class name="linked"/>
</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>
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
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
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>
<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="GtkBox" id="list_buttons">
Fix composer UI brokenness when compiled under vala 0.36. Don't rely ComposerState::state notify and property bindings firing when the value hasn't actually changed to update the composer's UI. This is works around Vala Bug 631267 landing. * src/client/composer/composer-headerbar.vala (ComposerHeaderbar): Add signal and methods to be called explicity on state changes, rather than relying on being notified of ComposerWidget::state changing. * src/client/composer/composer-widget.vala (ComposerWidget): Hook up new ComposerHeaderbar signal and method. Remove notify and property bindings on ::state property, move related code to new ::update_composer_view method and call that as needed. Remove overridden ::show_all, because the UI state should now always be consistent with ::state. Clean up various methods. * src/client/composer/email-entry.vala (EmailEntry::EmailEntry): Make widget visible by default, since we are no longer calling ComposerWidget::show_all(). * src/client/application/geary-controller.vala: Don't call show all on new composers, they now manage their visibility properly. * ui/composer-headerbar.ui: Make toolbar icons visible by default. * ui/composer-widget.ui: Make toolbar icons visible by default, set Send button icon here rather than in the class.
2017-03-04 13:42:53 +11:00
<property name="visible">True</property>
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="can_focus">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
<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="GtkButton" id="ulist_button">
Fix composer UI brokenness when compiled under vala 0.36. Don't rely ComposerState::state notify and property bindings firing when the value hasn't actually changed to update the composer's UI. This is works around Vala Bug 631267 landing. * src/client/composer/composer-headerbar.vala (ComposerHeaderbar): Add signal and methods to be called explicity on state changes, rather than relying on being notified of ComposerWidget::state changing. * src/client/composer/composer-widget.vala (ComposerWidget): Hook up new ComposerHeaderbar signal and method. Remove notify and property bindings on ::state property, move related code to new ::update_composer_view method and call that as needed. Remove overridden ::show_all, because the UI state should now always be consistent with ::state. Clean up various methods. * src/client/composer/email-entry.vala (EmailEntry::EmailEntry): Make widget visible by default, since we are no longer calling ComposerWidget::show_all(). * src/client/application/geary-controller.vala: Don't call show all on new composers, they now manage their visibility properly. * ui/composer-headerbar.ui: Make toolbar icons visible by default. * ui/composer-widget.ui: Make toolbar icons visible by default, set Send button icon here rather than in the class.
2017-03-04 13:42:53 +11:00
<property name="visible">True</property>
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="can_focus">True</property>
<property name="focus_on_click">False</property>
<property name="receives_default">False</property>
Remove shortcuts from composer tooltips These are rendundant now that the shortcut overlay exists.
2019-11-18 18:31:59 +11:00
<property name="tooltip_text" translatable="yes">Insert bulleted list</property>
Rework action names groups across the client Introduce a new standard edit action group "edt" for editing actions such as copy and undo, separate from the "win" window action group, so that editing actions can be scoped to specific widgets and overridden by children. Add new Action namespace with sub-namespaces for the app, win and edt namespaces and move consts from GearyApplication there. Update call sites and UI files, use consistent approach to setting up action groups across all classes that use them.
2019-11-07 11:47:41 +11:00
<property name="action_name">edt.ulist</property>
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="always_show_image">True</property>
<child>
<object class="GtkImage" id="ulist_image">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="pixel_size">16</property>
<property name="icon_name">format-unordered-list-symbolic</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
</object>
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
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
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>
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
<child>
<object class="GtkButton" id="olist_button">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="focus_on_click">False</property>
<property name="receives_default">False</property>
Remove shortcuts from composer tooltips These are rendundant now that the shortcut overlay exists.
2019-11-18 18:31:59 +11:00
<property name="tooltip_text" translatable="yes">Insert numbered list</property>
Rework action names groups across the client Introduce a new standard edit action group "edt" for editing actions such as copy and undo, separate from the "win" window action group, so that editing actions can be scoped to specific widgets and overridden by children. Add new Action namespace with sub-namespaces for the app, win and edt namespaces and move consts from GearyApplication there. Update call sites and UI files, use consistent approach to setting up action groups across all classes that use them.
2019-11-07 11:47:41 +11:00
<property name="action_name">edt.olist</property>
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="always_show_image">True</property>
<child>
<object class="GtkImage" id="olist_image">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="pixel_size">16</property>
<property name="icon_name">format-ordered-list-symbolic</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
<style>
<class name="linked"/>
</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>
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
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">2</property>
</packing>
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>
<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="GtkBox" id="indentation_buttons">
Fix composer UI brokenness when compiled under vala 0.36. Don't rely ComposerState::state notify and property bindings firing when the value hasn't actually changed to update the composer's UI. This is works around Vala Bug 631267 landing. * src/client/composer/composer-headerbar.vala (ComposerHeaderbar): Add signal and methods to be called explicity on state changes, rather than relying on being notified of ComposerWidget::state changing. * src/client/composer/composer-widget.vala (ComposerWidget): Hook up new ComposerHeaderbar signal and method. Remove notify and property bindings on ::state property, move related code to new ::update_composer_view method and call that as needed. Remove overridden ::show_all, because the UI state should now always be consistent with ::state. Clean up various methods. * src/client/composer/email-entry.vala (EmailEntry::EmailEntry): Make widget visible by default, since we are no longer calling ComposerWidget::show_all(). * src/client/application/geary-controller.vala: Don't call show all on new composers, they now manage their visibility properly. * ui/composer-headerbar.ui: Make toolbar icons visible by default. * ui/composer-widget.ui: Make toolbar icons visible by default, set Send button icon here rather than in the class.
2017-03-04 13:42:53 +11:00
<property name="visible">True</property>
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="can_focus">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
<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="GtkButton" id="indent_button">
Fix composer UI brokenness when compiled under vala 0.36. Don't rely ComposerState::state notify and property bindings firing when the value hasn't actually changed to update the composer's UI. This is works around Vala Bug 631267 landing. * src/client/composer/composer-headerbar.vala (ComposerHeaderbar): Add signal and methods to be called explicity on state changes, rather than relying on being notified of ComposerWidget::state changing. * src/client/composer/composer-widget.vala (ComposerWidget): Hook up new ComposerHeaderbar signal and method. Remove notify and property bindings on ::state property, move related code to new ::update_composer_view method and call that as needed. Remove overridden ::show_all, because the UI state should now always be consistent with ::state. Clean up various methods. * src/client/composer/email-entry.vala (EmailEntry::EmailEntry): Make widget visible by default, since we are no longer calling ComposerWidget::show_all(). * src/client/application/geary-controller.vala: Don't call show all on new composers, they now manage their visibility properly. * ui/composer-headerbar.ui: Make toolbar icons visible by default. * ui/composer-widget.ui: Make toolbar icons visible by default, set Send button icon here rather than in the class.
2017-03-04 13:42:53 +11:00
<property name="visible">True</property>
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="can_focus">True</property>
<property name="focus_on_click">False</property>
<property name="receives_default">False</property>
Remove shortcuts from composer tooltips These are rendundant now that the shortcut overlay exists.
2019-11-18 18:31:59 +11:00
<property name="tooltip_text" translatable="yes">Indent or quote text</property>
Rework action names groups across the client Introduce a new standard edit action group "edt" for editing actions such as copy and undo, separate from the "win" window action group, so that editing actions can be scoped to specific widgets and overridden by children. Add new Action namespace with sub-namespaces for the app, win and edt namespaces and move consts from GearyApplication there. Update call sites and UI files, use consistent approach to setting up action groups across all classes that use them.
2019-11-07 11:47:41 +11:00
<property name="action_name">edt.indent</property>
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="always_show_image">True</property>
<child>
<object class="GtkImage" id="indent_image">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="pixel_size">16</property>
<property name="icon_name">format-indent-more-symbolic</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkButton" id="outdent_button">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="focus_on_click">False</property>
<property name="receives_default">False</property>
Remove shortcuts from composer tooltips These are rendundant now that the shortcut overlay exists.
2019-11-18 18:31:59 +11:00
<property name="tooltip_text" translatable="yes">Un-indent or unquote text</property>
Rework action names groups across the client Introduce a new standard edit action group "edt" for editing actions such as copy and undo, separate from the "win" window action group, so that editing actions can be scoped to specific widgets and overridden by children. Add new Action namespace with sub-namespaces for the app, win and edt namespaces and move consts from GearyApplication there. Update call sites and UI files, use consistent approach to setting up action groups across all classes that use them.
2019-11-07 11:47:41 +11:00
<property name="action_name">edt.outdent</property>
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="always_show_image">True</property>
<child>
<object class="GtkImage" id="outdent_image">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="pixel_size">16</property>
<property name="icon_name">format-indent-less-symbolic</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
</object>
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
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
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>
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
<style>
<class name="linked"/>
</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>
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
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">3</property>
</packing>
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>
Swap position of UL and OL lists, to be in that order.
2017-12-12 23:31:27 +11:00
<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="GtkBox" id="insert_buttons">
Added support for lists in composer This attempts to solve bug [#714921](https://bugzilla.gnome.org/show_bug.cgi?id=714921). They are available as two buttons on the format bar, next to font options. The icons I used are taken from a free icons site just for demo purposes and should be replaced by new icons. Also I did not include hotkeys mainly because I could not come up with a good one, also they are pretty uncommon I think. Also added new icons to icons/CMakeLists.txt
2017-12-06 17:04:18 -03:00
<property name="visible">True</property>
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="can_focus">False</property>
Added support for lists in composer This attempts to solve bug [#714921](https://bugzilla.gnome.org/show_bug.cgi?id=714921). They are available as two buttons on the format bar, next to font options. The icons I used are taken from a free icons site just for demo purposes and should be replaced by new icons. Also I did not include hotkeys mainly because I could not come up with a good one, also they are pretty uncommon I think. Also added new icons to icons/CMakeLists.txt
2017-12-06 17:04:18 -03:00
<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="GtkButton" id="insert_link_button">
Added support for lists in composer This attempts to solve bug [#714921](https://bugzilla.gnome.org/show_bug.cgi?id=714921). They are available as two buttons on the format bar, next to font options. The icons I used are taken from a free icons site just for demo purposes and should be replaced by new icons. Also I did not include hotkeys mainly because I could not come up with a good one, also they are pretty uncommon I think. Also added new icons to icons/CMakeLists.txt
2017-12-06 17:04:18 -03:00
<property name="visible">True</property>
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="can_focus">True</property>
<property name="focus_on_click">False</property>
<property name="receives_default">False</property>
Remove shortcuts from composer tooltips These are rendundant now that the shortcut overlay exists.
2019-11-18 18:31:59 +11:00
<property name="tooltip_text" translatable="yes">Insert or update text link</property>
Rework action names groups across the client Introduce a new standard edit action group "edt" for editing actions such as copy and undo, separate from the "win" window action group, so that editing actions can be scoped to specific widgets and overridden by children. Add new Action namespace with sub-namespaces for the app, win and edt namespaces and move consts from GearyApplication there. Update call sites and UI files, use consistent approach to setting up action groups across all classes that use them.
2019-11-07 11:47:41 +11:00
<property name="action_name">edt.insert-link</property>
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="always_show_image">True</property>
<child>
<object class="GtkImage" id="insert_link_image">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="pixel_size">16</property>
<property name="icon_name">insert-link-symbolic</property>
</object>
</child>
Added support for lists in composer This attempts to solve bug [#714921](https://bugzilla.gnome.org/show_bug.cgi?id=714921). They are available as two buttons on the format bar, next to font options. The icons I used are taken from a free icons site just for demo purposes and should be replaced by new icons. Also I did not include hotkeys mainly because I could not come up with a good one, also they are pretty uncommon I think. Also added new icons to icons/CMakeLists.txt
2017-12-06 17:04:18 -03:00
</object>
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
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
Added support for lists in composer This attempts to solve bug [#714921](https://bugzilla.gnome.org/show_bug.cgi?id=714921). They are available as two buttons on the format bar, next to font options. The icons I used are taken from a free icons site just for demo purposes and should be replaced by new icons. Also I did not include hotkeys mainly because I could not come up with a good one, also they are pretty uncommon I think. Also added new icons to icons/CMakeLists.txt
2017-12-06 17:04:18 -03:00
</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="GtkButton" id="insert_image_button">
Added support for lists in composer This attempts to solve bug [#714921](https://bugzilla.gnome.org/show_bug.cgi?id=714921). They are available as two buttons on the format bar, next to font options. The icons I used are taken from a free icons site just for demo purposes and should be replaced by new icons. Also I did not include hotkeys mainly because I could not come up with a good one, also they are pretty uncommon I think. Also added new icons to icons/CMakeLists.txt
2017-12-06 17:04:18 -03:00
<property name="visible">True</property>
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="can_focus">True</property>
<property name="focus_on_click">False</property>
<property name="receives_default">False</property>
Remove shortcuts from composer tooltips These are rendundant now that the shortcut overlay exists.
2019-11-18 18:31:59 +11:00
<property name="tooltip_text" translatable="yes">Insert an image</property>
Rework action names groups across the client Introduce a new standard edit action group "edt" for editing actions such as copy and undo, separate from the "win" window action group, so that editing actions can be scoped to specific widgets and overridden by children. Add new Action namespace with sub-namespaces for the app, win and edt namespaces and move consts from GearyApplication there. Update call sites and UI files, use consistent approach to setting up action groups across all classes that use them.
2019-11-07 11:47:41 +11:00
<property name="action_name">edt.insert-image</property>
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="always_show_image">True</property>
<child>
<object class="GtkImage">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="pixel_size">16</property>
<property name="icon_name">insert-image-symbolic</property>
</object>
</child>
Added support for lists in composer This attempts to solve bug [#714921](https://bugzilla.gnome.org/show_bug.cgi?id=714921). They are available as two buttons on the format bar, next to font options. The icons I used are taken from a free icons site just for demo purposes and should be replaced by new icons. Also I did not include hotkeys mainly because I could not come up with a good one, also they are pretty uncommon I think. Also added new icons to icons/CMakeLists.txt
2017-12-06 17:04:18 -03:00
</object>
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
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
Added support for lists in composer This attempts to solve bug [#714921](https://bugzilla.gnome.org/show_bug.cgi?id=714921). They are available as two buttons on the format bar, next to font options. The icons I used are taken from a free icons site just for demo purposes and should be replaced by new icons. Also I did not include hotkeys mainly because I could not come up with a good one, also they are pretty uncommon I think. Also added new icons to icons/CMakeLists.txt
2017-12-06 17:04:18 -03:00
</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
<style>
<class name="linked"/>
</style>
Swap position of UL and OL lists, to be in that order.
2017-12-12 23:31:27 +11:00
</object>
Added support for lists in composer This attempts to solve bug [#714921](https://bugzilla.gnome.org/show_bug.cgi?id=714921). They are available as two buttons on the format bar, next to font options. The icons I used are taken from a free icons site just for demo purposes and should be replaced by new icons. Also I did not include hotkeys mainly because I could not come up with a good one, also they are pretty uncommon I think. Also added new icons to icons/CMakeLists.txt
2017-12-06 17:04:18 -03:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
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="position">4</property>
Added support for lists in composer This attempts to solve bug [#714921](https://bugzilla.gnome.org/show_bug.cgi?id=714921). They are available as two buttons on the format bar, next to font options. The icons I used are taken from a free icons site just for demo purposes and should be replaced by new icons. Also I did not include hotkeys mainly because I could not come up with a good one, also they are pretty uncommon I think. Also added new icons to icons/CMakeLists.txt
2017-12-06 17:04:18 -03:00
</packing>
Swap position of UL and OL lists, to be in that order.
2017-12-12 23:31:27 +11: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
<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="GtkButton" id="remove_format_button">
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>
Use click-to-focus prop on toolbar buttons rather than other workarounds. * src/client/application/geary-controller.vala (GearyController::archive_or_delete_selection_async): Don't modify the focus after archiving/trashing/deleting. * src/client/components/pill-toolbar.vala, ui/composer-headerbar.ui, ui/composer-widget.ui: Ensure all toolbar buttons are focusable but have focus-on-click disabled.
2016-10-20 16:58:48 +11:00
<property name="can_focus">True</property>
<property name="focus_on_click">False</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="receives_default">False</property>
Remove shortcuts from composer tooltips These are rendundant now that the shortcut overlay exists.
2019-11-18 18:31:59 +11:00
<property name="tooltip_text" translatable="yes">Remove text formatting</property>
Rework action names groups across the client Introduce a new standard edit action group "edt" for editing actions such as copy and undo, separate from the "win" window action group, so that editing actions can be scoped to specific widgets and overridden by children. Add new Action namespace with sub-namespaces for the app, win and edt namespaces and move consts from GearyApplication there. Update call sites and UI files, use consistent approach to setting up action groups across all classes that use them.
2019-11-07 11:47:41 +11:00
<property name="action_name">edt.remove-format</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="always_show_image">True</property>
<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="GtkImage" id="remove_format_image">
Fix composer UI brokenness when compiled under vala 0.36. Don't rely ComposerState::state notify and property bindings firing when the value hasn't actually changed to update the composer's UI. This is works around Vala Bug 631267 landing. * src/client/composer/composer-headerbar.vala (ComposerHeaderbar): Add signal and methods to be called explicity on state changes, rather than relying on being notified of ComposerWidget::state changing. * src/client/composer/composer-widget.vala (ComposerWidget): Hook up new ComposerHeaderbar signal and method. Remove notify and property bindings on ::state property, move related code to new ::update_composer_view method and call that as needed. Remove overridden ::show_all, because the UI state should now always be consistent with ::state. Clean up various methods. * src/client/composer/email-entry.vala (EmailEntry::EmailEntry): Make widget visible by default, since we are no longer calling ComposerWidget::show_all(). * src/client/application/geary-controller.vala: Don't call show all on new composers, they now manage their visibility properly. * ui/composer-headerbar.ui: Make toolbar icons visible by default. * ui/composer-widget.ui: Make toolbar icons visible by default, set Send button icon here rather than in the class.
2017-03-04 13:42:53 +11:00
<property name="visible">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="can_focus">False</property>
<property name="pixel_size">16</property>
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="icon_name">format-text-remove-symbolic</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
</object>
</child>
</object>
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
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
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="position">5</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
</packing>
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>
<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="GtkButton" id="select_dictionary_button">
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>
Use click-to-focus prop on toolbar buttons rather than other workarounds. * src/client/application/geary-controller.vala (GearyController::archive_or_delete_selection_async): Don't modify the focus after archiving/trashing/deleting. * src/client/components/pill-toolbar.vala, ui/composer-headerbar.ui, ui/composer-widget.ui: Ensure all toolbar buttons are focusable but have focus-on-click disabled.
2016-10-20 16:58:48 +11:00
<property name="can_focus">True</property>
<property name="focus_on_click">False</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="receives_default">False</property>
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="tooltip_text" translatable="yes">Select spell checking languages</property>
<property name="action_name">win.select-dictionary</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="always_show_image">True</property>
<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="GtkImage" id="select_dictionary_image">
Fix composer UI brokenness when compiled under vala 0.36. Don't rely ComposerState::state notify and property bindings firing when the value hasn't actually changed to update the composer's UI. This is works around Vala Bug 631267 landing. * src/client/composer/composer-headerbar.vala (ComposerHeaderbar): Add signal and methods to be called explicity on state changes, rather than relying on being notified of ComposerWidget::state changing. * src/client/composer/composer-widget.vala (ComposerWidget): Hook up new ComposerHeaderbar signal and method. Remove notify and property bindings on ::state property, move related code to new ::update_composer_view method and call that as needed. Remove overridden ::show_all, because the UI state should now always be consistent with ::state. Clean up various methods. * src/client/composer/email-entry.vala (EmailEntry::EmailEntry): Make widget visible by default, since we are no longer calling ComposerWidget::show_all(). * src/client/application/geary-controller.vala: Don't call show all on new composers, they now manage their visibility properly. * ui/composer-headerbar.ui: Make toolbar icons visible by default. * ui/composer-widget.ui: Make toolbar icons visible by default, set Send button icon here rather than in the class.
2017-03-04 13:42:53 +11:00
<property name="visible">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="can_focus">False</property>
<property name="pixel_size">16</property>
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="icon_name">accessories-dictionary-symbolic</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
</object>
</child>
</object>
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
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
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="position">6</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
</packing>
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>
<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="GtkMenuButton" id="menu_button">
Fix composer UI brokenness when compiled under vala 0.36. Don't rely ComposerState::state notify and property bindings firing when the value hasn't actually changed to update the composer's UI. This is works around Vala Bug 631267 landing. * src/client/composer/composer-headerbar.vala (ComposerHeaderbar): Add signal and methods to be called explicity on state changes, rather than relying on being notified of ComposerWidget::state changing. * src/client/composer/composer-widget.vala (ComposerWidget): Hook up new ComposerHeaderbar signal and method. Remove notify and property bindings on ::state property, move related code to new ::update_composer_view method and call that as needed. Remove overridden ::show_all, because the UI state should now always be consistent with ::state. Clean up various methods. * src/client/composer/email-entry.vala (EmailEntry::EmailEntry): Make widget visible by default, since we are no longer calling ComposerWidget::show_all(). * src/client/application/geary-controller.vala: Don't call show all on new composers, they now manage their visibility properly. * ui/composer-headerbar.ui: Make toolbar icons visible by default. * ui/composer-widget.ui: Make toolbar icons visible by default, set Send button icon here rather than in the class.
2017-03-04 13:42:53 +11:00
<property name="visible">True</property>
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="can_focus">False</property>
Use click-to-focus prop on toolbar buttons rather than other workarounds. * src/client/application/geary-controller.vala (GearyController::archive_or_delete_selection_async): Don't modify the focus after archiving/trashing/deleting. * src/client/components/pill-toolbar.vala, ui/composer-headerbar.ui, ui/composer-widget.ui: Ensure all toolbar buttons are focusable but have focus-on-click disabled.
2016-10-20 16:58:48 +11:00
<property name="focus_on_click">False</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="receives_default">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
<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
<placeholder/>
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>
Add Insert Image button, action and hander to composer. Bug 712995. * src/client/composer/composer-widget.vala (ComposerWidget): Add action and callback that simply does a normal attachment for now. * ui/composer-widget.ui: Add insert image button to the composer toobar.
2016-09-28 22:47:40 +10:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
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="pack_type">end</property>
<property name="position">7</property>
Add Insert Image button, action and hander to composer. Bug 712995. * src/client/composer/composer-widget.vala (ComposerWidget): Add action and callback that simply does a normal attachment for now. * ui/composer-widget.ui: Add insert image button to the composer toobar.
2016-09-28 22:47:40 +10:00
</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="GtkLabel" id="info_label">
Fix composer UI brokenness when compiled under vala 0.36. Don't rely ComposerState::state notify and property bindings firing when the value hasn't actually changed to update the composer's UI. This is works around Vala Bug 631267 landing. * src/client/composer/composer-headerbar.vala (ComposerHeaderbar): Add signal and methods to be called explicity on state changes, rather than relying on being notified of ComposerWidget::state changing. * src/client/composer/composer-widget.vala (ComposerWidget): Hook up new ComposerHeaderbar signal and method. Remove notify and property bindings on ::state property, move related code to new ::update_composer_view method and call that as needed. Remove overridden ::show_all, because the UI state should now always be consistent with ::state. Clean up various methods. * src/client/composer/email-entry.vala (EmailEntry::EmailEntry): Make widget visible by default, since we are no longer calling ComposerWidget::show_all(). * src/client/application/geary-controller.vala: Don't call show all on new composers, they now manage their visibility properly. * ui/composer-headerbar.ui: Make toolbar icons visible by default. * ui/composer-widget.ui: Make toolbar icons visible by default, set Send button icon here rather than in the class.
2017-03-04 13:42:53 +11:00
<property name="visible">True</property>
Add Insert Image button, action and hander to composer. Bug 712995. * src/client/composer/composer-widget.vala (ComposerWidget): Add action and callback that simply does a normal attachment for now. * ui/composer-widget.ui: Add insert image button to the composer toobar.
2016-09-28 22:47:40 +10:00
<property name="can_focus">True</property>
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="ellipsize">end</property>
<property name="width_chars">6</property>
<property name="xalign">0</property>
<style>
<class name="dim-label"/>
</style>
Add Insert Image button, action and hander to composer. Bug 712995. * src/client/composer/composer-widget.vala (ComposerWidget): Add action and callback that simply does a normal attachment for now. * ui/composer-widget.ui: Add insert image button to the composer toobar.
2016-09-28 22:47:40 +10:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
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="pack_type">end</property>
<property name="position">8</property>
Add Insert Image button, action and hander to composer. Bug 712995. * src/client/composer/composer-widget.vala (ComposerWidget): Add action and callback that simply does a normal attachment for now. * ui/composer-widget.ui: Add insert image button to the composer toobar.
2016-09-28 22:47:40 +10:00
</packing>
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>
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
<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="left_attach">0</property>
<property name="top_attach">0</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
</packing>
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>
<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="GtkFrame">
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>
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="label_xalign">0</property>
<property name="shadow_type">in</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
<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="GtkBox" id="message_area">
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="visible">True</property>
<property name="can_focus">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
<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="GtkOverlay" id="message_overlay">
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>
Remove composer's scrolled window since WebView now scrolls internally. We can't easily wrap ComposerWebView in a GtkScrolledWindow, since we don't any notifications that the cursor has moved offscreen and hence the view needs to be scrolled, so let the view do its own scrolling. * ui/composer-widget.ui: Replace editor_scrolled with editor_container, update uses.
2017-01-26 22:03:29 +11:00
<property name="can_focus">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
<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="body_container">
<property name="height_request">250</property>
<property name="visible">True</property>
<property name="can_focus">False</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>
</object>
<packing>
<property name="index">-1</property>
</packing>
Replace composer keyboard shortcut with standard widget action scoping Rather than adding and removing shortcuts when the composer's web view gains and loses focus to avoid invoking main window shortcuts, just rely on standard GTK action scoping rules. This fixes editing shortcuts like Ctrl+I breaking when clicking on toolbar buttons, a crasher because the composer left the undo button enabled after it was closed, and allows Escape to close the composer from anywherre. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=774651, https://bugzilla.gnome.org/show_bug.cgi?id=785187, and https://bugzilla.gnome.org/show_bug.cgi?id=741741
2019-02-13 22:19:44 +11:00
</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
<child type="overlay">
<object class="GtkLabel" id="message_overlay_label">
<property name="can_focus">False</property>
<property name="no_show_all">True</property>
<property name="halign">start</property>
<property name="valign">end</property>
<property name="ellipsize">middle</property>
<style>
<class name="geary-overlay"/>
</style>
</object>
Replace composer keyboard shortcut with standard widget action scoping Rather than adding and removing shortcuts when the composer's web view gains and loses focus to avoid invoking main window shortcuts, just rely on standard GTK action scoping rules. This fixes editing shortcuts like Ctrl+I breaking when clicking on toolbar buttons, a crasher because the composer left the undo button enabled after it was closed, and allows Escape to close the composer from anywherre. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=774651, https://bugzilla.gnome.org/show_bug.cgi?id=785187, and https://bugzilla.gnome.org/show_bug.cgi?id=741741
2019-02-13 22:19:44 +11:00
</child>
Add feedback via HUD progress pulse on slow inline image paste
2019-12-06 11:17:12 +01:00
<child type="overlay">
<object class="GtkProgressBar" id="background_progress">
<property name="can_focus">False</property>
<property name="valign">start</property>
<style>
<class name="osd"/>
<class name="top"/>
</style>
</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>
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
<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">True</property>
<property name="fill">True</property>
<property name="position">0</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
</packing>
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>
</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
<style>
<class name="geary-composer-body"/>
</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>
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
<packing>
<property name="left_attach">0</property>
<property name="top_attach">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>
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>
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="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>
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="margin_left">6</property>
<property name="margin_right">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
<property name="margin_start">6</property>
<property name="margin_end">6</property>
<property name="margin_top">6</property>
<property name="margin_bottom">6</property>
<property name="orientation">vertical</property>
<property name="spacing">6</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
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="position">4</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>
</interface>
Reference in a new issue Copy permalink