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


On Tue, 2014-01-07 at 15:05 -0200, Olivier Hallot wrote:
Hi

I have a demand to tweak some dialogs with better layout or widgets
positions. In order to avoid disruption with the core development, I
would like to know if these .ui dialogs can be packed into UNO extensions.

What you want to do is to effectively over-ride/replace existing .ui
files which isn't something I had considered doing at all. I have no
plans around that. 

I guess it wouldn't be impossible to e.g. in VclBuilder::VclBuilder
where the sUIDir, sUIFile and sID of the dialog are passed in to there
see if there any listeners to a hypothetical uiload event and ask them
if the want to provide a .ui for that case to use instead of the normal
one.

Or maybe some config settings to set some override dirs which would be
searched before the standard one to find the .ui. Obviously tweaking
things here would be necessarily very fragile. One could move elements,
hide them, change default buttons and those would generally work but
adding and removing stuff wouldn't generally work.

For the more normal case where extensions want to use the .ui for their
own dialogs I sort of plan to allow that once all the normal dialogs are
converted over and then make a careful glade catalog to describe the
awt-view of the uno-api widgets, figure out the existing translation
stuff for extension widgets and see what the right thing to do there is.

C.


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.