Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


Hi Stephan,

On Wed, Nov 4, 2015 at 9:52 AM, Stephan Bergmann <sbergman@redhat.com> wrote:
Out of curiosity, do you have a short summary what this is going to be used for? Is it about right-click context menus
Yes. I'm trying to implement tdf#93837 - Allow customization of the Context Menus (which is a continuation of i#7449). For this I need to change the current .src-based popup menus to a format that allows writing the modified menu back, and also be able to save to the user profile or the document itself, the same way we do for other UI elements. But there are also some secondary goals, that could be considered later:

1. Easy creation of toolbar buttons with commands-based drop-down menus. This is something the UX guys are asking for a very long time.

2. We already support 3 different formats to express menus: .src, framework, VclBuilder. I really hope that it will be possible to kill one of them (the .src) at some point.

(are they maybe created in hard-coded ways in the code right now, and that will change to a more flexible scheme)?
It depends, e.g. the hard-coded menu in chart2/source/controller/main/ChartController_Window.cxx should be easily convertible to xml (and killing then also svt::ContextMenuHelper), but there are some menus with a custom implementation (e.g. spellcheck) that unfortunately would need more complex solution.

Maxim


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.