On Mon, 2013-03-18 at 12:01 +0100, Lubos Lunak wrote:
On Fri, 2013-03-15 at 18:32 +0000, Jack Leigh (via Code Review) wrote:
various .ui fixes caught by linter tool
Sounds really interesting :-) can we make the tool part of our build
process somehow ?
And do we need such a tool at all? If Glade is not capable of providing
sensible defaults for spacing and similar features, cannot our code for
loading the .ui files handle that?
Not sure it's -that- easy, we can use the same widgets with different
padding around the place and/or may want to tweak that.
Either way - IIRC we also want the linter to ensure that all strings
are marked translated to avoid the problems we had around 4.0.0 here.
Jack - I guess a good place to put the lint tool might be in the
install rule for the .ui files:
solenv/gbuild/UI.mk
would be the place to add that; though it's not terribly clear
how/where - presumably the:
$(call gb_Package_Package_internal,$(1)_ui,$(SRCDIR))
piece does something like that,
Thanks !
Michael.
--
michael.meeks@suse.com <><, Pseudo Engineer, itinerant idiot
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.