procyberian/gimp
2
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/gimp.git synced 2025-07-03 17:33:25 +00:00
Code Issues 1 Projects 1 Releases Packages Wiki Activity Actions
gimp/menus/image-menu.ui.in.in

921 lines
52 KiB
Text
Raw Normal View History

app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<?xml version="1.0" encoding="utf-8"?>
menus: add a dockable-menu with the new GtkBuilder format. The dialogs-menuitems is shared between dockable-menu and image-menu, just as it was with the old format. For this, we use XSL transformation with XInclude, then drop the namespace (because GTK doesn't like the unknown namespace being defined and crash immediately otherwise).
2023-02-22 21:29:08 +01:00
<interface xmlns:xi="http://www.w3.org/2001/XInclude">
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<menu id="/image-menubar">
<!-- File menu -->
<submenu>
<attribute name="label" translatable="yes" context="file-action">_File</attribute>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Open</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.image-new</attribute></item>
<submenu>
<attribute name="label" translatable="yes" context="file-action">Crea_te</attribute>
<item><attribute name="action">app.edit-paste-as-new-image</attribute></item>
</submenu>
<item><attribute name="action">app.file-open</attribute></item>
<item><attribute name="action">app.file-open-as-layers</attribute></item>
<item><attribute name="action">app.file-open-location</attribute></item>
<submenu>
<attribute name="label" translatable="yes" context="file-action">Open _Recent</attribute>
<section>
app, menus: remove all placeholder code. This is now fully replaced by the new section name code.
2023-07-13 16:53:11 +02:00
<attribute name="section-name" translatable="no">Files</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
</section>
<item><attribute name="action">app.dialogs-document-history</attribute></item>
</submenu>
<submenu>
<attribute name="label" translatable="yes">_Debug</attribute>
<item><attribute name="action">app.debug-gtk-inspector</attribute></item>
<section>
<item><attribute name="action">app.debug-mem-profile</attribute></item>
<item><attribute name="action">app.debug-benchmark-projection</attribute></item>
<item><attribute name="action">app.debug-show-image-graph</attribute></item>
</section>
<section>
<item><attribute name="action">app.debug-dump-keyboard-shortcuts</attribute></item>
<item><attribute name="action">app.debug-dump-attached-data</attribute></item>
</section>
</submenu>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Save</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.file-save</attribute></item>
<item><attribute name="action">app.file-save-as</attribute></item>
<item><attribute name="action">app.file-save-a-copy</attribute></item>
<item><attribute name="action">app.file-revert</attribute></item>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Export</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.file-overwrite</attribute></item>
<item><attribute name="action">app.file-export</attribute></item>
<item><attribute name="action">app.file-export-as</attribute></item>
<item><attribute name="action">app.file-create-template</attribute></item>
</section>
menus, plug-ins: now place various plug-ins in the right menu sections. This removes a bunch of inconsistencies we had from the before-2.99.16 version because new items from plug-ins were all added at the bottom of their respective submenu.
2023-07-13 15:34:40 +02:00
<section>
menus: make all section names non-translatable. I'm not sure what's the default for random string attribute, but better be explicit anyway. I think this way, we make sure that gettext won't try and translate these.
2023-07-13 16:57:23 +02:00
<attribute name="section-name" translatable="no">Send</attribute>
menus, plug-ins: now place various plug-ins in the right menu sections. This removes a bunch of inconsistencies we had from the before-2.99.16 version because new items from plug-ins were all added at the bottom of their respective submenu.
2023-07-13 15:34:40 +02:00
</section>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Info</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.file-copy-location</attribute></item>
<item><attribute name="action">app.file-show-in-file-manager</attribute></item>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Close</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.view-close</attribute></item>
<item><attribute name="action">app.file-close-all</attribute></item>
menus: hide some menu items on macOS. File/Quit, Edit/Preferences|Input Devices|Keyboard Shortcuts should not be in the main menu bar on macOS because they are already in the "app menu". See #9322.
2023-07-13 23:41:18 +02:00
<item>
<attribute name="hidden-when">macos-menubar</attribute>
<attribute name="action">app.file-quit</attribute>
</item>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
</section>
</submenu>
<!-- Edit menu -->
<submenu>
<attribute name="label" translatable="yes" context="edit-action">_Edit</attribute>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Undo</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.edit-undo</attribute></item>
<item><attribute name="action">app.edit-redo</attribute></item>
<item><attribute name="action">app.dialogs-undo-history</attribute></item>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<!-- TODO: In 2.10, we actually had 3 sections "Cut", "Copy" and "Paste" yet don't want delimiters. -->
<attribute name="section-name" translatable="no">Paste</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.edit-cut</attribute></item>
<item><attribute name="action">app.edit-copy</attribute></item>
<item><attribute name="action">app.edit-copy-visible</attribute></item>
<item><attribute name="action">app.edit-paste</attribute></item>
<item><attribute name="action">app.edit-paste-in-place</attribute></item>
<submenu>
<attribute name="label" translatable="yes" context="edit-action">Paste _as</attribute>
Issue #10153: introducing new floating data actions. Though we mostly removed floating layers/masks (formerly floating selections) in many interactions, at least for default behaviors for basic pastes, there are still advanced usage attached to this concept and some advanced users are willing to have easier access to such items. For this reason, this commit: - adds edit-paste-float and edit-paste-float-in-place for pasting the contents of the clipboard as floating data with default positionning algorithm or in-place respectively; - renames select-float to select-cut-float which does a cut and paste as float in one action; - adds select-copy-float which does a copy and paste as float in one action; - reorganize a bit the `Edit > Paste as` submenu with sections for the floating data variants; - add a "Float" submenu in "Select" root menu, containing the 2 variant actions select-cut-float and select-copy-float.
2023-11-11 16:33:57 +01:00
<section>
<item><attribute name="action">app.edit-paste-merged</attribute></item>
<item><attribute name="action">app.edit-paste-merged-in-place</attribute></item>
</section>
<section>
<item><attribute name="action">app.edit-paste-float</attribute></item>
<item><attribute name="action">app.edit-paste-float-in-place</attribute></item>
<item><attribute name="action">app.edit-paste-into</attribute></item>
<item><attribute name="action">app.edit-paste-into-in-place</attribute></item>
</section>
Issue #9349: removing 2 duplicate "*-short" actions. "edit-paste-as-new-image-short" and "vectors-selection-to-vectors-short" were just duplicate of the action named the same, except for the "-short" suffix, and the only point was to have different labels. Not though that this time, it was not enough to conclude that the action in a menu shoud have the short variant. These were both used differently depending on the menu. Instead I added the concept of "label-variant" attribute in .ui menu files. When the "long" variant is set, then we simply use the longer label. There is still one more "-short" action: "tools-by-color-select-short", but I am a still unsure how to handle this one.
2023-04-14 18:54:16 +02:00
<item><attribute name="action">app.edit-paste-as-new-image</attribute><attribute name="label-variant">long</attribute></item>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="edit-action">_Buffer</attribute>
<item><attribute name="action">app.edit-named-cut</attribute></item>
<item><attribute name="action">app.edit-named-copy</attribute></item>
<item><attribute name="action">app.edit-named-copy-visible</attribute></item>
<item><attribute name="action">app.edit-named-paste</attribute></item>
</submenu>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<!-- TODO: In 2.10, we actually had 3 sections "Clear", "Fill" and "Stroke" yet don't want delimiters. -->
<attribute name="section-name" translatable="no">Stroke</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.edit-clear</attribute></item>
<item><attribute name="action">app.edit-fill-fg</attribute></item>
<item><attribute name="action">app.edit-fill-bg</attribute></item>
<item><attribute name="action">app.edit-fill-pattern</attribute></item>
<item><attribute name="action">app.select-fill</attribute></item>
app, menus: rename all "vectors-" actions to "paths-". Though these are not as user-facing as other strings, the action names still are somewhat user-facing. Let's rename them consistently with the GUI and the API. This commit also handles user config migration so that custom shortcuts are not lost.
2024-08-04 20:11:53 +02:00
<item><attribute name="action">app.paths-fill</attribute></item>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.select-stroke</attribute></item>
app, menus: rename all "vectors-" actions to "paths-". Though these are not as user-facing as other strings, the action names still are somewhat user-facing. Let's rename them consistently with the GUI and the API. This commit also handles user config migration so that custom shortcuts are not lost.
2024-08-04 20:11:53 +02:00
<item><attribute name="action">app.paths-stroke</attribute></item>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
</section>
<section>
menus: make all section names non-translatable. I'm not sure what's the default for random string attribute, but better be explicit anyway. I think this way, we make sure that gettext won't try and translate these.
2023-07-13 16:57:23 +02:00
<attribute name="section-name" translatable="no">Preferences</attribute>
menus: hide some menu items on macOS. File/Quit, Edit/Preferences|Input Devices|Keyboard Shortcuts should not be in the main menu bar on macOS because they are already in the "app menu". See #9322.
2023-07-13 23:41:18 +02:00
<item>
<attribute name="hidden-when">macos-menubar</attribute>
<attribute name="action">app.dialogs-preferences</attribute>
</item>
Issue #10776: Hide "Edit > Manage Extensions" for the release. The extension format's official release is pushed for after GIMP 3 release. Let's not leave this dialog around as it would confuse people.
2024-03-01 00:43:26 +01:00
<!-- TODO: re-enable this when extensions are publicly released.
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.dialogs-extensions</attribute></item>
Issue #10776: Hide "Edit > Manage Extensions" for the release. The extension format's official release is pushed for after GIMP 3 release. Let's not leave this dialog around as it would confuse people.
2024-03-01 00:43:26 +01:00
-->
menus: hide some menu items on macOS. File/Quit, Edit/Preferences|Input Devices|Keyboard Shortcuts should not be in the main menu bar on macOS because they are already in the "app menu". See #9322.
2023-07-13 23:41:18 +02:00
<item>
<attribute name="hidden-when">macos-menubar</attribute>
<attribute name="action">app.dialogs-input-devices</attribute>
</item>
<item>
<attribute name="hidden-when">macos-menubar</attribute>
<attribute name="action">app.dialogs-keyboard-shortcuts</attribute>
</item>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.dialogs-module-dialog</attribute></item>
</section>
</submenu>
<!-- Select menu -->
<submenu>
<attribute name="label" translatable="yes" context="select-action">_Select</attribute>
<section>
<item><attribute name="action">app.select-all</attribute></item>
<item><attribute name="action">app.select-none</attribute></item>
<item><attribute name="action">app.select-invert</attribute></item>
Issue #10153: introducing new floating data actions. Though we mostly removed floating layers/masks (formerly floating selections) in many interactions, at least for default behaviors for basic pastes, there are still advanced usage attached to this concept and some advanced users are willing to have easier access to such items. For this reason, this commit: - adds edit-paste-float and edit-paste-float-in-place for pasting the contents of the clipboard as floating data with default positionning algorithm or in-place respectively; - renames select-float to select-cut-float which does a cut and paste as float in one action; - adds select-copy-float which does a copy and paste as float in one action; - reorganize a bit the `Edit > Paste as` submenu with sections for the floating data variants; - add a "Float" submenu in "Select" root menu, containing the 2 variant actions select-cut-float and select-copy-float.
2023-11-11 16:33:57 +01:00
<submenu>
<attribute name="label" translatable="yes" context="view-action">_Float</attribute>
<item><attribute name="action">app.select-cut-float</attribute></item>
<item><attribute name="action">app.select-copy-float</attribute></item>
</submenu>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.tools-by-color-select-short</attribute></item>
app, menus: rename all "vectors-" actions to "paths-". Though these are not as user-facing as other strings, the action names still are somewhat user-facing. Let's rename them consistently with the GUI and the API. This commit also handles user config migration so that custom shortcuts are not lost.
2024-08-04 20:11:53 +02:00
<item><attribute name="action">app.paths-selection-from-paths</attribute></item>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.dialogs-selection-editor</attribute></item>
menus, plug-ins: now place various plug-ins in the right menu sections. This removes a bunch of inconsistencies we had from the before-2.99.16 version because new items from plug-ins were all added at the bottom of their respective submenu.
2023-07-13 15:34:40 +02:00
</section>
<section>
menus: make all section names non-translatable. I'm not sure what's the default for random string attribute, but better be explicit anyway. I think this way, we make sure that gettext won't try and translate these.
2023-07-13 16:57:23 +02:00
<attribute name="section-name" translatable="no">Modify</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.select-feather</attribute></item>
<item><attribute name="action">app.select-sharpen</attribute></item>
<item><attribute name="action">app.select-shrink</attribute></item>
<item><attribute name="action">app.select-grow</attribute></item>
<item><attribute name="action">app.select-border</attribute></item>
<item><attribute name="action">app.select-flood</attribute></item>
</section>
<section>
<item><attribute name="action">app.quick-mask-toggle</attribute></item>
<item><attribute name="action">app.select-save</attribute></item>
app, menus: rename all "vectors-" actions to "paths-". Though these are not as user-facing as other strings, the action names still are somewhat user-facing. Let's rename them consistently with the GUI and the API. This commit also handles user config migration so that custom shortcuts are not lost.
2024-08-04 20:11:53 +02:00
<item><attribute name="action">app.paths-selection-to-path</attribute></item>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
</section>
</submenu>
<!-- View menu -->
<submenu>
<attribute name="label" translatable="yes" context="view-action">_View</attribute>
<item><attribute name="action">app.view-new</attribute></item>
<item><attribute name="action">app.view-show-all</attribute></item>
<item><attribute name="action">app.view-dot-for-dot</attribute></item>
<submenu>
<attribute name="label" translatable="yes" context="view-action">_Zoom</attribute>
<section>
<item><attribute name="action">app.view-zoom-revert</attribute></item>
<item><attribute name="action">app.view-zoom-out</attribute></item>
<item><attribute name="action">app.view-zoom-in</attribute></item>
<item><attribute name="action">app.view-zoom-fit-in</attribute></item>
<item><attribute name="action">app.view-zoom-fill</attribute></item>
<item><attribute name="action">app.view-zoom-selection</attribute></item>
</section>
<section>
<item><attribute name="action">app.view-zoom-16-1</attribute></item>
<item><attribute name="action">app.view-zoom-8-1</attribute></item>
<item><attribute name="action">app.view-zoom-4-1</attribute></item>
<item><attribute name="action">app.view-zoom-2-1</attribute></item>
<item><attribute name="action">app.view-zoom-1-1</attribute></item>
<item><attribute name="action">app.view-zoom-1-2</attribute></item>
<item><attribute name="action">app.view-zoom-1-4</attribute></item>
<item><attribute name="action">app.view-zoom-1-8</attribute></item>
<item><attribute name="action">app.view-zoom-1-16</attribute></item>
</section>
<section>
<item><attribute name="action">app.view-zoom-other</attribute></item>
</section>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="view-action">_Flip &amp; Rotate</attribute>
<section>
<item><attribute name="action">app.view-reset</attribute></item>
</section>
<section>
<item><attribute name="action">app.view-flip-horizontally</attribute></item>
<item><attribute name="action">app.view-flip-vertically</attribute></item>
</section>
<section>
<item><attribute name="action">app.view-rotate-15</attribute></item>
<item><attribute name="action">app.view-rotate-345</attribute></item>
<item><attribute name="action">app.view-rotate-90</attribute></item>
<item><attribute name="action">app.view-rotate-270</attribute></item>
<item><attribute name="action">app.view-rotate-180</attribute></item>
</section>
<section>
<item><attribute name="action">app.view-rotate-other</attribute></item>
</section>
</submenu>
<item><attribute name="action">app.view-scroll-center</attribute></item>
<section>
<item><attribute name="action">app.view-shrink-wrap</attribute></item>
<item><attribute name="action">app.view-fullscreen</attribute></item>
<submenu>
<attribute name="label" translatable="yes" context="view-action">Move to Screen</attribute>
<item><attribute name="action">app.view-open-display</attribute></item>
<!-- TODO: screen list. -->
</submenu>
</section>
<section>
<item><attribute name="action">app.view-navigation-window</attribute></item>
<item><attribute name="action">app.view-display-filters</attribute></item>
<submenu>
<attribute name="label" translatable="yes" context="view-action">_Color Management</attribute>
<section>
<item><attribute name="action">app.view-color-management-enable</attribute></item>
<item><attribute name="action">app.view-color-management-softproof</attribute></item>
</section>
<section>
<submenu>
<attribute name="label" translatable="yes" context="view-action">Display _Rendering Intent</attribute>
<item><attribute name="action">app.view-display-intent-perceptual</attribute></item>
<item><attribute name="action">app.view-display-intent-relative-colorimetric</attribute></item>
<item><attribute name="action">app.view-display-intent-saturation</attribute></item>
<item><attribute name="action">app.view-display-intent-absolute-colorimetric</attribute></item>
</submenu>
<item><attribute name="action">app.view-display-black-point-compensation</attribute></item>
</section>
<section>
<item><attribute name="action">app.view-softproof-gamut-check</attribute></item>
<item><attribute name="action">app.view-color-management-reset</attribute></item>
</section>
</submenu>
</section>
<section>
<item><attribute name="action">app.view-show-selection</attribute></item>
<item><attribute name="action">app.view-show-layer-boundary</attribute></item>
<item><attribute name="action">app.view-show-canvas-boundary</attribute></item>
<item><attribute name="action">app.view-show-guides</attribute></item>
<item><attribute name="action">app.view-show-grid</attribute></item>
<item><attribute name="action">app.view-show-sample-points</attribute></item>
</section>
<section>
<item><attribute name="action">app.view-snap-to-guides</attribute></item>
<item><attribute name="action">app.view-snap-to-grid</attribute></item>
<item><attribute name="action">app.view-snap-to-canvas</attribute></item>
<item><attribute name="action">app.view-snap-to-vectors</attribute></item>
Adding initial support for snapping layers/path_points by layers bounding boxes
2023-03-08 19:08:55 +03:00
<item><attribute name="action">app.view-snap-to-bbox</attribute></item>
<item><attribute name="action">app.view-snap-to-equidistance</attribute></item>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
</section>
<section>
<submenu>
menus: Use Header Capitalization in image-menu.ui Follow Header Capitalization for The "Padding Color" string. More information: https://developer.gnome.org/hig/guidelines/writing-style.html
2023-07-18 19:08:28 +03:00
<attribute name="label" translatable="yes" context="view-action">_Padding Color</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<section>
<item><attribute name="action">app.view-padding-color-theme</attribute></item>
<item><attribute name="action">app.view-padding-color-light-check</attribute></item>
<item><attribute name="action">app.view-padding-color-dark-check</attribute></item>
<item><attribute name="action">app.view-padding-color-custom</attribute></item>
</section>
<section>
<item><attribute name="action">app.view-padding-color-in-show-all</attribute></item>
</section>
<section>
<item><attribute name="action">app.view-padding-color-prefs</attribute></item>
</section>
</submenu>
<item><attribute name="action">app.view-show-menubar</attribute></item>
<item><attribute name="action">app.view-show-rulers</attribute></item>
<item><attribute name="action">app.view-show-scrollbars</attribute></item>
<item><attribute name="action">app.view-show-statusbar</attribute></item>
</section>
</submenu>
<!-- Image menu -->
<submenu>
<attribute name="label" translatable="yes" context="image-action">_Image</attribute>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">New</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.image-duplicate</attribute></item>
</section>
<section>
<submenu>
<attribute name="label" translatable="yes" context="image-action">_Mode</attribute>
<item><attribute name="action">app.image-convert-rgb</attribute></item>
<item><attribute name="action">app.image-convert-grayscale</attribute></item>
<item><attribute name="action">app.image-convert-indexed</attribute></item>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="image-action">_Encoding</attribute>
<section>
<item><attribute name="action">app.image-convert-u8</attribute></item>
<item><attribute name="action">app.image-convert-u16</attribute></item>
<item><attribute name="action">app.image-convert-u32</attribute></item>
<item><attribute name="action">app.image-convert-half</attribute></item>
<item><attribute name="action">app.image-convert-float</attribute></item>
<item><attribute name="action">app.image-convert-double</attribute></item>
</section>
<section>
<item><attribute name="action">app.image-convert-linear</attribute></item>
<item><attribute name="action">app.image-convert-non-linear</attribute></item>
<item><attribute name="action">app.image-convert-perceptual</attribute></item>
</section>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="image-action">Color Ma_nagement</attribute>
<section>
<item><attribute name="action">app.image-color-profile-use-srgb</attribute></item>
</section>
<section>
<item><attribute name="action">app.image-color-profile-assign</attribute></item>
<item><attribute name="action">app.image-color-profile-convert</attribute></item>
<item><attribute name="action">app.image-color-profile-discard</attribute></item>
</section>
<section>
<item><attribute name="action">app.image-color-profile-save</attribute></item>
</section>
<section>
<item><attribute name="action">app.image-softproof-profile</attribute></item>
</section>
<section>
<submenu>
<attribute name="label" translatable="yes" context="image-action">Soft-Proofing Re_ndering Intent</attribute>
<item><attribute name="action">app.image-softproof-intent-perceptual</attribute></item>
<item><attribute name="action">app.image-softproof-intent-relative-colorimetric</attribute></item>
<item><attribute name="action">app.image-softproof-intent-saturation</attribute></item>
<item><attribute name="action">app.image-softproof-intent-absolute-colorimetric</attribute></item>
</submenu>
<item><attribute name="action">app.image-softproof-black-point-compensation</attribute></item>
</section>
</submenu>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<!-- XXX This section should actually start after the submenu and there should be a "Resize" section first but we want to avoid the separators. -->
<attribute name="section-name" translatable="no">Scale</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<submenu>
<attribute name="label" translatable="yes" context="image-action">_Transform</attribute>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Flip</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.image-flip-horizontal</attribute></item>
<item><attribute name="action">app.image-flip-vertical</attribute></item>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Rotate</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.image-rotate-90</attribute></item>
<item><attribute name="action">app.image-rotate-270</attribute></item>
<item><attribute name="action">app.image-rotate-180</attribute></item>
<item><attribute name="action">app.tools-rotate-image-arbitrary</attribute></item>
</section>
</submenu>
<item><attribute name="action">app.image-resize</attribute></item>
<item><attribute name="action">app.image-resize-to-layers</attribute></item>
<item><attribute name="action">app.image-resize-to-selection</attribute></item>
<item><attribute name="action">app.image-print-size</attribute></item>
<item><attribute name="action">app.image-scale</attribute></item>
</section>
<section>
menus: make all section names non-translatable. I'm not sure what's the default for random string attribute, but better be explicit anyway. I think this way, we make sure that gettext won't try and translate these.
2023-07-13 16:57:23 +02:00
<attribute name="section-name" translatable="no">Crop</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.image-crop-to-selection</attribute></item>
<item><attribute name="action">app.image-crop-to-content</attribute></item>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<!-- TODO: missing "Structure" section. -->
menus: make all section names non-translatable. I'm not sure what's the default for random string attribute, but better be explicit anyway. I think this way, we make sure that gettext won't try and translate these.
2023-07-13 16:57:23 +02:00
<attribute name="section-name" translatable="no">Arrange</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.image-merge-layers</attribute></item>
<item><attribute name="action">app.image-flatten</attribute></item>
</section>
<section>
<submenu>
<attribute name="label" translatable="yes" context="image-action">_Guides</attribute>
</submenu>
<item><attribute name="action">app.image-configure-grid</attribute></item>
</section>
<section>
menus: make all section names non-translatable. I'm not sure what's the default for random string attribute, but better be explicit anyway. I think this way, we make sure that gettext won't try and translate these.
2023-07-13 16:57:23 +02:00
<attribute name="section-name" translatable="no">Properties</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.image-properties</attribute></item>
menus, plug-ins: now place various plug-ins in the right menu sections. This removes a bunch of inconsistencies we had from the before-2.99.16 version because new items from plug-ins were all added at the bottom of their respective submenu.
2023-07-13 15:34:40 +02:00
<submenu>
<attribute name="label" translatable="yes" context="image-action">Meta_data</attribute>
</submenu>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
</section>
</submenu>
<!-- Layer menu -->
<submenu>
<attribute name="label" translatable="yes" context="layers-action">_Layer</attribute>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<!-- TODO: missing "New" section. -->
<attribute name="section-name" translatable="no">Structure</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.layers-new</attribute></item>
<item><attribute name="action">app.layers-new-from-visible</attribute></item>
<item><attribute name="action">app.layers-new-group</attribute></item>
<item><attribute name="action">app.layers-duplicate</attribute></item>
<item><attribute name="action">app.layers-anchor</attribute></item>
<item><attribute name="action">app.layers-merge-down</attribute></item>
<item><attribute name="action">app.layers-merge-group</attribute></item>
<item><attribute name="action">app.layers-delete</attribute></item>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Text</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.layers-text-discard</attribute></item>
<item><attribute name="action">app.layers-text-to-vectors</attribute></item>
<item><attribute name="action">app.layers-text-along-vectors</attribute></item>
</section>
<section>
<submenu>
<attribute name="label" translatable="yes" context="layers-action">Stac_k</attribute>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Select</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.layers-select-previous</attribute></item>
<item><attribute name="action">app.layers-select-next</attribute></item>
<item><attribute name="action">app.layers-select-top</attribute></item>
<item><attribute name="action">app.layers-select-bottom</attribute></item>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Position</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.layers-raise</attribute></item>
<item><attribute name="action">app.layers-lower</attribute></item>
<item><attribute name="action">app.layers-raise-to-top</attribute></item>
<item><attribute name="action">app.layers-lower-to-bottom</attribute></item>
</section>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="layers-action">_Mask</attribute>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Modify</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.layers-mask-add</attribute></item>
<item><attribute name="action">app.layers-mask-apply</attribute></item>
<item><attribute name="action">app.layers-mask-delete</attribute></item>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Properties</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.layers-mask-show</attribute></item>
<item><attribute name="action">app.layers-mask-edit</attribute></item>
<item><attribute name="action">app.layers-mask-disable</attribute></item>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Selection</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.layers-mask-selection-replace</attribute></item>
<item><attribute name="action">app.layers-mask-selection-add</attribute></item>
<item><attribute name="action">app.layers-mask-selection-subtract</attribute></item>
<item><attribute name="action">app.layers-mask-selection-intersect</attribute></item>
</section>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="layers-action">Tr_ansparency</attribute>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Modify</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.layers-alpha-add</attribute></item>
<item><attribute name="action">app.layers-alpha-remove</attribute></item>
<item><attribute name="action">app.filters-color-to-alpha</attribute></item>
<item><attribute name="action">app.filters-semi-flatten</attribute></item>
<item><attribute name="action">app.filters-threshold-alpha</attribute></item>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Selection</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.layers-alpha-selection-replace</attribute></item>
<item><attribute name="action">app.layers-alpha-selection-add</attribute></item>
<item><attribute name="action">app.layers-alpha-selection-subtract</attribute></item>
<item><attribute name="action">app.layers-alpha-selection-intersect</attribute></item>
</section>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="layers-action">_Transform</attribute>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Flip</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.drawable-flip-horizontal</attribute></item>
<item><attribute name="action">app.drawable-flip-vertical</attribute></item>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Rotate</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.drawable-rotate-90</attribute></item>
<item><attribute name="action">app.drawable-rotate-270</attribute></item>
<item><attribute name="action">app.drawable-rotate-180</attribute></item>
<item><attribute name="action">app.tools-rotate-arbitrary</attribute></item>
</section>
<item><attribute name="action">app.filters-offset</attribute></item>
</submenu>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<!-- TODO: missing "Resize" and "Scale" sections. -->
<attribute name="section-name" translatable="no">Crop</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.layers-resize</attribute></item>
<item><attribute name="action">app.layers-resize-to-image</attribute></item>
<item><attribute name="action">app.layers-scale</attribute></item>
<item><attribute name="action">app.layers-crop-to-selection</attribute></item>
<item><attribute name="action">app.layers-crop-to-content</attribute></item>
</section>
</submenu>
<!-- Colors Menu -->
<submenu>
<attribute name="label" translatable="yes" context="image-action">_Colors</attribute>
<section>
<item><attribute name="action">app.filters-color-balance</attribute></item>
<item><attribute name="action">app.filters-color-temperature</attribute></item>
<item><attribute name="action">app.filters-hue-chroma</attribute></item>
<item><attribute name="action">app.filters-hue-saturation</attribute></item>
<item><attribute name="action">app.filters-saturation</attribute></item>
<item><attribute name="action">app.filters-exposure</attribute></item>
<item><attribute name="action">app.filters-shadows-highlights</attribute></item>
<item><attribute name="action">app.filters-brightness-contrast</attribute></item>
<item><attribute name="action">app.filters-levels</attribute></item>
<item><attribute name="action">app.filters-curves</attribute></item>
</section>
<section>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<attribute name="section-name" translatable="no">Invert</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.filters-invert-perceptual</attribute></item>
<item><attribute name="action">app.filters-invert-linear</attribute></item>
<item><attribute name="action">app.filters-invert-value</attribute></item>
</section>
<section>
<submenu>
<attribute name="label" translatable="yes" context="image-action">_Auto</attribute>
<item><attribute name="action">app.drawable-equalize</attribute></item>
<item><attribute name="action">app.drawable-levels-stretch</attribute></item>
<item><attribute name="action">app.filters-stretch-contrast</attribute></item>
<item><attribute name="action">app.filters-stretch-contrast-hsv</attribute></item>
<item><attribute name="action">app.filters-color-enhance</attribute></item>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="image-action">C_omponents</attribute>
<item><attribute name="action">app.filters-channel-mixer</attribute></item>
<item><attribute name="action">app.filters-component-extract</attribute></item>
<item><attribute name="action">app.filters-mono-mixer</attribute></item>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="image-action">D_esaturate</attribute>
<item><attribute name="action">app.filters-c2g</attribute></item>
<item><attribute name="action">app.filters-desaturate</attribute></item>
<item><attribute name="action">app.filters-mono-mixer</attribute></item>
<item><attribute name="action">app.filters-sepia</attribute></item>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="image-action">_Map</attribute>
menus, plug-ins: now place various plug-ins in the right menu sections. This removes a bunch of inconsistencies we had from the before-2.99.16 version because new items from plug-ins were all added at the bottom of their respective submenu.
2023-07-13 15:34:40 +02:00
<section>
menus: make all section names non-translatable. I'm not sure what's the default for random string attribute, but better be explicit anyway. I think this way, we make sure that gettext won't try and translate these.
2023-07-13 16:57:23 +02:00
<attribute name="section-name" translatable="no">Colormap</attribute>
menus, plug-ins: now place various plug-ins in the right menu sections. This removes a bunch of inconsistencies we had from the before-2.99.16 version because new items from plug-ins were all added at the bottom of their respective submenu.
2023-07-13 15:34:40 +02:00
</section>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<section>
<item><attribute name="action">app.filters-alien-map</attribute></item>
<item><attribute name="action">app.filters-color-exchange</attribute></item>
<item><attribute name="action">app.filters-color-rotate</attribute></item>
</section>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="image-action">_Tone Mapping</attribute>
<item><attribute name="action">app.filters-fattal-2002</attribute></item>
<item><attribute name="action">app.filters-mantiuk-2006</attribute></item>
<item><attribute name="action">app.filters-reinhard-2005</attribute></item>
<item><attribute name="action">app.filters-stress</attribute></item>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="image-action">I_nfo</attribute>
<item><attribute name="action">app.dialogs-histogram</attribute></item>
</submenu>
</section>
<section>
menus: make all section names non-translatable. I'm not sure what's the default for random string attribute, but better be explicit anyway. I think this way, we make sure that gettext won't try and translate these.
2023-07-13 16:57:23 +02:00
<attribute name="section-name" translatable="no">Modify</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.filters-threshold</attribute></item>
<item><attribute name="action">app.filters-colorize</attribute></item>
<item><attribute name="action">app.filters-posterize</attribute></item>
<item><attribute name="action">app.filters-color-to-alpha</attribute></item>
<item><attribute name="action">app.filters-dither</attribute></item>
<item><attribute name="action">app.filters-rgb-clip</attribute></item>
</section>
</submenu>
<!-- Tools Menu -->
<submenu>
<attribute name="label" translatable="yes" context="tools-action">_Tools</attribute>
<section>
<submenu>
<attribute name="label" translatable="yes" context="tools-action">_Selection Tools</attribute>
<item><attribute name="action">app.tools-rect-select</attribute></item>
<item><attribute name="action">app.tools-ellipse-select</attribute></item>
<item><attribute name="action">app.tools-free-select</attribute></item>
<item><attribute name="action">app.tools-foreground-select</attribute></item>
<item><attribute name="action">app.tools-fuzzy-select</attribute></item>
<item><attribute name="action">app.tools-by-color-select</attribute></item>
<item><attribute name="action">app.tools-iscissors</attribute></item>
<!-- Enable when the tool leaves the playground
<item><attribute name="action">app.tools-paint-select</attribute></item>
-->
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="tools-action">_Paint Tools</attribute>
<item><attribute name="action">app.tools-bucket-fill</attribute></item>
<item><attribute name="action">app.tools-gradient</attribute></item>
<item><attribute name="action">app.tools-pencil</attribute></item>
<item><attribute name="action">app.tools-paintbrush</attribute></item>
<item><attribute name="action">app.tools-eraser</attribute></item>
<item><attribute name="action">app.tools-airbrush</attribute></item>
<item><attribute name="action">app.tools-ink</attribute></item>
<item><attribute name="action">app.tools-mypaint-brush</attribute></item>
<item><attribute name="action">app.tools-clone</attribute></item>
<item><attribute name="action">app.tools-heal</attribute></item>
<item><attribute name="action">app.tools-perspective-clone</attribute></item>
<item><attribute name="action">app.tools-convolve</attribute></item>
<item><attribute name="action">app.tools-smudge</attribute></item>
<item><attribute name="action">app.tools-dodge-burn</attribute></item>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="tools-action">_Transform Tools</attribute>
<item><attribute name="action">app.tools-align</attribute></item>
<item><attribute name="action">app.tools-move</attribute></item>
<item><attribute name="action">app.tools-crop</attribute></item>
<item><attribute name="action">app.tools-rotate</attribute></item>
<item><attribute name="action">app.tools-scale</attribute></item>
<item><attribute name="action">app.tools-shear</attribute></item>
<item><attribute name="action">app.tools-perspective</attribute></item>
<item><attribute name="action">app.tools-transform-3d</attribute></item>
<item><attribute name="action">app.tools-unified-transform</attribute></item>
<item><attribute name="action">app.tools-handle-transform</attribute></item>
<item><attribute name="action">app.tools-flip</attribute></item>
<item><attribute name="action">app.tools-cage</attribute></item>
<item><attribute name="action">app.tools-warp</attribute></item>
<!-- Enable when the tool leaves the playground
<item><attribute name="action">app.tools-n-point-deformation</attribute></item>
-->
</submenu>
<item><attribute name="action">app.tools-vector</attribute></item>
<item><attribute name="action">app.tools-text</attribute></item>
</section>
<section>
<item><attribute name="action">app.tools-color-picker</attribute></item>
<item><attribute name="action">app.tools-measure</attribute></item>
<item><attribute name="action">app.tools-zoom</attribute></item>
</section>
app: reimplement the stuff reverted below but stay completely in filter-actions.c and filters-menus.c
2023-05-25 02:30:29 +02:00
<section>
<item><attribute name="action">app.tools-gegl</attribute></item>
</section>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<section>
<item><attribute name="action">app.dialogs-toolbox</attribute></item>
<item><attribute name="action">app.context-colors-default</attribute></item>
<item><attribute name="action">app.context-colors-swap</attribute></item>
</section>
</submenu>
<!-- Filters menu -->
<submenu>
<attribute name="label" translatable="yes" context="filters-action">Filte_rs</attribute>
<section>
<item><attribute name="action">app.filters-repeat</attribute></item>
<item><attribute name="action">app.filters-reshow</attribute></item>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">Recently Used</attribute>
app, menus: remove all placeholder code. This is now fully replaced by the new section name code.
2023-07-13 16:53:11 +02:00
<section>
<attribute name="section-name" translatable="no">Filters</attribute>
</section>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
</submenu>
<item><attribute name="action">app.plug-in-reset-all</attribute></item>
</section>
<section>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">_Blur</attribute>
menus: forward port 2.10 placeholder names into 3.0 section names. It's nearly the same list of placeholders which will make it easier to third-party developers (though format still changed, devs will have to add square brackets for section names). Now some section names are missing because we would need to break some list into smaller sections yet want to avoid having separators everywhere. This makes me wonder if removing my first placeholder implementation was the right idea. Anyway this new implementation is cleaner and we should find a way to add sub-sections without creating separators in menus. Also I didn't try to add new section names (though I did once or twice, e.g. a "Close" section around quit/close actions which didn't exist) but eventually we should. Being able to name logically parts of the menus will make them even more organized (if we can't name a group of actions, it may mean we didn't think properly the organization and order).
2023-07-15 16:31:37 +02:00
<!-- TODO: missing subsections? -->
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.filters-focus-blur</attribute></item>
<item><attribute name="action">app.filters-gaussian-blur</attribute></item>
<item><attribute name="action">app.filters-lens-blur</attribute></item>
<item><attribute name="action">app.filters-mean-curvature-blur</attribute></item>
<item><attribute name="action">app.filters-median-blur</attribute></item>
<item><attribute name="action">app.filters-pixelize</attribute></item>
<item><attribute name="action">app.filters-gaussian-blur-selective</attribute></item>
<item><attribute name="action">app.filters-variable-blur</attribute></item>
<item><attribute name="action">app.filters-motion-blur-circular</attribute></item>
<item><attribute name="action">app.filters-motion-blur-linear</attribute></item>
<item><attribute name="action">app.filters-motion-blur-zoom</attribute></item>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">En_hance</attribute>
<item><attribute name="action">app.filters-antialias</attribute></item>
<item><attribute name="action">app.filters-deinterlace</attribute></item>
<item><attribute name="action">app.filters-high-pass</attribute></item>
<item><attribute name="action">app.filters-noise-reduction</attribute></item>
<item><attribute name="action">app.filters-red-eye-removal</attribute></item>
<item><attribute name="action">app.filters-snn-mean</attribute></item>
<item><attribute name="action">app.filters-unsharp-mask</attribute></item>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">_Distorts</attribute>
<item><attribute name="action">app.filters-apply-lens</attribute></item>
<item><attribute name="action">app.filters-emboss</attribute></item>
<item><attribute name="action">app.filters-engrave</attribute></item>
<item><attribute name="action">app.filters-lens-distortion</attribute></item>
<item><attribute name="action">app.filters-kaleidoscope</attribute></item>
<item><attribute name="action">app.filters-mosaic</attribute></item>
<item><attribute name="action">app.filters-newsprint</attribute></item>
<item><attribute name="action">app.filters-polar-coordinates</attribute></item>
<item><attribute name="action">app.filters-ripple</attribute></item>
<item><attribute name="action">app.filters-shift</attribute></item>
<item><attribute name="action">app.filters-spherize</attribute></item>
<item><attribute name="action">app.filters-value-propagate</attribute></item>
<item><attribute name="action">app.filters-video-degradation</attribute></item>
<item><attribute name="action">app.filters-waves</attribute></item>
<item><attribute name="action">app.filters-whirl-pinch</attribute></item>
<item><attribute name="action">app.filters-wind</attribute></item>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">_Light and Shadow</attribute>
<section>
menus: make all section names non-translatable. I'm not sure what's the default for random string attribute, but better be explicit anyway. I think this way, we make sure that gettext won't try and translate these.
2023-07-13 16:57:23 +02:00
<attribute name="section-name" translatable="no">Light</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.filters-bloom</attribute></item>
<item><attribute name="action">app.filters-supernova</attribute></item>
<item><attribute name="action">app.filters-lens-flare</attribute></item>
</section>
<section>
menus: make all section names non-translatable. I'm not sure what's the default for random string attribute, but better be explicit anyway. I think this way, we make sure that gettext won't try and translate these.
2023-07-13 16:57:23 +02:00
<attribute name="section-name" translatable="no">Shadow</attribute>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.filters-dropshadow</attribute></item>
<item><attribute name="action">app.filters-long-shadow</attribute></item>
<item><attribute name="action">app.filters-vignette</attribute></item>
</section>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">_Noise</attribute>
<item><attribute name="action">app.filters-noise-cie-lch</attribute></item>
<item><attribute name="action">app.filters-noise-hsv</attribute></item>
<item><attribute name="action">app.filters-noise-hurl</attribute></item>
<item><attribute name="action">app.filters-noise-pick</attribute></item>
<item><attribute name="action">app.filters-noise-rgb</attribute></item>
<item><attribute name="action">app.filters-noise-slur</attribute></item>
<item><attribute name="action">app.filters-noise-spread</attribute></item>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">Edge-De_tect</attribute>
<item><attribute name="action">app.filters-difference-of-gaussians</attribute></item>
<item><attribute name="action">app.filters-edge</attribute></item>
<item><attribute name="action">app.filters-edge-laplace</attribute></item>
<item><attribute name="action">app.filters-edge-neon</attribute></item>
<item><attribute name="action">app.filters-edge-sobel</attribute></item>
<item><attribute name="action">app.filters-image-gradient</attribute></item>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">_Generic</attribute>
<item><attribute name="action">app.filters-convolution-matrix</attribute></item>
<item><attribute name="action">app.filters-distance-map</attribute></item>
<item><attribute name="action">app.filters-normal-map</attribute></item>
<item><attribute name="action">app.filters-dilate</attribute></item>
<item><attribute name="action">app.filters-erode</attribute></item>
app: reimplement the stuff reverted below but stay completely in filter-actions.c and filters-menus.c
2023-05-25 02:30:29 +02:00
<section>
<item><attribute name="action">app.filters-gegl-graph</attribute></item>
</section>
</submenu>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<submenu>
<attribute name="label" translatable="yes" context="filters-action">C_ombine</attribute>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">_Artistic</attribute>
<item><attribute name="action">app.filters-apply-canvas</attribute></item>
<item><attribute name="action">app.filters-cartoon</attribute></item>
<item><attribute name="action">app.filters-cubism</attribute></item>
<item><attribute name="action">app.filters-tile-glass</attribute></item>
<item><attribute name="action">app.filters-oilify</attribute></item>
<item><attribute name="action">app.filters-photocopy</attribute></item>
<item><attribute name="action">app.filters-slic</attribute></item>
<item><attribute name="action">app.filters-softglow</attribute></item>
<item><attribute name="action">app.filters-waterpixels</attribute></item>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">_Decor</attribute>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">_Map</attribute>
<item><attribute name="action">app.filters-bump-map</attribute></item>
<item><attribute name="action">app.filters-displace</attribute></item>
<item><attribute name="action">app.filters-fractal-trace</attribute></item>
<item><attribute name="action">app.filters-illusion</attribute></item>
<item><attribute name="action">app.filters-little-planet</attribute></item>
<item><attribute name="action">app.filters-panorama-projection</attribute></item>
<item><attribute name="action">app.filters-recursive-transform</attribute></item>
<item><attribute name="action">app.filters-tile-paper</attribute></item>
<item><attribute name="action">app.filters-tile-seamless</attribute></item>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">_Render</attribute>
menus, plug-ins: now place various plug-ins in the right menu sections. This removes a bunch of inconsistencies we had from the before-2.99.16 version because new items from plug-ins were all added at the bottom of their respective submenu.
2023-07-13 15:34:40 +02:00
<section>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">_Fractals</attribute>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">N_oise</attribute>
<item><attribute name="action">app.filters-noise-cell</attribute></item>
<item><attribute name="action">app.filters-noise-perlin</attribute></item>
<item><attribute name="action">app.filters-plasma</attribute></item>
<item><attribute name="action">app.filters-noise-simplex</attribute></item>
<item><attribute name="action">app.filters-noise-solid</attribute></item>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">_Pattern</attribute>
<item><attribute name="action">app.filters-bayer-matrix</attribute></item>
<item><attribute name="action">app.filters-checkerboard</attribute></item>
<item><attribute name="action">app.filters-diffraction-patterns</attribute></item>
<item><attribute name="action">app.filters-grid</attribute></item>
<item><attribute name="action">app.filters-linear-sinusoid</attribute></item>
<item><attribute name="action">app.filters-maze</attribute></item>
<item><attribute name="action">app.filters-sinus</attribute></item>
<item><attribute name="action">app.filters-spiral</attribute></item>
</submenu>
</section>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">_Web</attribute>
<item><attribute name="action">app.filters-semi-flatten</attribute></item>
</submenu>
</section>
menus: add missing submenus to image-menu.ui.in.in This allows for translation and use of accelerators.
2023-07-13 21:30:14 +02:00
<section>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">An_imation</attribute>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">De_velopment</attribute>
<submenu>
menus: fix Plug-In CamelCase Followup to 34af64b70f05f188fc4e36337900abe2d7c068e6 The menu definition in image-menu.ui.in.in didn't have the same capitalization as in the plug-ins that uses it, so it was never used, and would never be shown translated.
2024-08-25 21:44:58 +02:00
<attribute name="label" translatable="yes" context="filters-action">Plug-In _Examples</attribute>
menus: add missing submenus to image-menu.ui.in.in This allows for translation and use of accelerators.
2023-07-13 21:30:14 +02:00
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">_Python-Fu</attribute>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="filters-action">_Script-Fu</attribute>
</submenu>
</submenu>
</section>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="windows-action">_Windows</attribute>
<section>
<submenu>
app, menus: fix the "Recently Closed Docks" auto-filling menu. It was actually working fine except that I wrongly named the submenu somehow, but even more particularly I thought it was about single dockables (tabs) whereas it was about full detached docks (a window containing several dockables/tabs).
2023-03-31 23:42:55 +02:00
<attribute name="label" translatable="yes" context="windows-action">_Recently Closed Docks</attribute>
<!-- Recently closed docks will be filled here automatically -->
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="windows-action">_Dockable Dialogs</attribute>
menus: fix dialogs_dockable_actions being in 2 groups. Depending on where it's used, this list of action can be either in the "dockable" or the "dialogs" action group. The meson rule is a bit more complicated than I wished it were because of the ever-so-blocking lack of simple dependency in meson. Cf. my latest comment: https://github.com/mesonbuild/meson/issues/8123#issuecomment-1496168759
2023-04-04 17:28:49 +02:00
<xi:include href="@GROUP@-dialogs-menuitems.ui" />
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
</submenu>
<item><attribute name="action">app.dialogs-toolbox</attribute></item>
</section>
app, menus: add the generated actions in the main menu. These are the menu items such as the recently opened images, or recently used filters, etc. Some notes: - I added back a "placeholder" concept in the GimpMenu logic. This will allow to place items at specific positions in the menu (either under the placeholder, which will make the last item be on top or above the placeholder to have the last item be in the bottom, depending on needs). Technically placeholders are just menu items with a label (used as placeholder key) and no associated action, which I will leave invisible. - I add a logic for submenus so that they are invisible by default and are only made visible when we add a menu item with an action in there. - I removed filling the "/Filters/Recently Used/Plug-ins" placeholder. As far as I could see, it was never filled (neither with old or new code) and the "/Filters/Recently Used/Filters" actually already takes care of filling the "Recently Used" submenu with both GEGL operations and plug-in calls. - The old gimp_ui_manager_add_ui() API is for all types of menus, e.g. including the ones created by dockables or elsewhere whereas my new API is (for now) still specific to the top menu. This will have to be further implemented later. I left a bunch of "TODO GMenu"-s for the time being. - I see 2 dock-related generated items which seem to never be added, for recently added and closed docks. It doesn't seem to work in the old API as well. I'll want to have a closer look too.
2023-02-10 12:57:29 +01:00
<section>
app, menus: remove all placeholder code. This is now fully replaced by the new section name code.
2023-07-13 16:53:11 +02:00
<attribute name="section-name" translatable="no">Images</attribute>
app, menus: add the generated actions in the main menu. These are the menu items such as the recently opened images, or recently used filters, etc. Some notes: - I added back a "placeholder" concept in the GimpMenu logic. This will allow to place items at specific positions in the menu (either under the placeholder, which will make the last item be on top or above the placeholder to have the last item be in the bottom, depending on needs). Technically placeholders are just menu items with a label (used as placeholder key) and no associated action, which I will leave invisible. - I add a logic for submenus so that they are invisible by default and are only made visible when we add a menu item with an action in there. - I removed filling the "/Filters/Recently Used/Plug-ins" placeholder. As far as I could see, it was never filled (neither with old or new code) and the "/Filters/Recently Used/Filters" actually already takes care of filling the "Recently Used" submenu with both GEGL operations and plug-in calls. - The old gimp_ui_manager_add_ui() API is for all types of menus, e.g. including the ones created by dockables or elsewhere whereas my new API is (for now) still specific to the top menu. This will have to be further implemented later. I left a bunch of "TODO GMenu"-s for the time being. - I see 2 dock-related generated items which seem to never be added, for recently added and closed docks. It doesn't seem to work in the old API as well. I'll want to have a closer look too.
2023-02-10 12:57:29 +01:00
</section>
<section>
app, menus: remove all placeholder code. This is now fully replaced by the new section name code.
2023-07-13 16:53:11 +02:00
<!-- TODO GMenu: is this placeholder section actually working/used? -->
<attribute name="section-name" translatable="no">Docks</attribute>
app, menus: add the generated actions in the main menu. These are the menu items such as the recently opened images, or recently used filters, etc. Some notes: - I added back a "placeholder" concept in the GimpMenu logic. This will allow to place items at specific positions in the menu (either under the placeholder, which will make the last item be on top or above the placeholder to have the last item be in the bottom, depending on needs). Technically placeholders are just menu items with a label (used as placeholder key) and no associated action, which I will leave invisible. - I add a logic for submenus so that they are invisible by default and are only made visible when we add a menu item with an action in there. - I removed filling the "/Filters/Recently Used/Plug-ins" placeholder. As far as I could see, it was never filled (neither with old or new code) and the "/Filters/Recently Used/Filters" actually already takes care of filling the "Recently Used" submenu with both GEGL operations and plug-in calls. - The old gimp_ui_manager_add_ui() API is for all types of menus, e.g. including the ones created by dockables or elsewhere whereas my new API is (for now) still specific to the top menu. This will have to be further implemented later. I left a bunch of "TODO GMenu"-s for the time being. - I see 2 dock-related generated items which seem to never be added, for recently added and closed docks. It doesn't seem to work in the old API as well. I'll want to have a closer look too.
2023-02-10 12:57:29 +01:00
</section>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<section>
<item><attribute name="action">app.windows-hide-docks</attribute></item>
<item><attribute name="action">app.windows-show-tabs</attribute></item>
<submenu>
<attribute name="label" translatable="yes" context="windows-action">_Tabs Position</attribute>
<item><attribute name="action">app.windows-tabs-position-top</attribute></item>
<item><attribute name="action">app.windows-tabs-position-bottom</attribute></item>
<item><attribute name="action">app.windows-tabs-position-left</attribute></item>
<item><attribute name="action">app.windows-tabs-position-right</attribute></item>
</submenu>
<item><attribute name="action">app.windows-use-single-window-mode</attribute></item>
</section>
</submenu>
<submenu>
<attribute name="label" translatable="yes" context="help-action">_Help</attribute>
<section>
<item><attribute name="action">app.help-help</attribute></item>
<item><attribute name="action">app.help-context-help</attribute></item>
menus: Rearrange Help menu Moves "About Gimp" to end of menu to match common UX. User Manual is also moved right after the Context Help option as they are related items.
2023-08-20 13:02:27 +00:00
<submenu>
<attribute name="label" translatable="yes" context="help-action">_User Manual</attribute>
scripts: GIMP Online accelerator and link fixes * 'Use selection' entry was missing due to wrong name * Write Table of contents without brackets, fixes #9903 * Avoid accelerator clashes
2024-02-18 13:09:45 +01:00
<section>
<attribute name="section-name" translatable="no">Table of Contents</attribute>
</section>
menus: Rearrange Help menu Moves "About Gimp" to end of menu to match common UX. User Manual is also moved right after the Context Help option as they are related items.
2023-08-20 13:02:27 +00:00
</submenu>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
<item><attribute name="action">app.dialogs-tips</attribute></item>
<item><attribute name="action">app.dialogs-welcome</attribute></item>
</section>
<section>
<item><attribute name="action">app.dialogs-action-search</attribute></item>
</section>
menus, plug-ins: now place various plug-ins in the right menu sections. This removes a bunch of inconsistencies we had from the before-2.99.16 version because new items from plug-ins were all added at the bottom of their respective submenu.
2023-07-13 15:34:40 +02:00
<section>
menus: make all section names non-translatable. I'm not sure what's the default for random string attribute, but better be explicit anyway. I think this way, we make sure that gettext won't try and translate these.
2023-07-13 16:57:23 +02:00
<attribute name="section-name" translatable="no">Programming</attribute>
menus, plug-ins: now place various plug-ins in the right menu sections. This removes a bunch of inconsistencies we had from the before-2.99.16 version because new items from plug-ins were all added at the bottom of their respective submenu.
2023-07-13 15:34:40 +02:00
</section>
menus: Rearrange Help menu Moves "About Gimp" to end of menu to match common UX. User Manual is also moved right after the Context Help option as they are related items.
2023-08-20 13:02:27 +00:00
<section>
<submenu>
<attribute name="label" translatable="yes" context="help-action">_GIMP Online</attribute>
</submenu>
<item><attribute name="action">app.dialogs-about</attribute></item>
</section>
app, menus: very early prototype for a GimpMenu. This demonstrates a first version of our replacing menu, using GAction and GMenuModel. I had to make our own subclass of GtkMenu to process the model (from a .ui XML file) for the following reasons: * gtk_menu_new_from_model() doesn't support tooltips, which is a feature we use quite extensively in GIMP: with all our filters, being able to give a longer description is often useful; moreover we use tooltips to give hints about why a menu item is deactivated as well. Unfortunately it looks like GTK doesn't consider this lack as a problem and don't plan on adding tooltip support. See: https://gitlab.gnome.org/GNOME/gtk/-/issues/785 * I won't to avoid copying action's label and icons in the .ui file. This only duplicates strings and would be a source of issues each time we change action's strings (we'd have to do it in 2 places, which someone will inevitably forget). Now it still has various issues: * The syncing between actions and menu items need to be cleaned up. It's still in early demo code. * It uses directly some Gtk*Action code because GimpRadioAction and GimpToggleAction are not directly related right now (only through their parents). * gtk_application_set_menubar() might still be necessary on macOS as I think it's what enables the native menu system on this OS. It means that we'll have to edit the menu model to add back the labels (as this function does not extract these from the linked action since GAction has no label or icon concept). * Icons are not taken into account right now. * I'll have to verify if GimpAction with proxy work (but my guess is that right now, it won't). * Action's active state is not synced with menu item active state right now. * Various actions are inserted live, such as opened images, opened views, recently opened images, and so on. This needs to be implemented back. * Plug-ins need to be able to create their own menu item into this new menu. * For all these various reasons, I'm keeping the old menu around, for the sake of comparison, until the time the new one becomes feature-full. Part of this commit is inspired by !558 and obsoletes this MR.
2023-02-07 13:59:20 +01:00
</submenu>
</menu>
</interface>
Reference in a new issue Copy permalink