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


Hi Sebastian,

On Wed, 2010-11-10 at 10:13 +0100, Sebastian Spaeth wrote:
So who would be able to make sure that we don't bundle the high contrast
icons in our buld anymore (and either purge those files or move them to
a high contrast theme...) ?

        Hah ! it is you I guess - you just volunteered.

        Currently our hicontrast theme is built by
packimages/pack/makefile.mk:

# generate the HiContrast icon set
$(MISC)$/hicontrast.flag .PHONY :
    $(PERL) $(SOLARENV)$/bin$/hicontrast-to-theme.pl
$(SOLARSRC)$/default_images $(MISC)$/hicontrast && $(TOUCH) $@

        We need to fixup this "hicontrast-to-theme.pl" script - so that we can
base it from a (new) base-directory as well; say
ooo_custom_images/highcontrast

        We need to move and rename the lch_ and sch_ etc. variants into lc_ and
sc_ variants in that directory incrementally, as they are removed from
the code; ie. git mv'ing the ones that Joseph has identified across [ I
believe git will do this efficiently ].

        That is mostly a matter of tweaking / testing the
hicontrast-to-theme.pl script and doing some git movement - can you look
at that Sebastian ?

        The key is (of course) to only move/rename those files for which we
already have patches :-)

        Thanks !

                Michael.

-- 
 michael.meeks@novell.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.