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


Unsure whether this is right forum or area to post this, but here goes:

I use LibO3.5 within my corporate work environment, along with a number of
other Open source apps - GIMP, Inkscape.

What I need LibO to do is handle a "corporate" color palette easily. I have
managed to edit the relevant files (.GPL) for Inkscape and GIMP - but LibO
is proving more difficult.

A number of Google searches highlights that it does not appear
straightforward to "swop" or make default my corporate colour palette in
LibO.

If this is the area for development in this area - while the Microsoft
"Theme" is attractive - I would prefer the palette "load" model approach of
something like GIMP.

I'm "power user" technical but not coding level technical - and I would like
to support developing this - how would I go about it?

--
View this message in context: 
http://nabble.documentfoundation.org/Color-handling-tp3893327p3941432.html
Sent from the Design mailing list archive at Nabble.com.

-- 
Unsubscribe instructions: E-mail to design+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/design/
All messages sent to this list will be publicly archived and cannot be deleted

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.