On Fri, May 11, 2012 at 11:50 AM, Kohei Yoshida <kohei.yoshida@gmail.com> wrote:
My gut feeling (totally unscientific and may be illogical) tells me
that wedging this information into the style section may not be the
cleanest approach. I could, however, imagine we define these color
scales elsewhere, and reference them from the style section somehow,
either by name or by index. Or just totally leave it outside the
style section. Somehow I tend to think that this feature behaves more
like a database range, chart source range, or pivot table data source,
than conditional formatting. And based on how Markus is implementing
it so far even in the core, the color scale data is separated stored
than the conventional conditional formatting data.
Actually I'll take a step back from this. The existing conditional
formatting implementation *does* have the concept of ranges. For
instance, unique values condition only makes sense when it's applied
to a range of cells. So, color scales may be considered a logical
extension of the conventional conditional formatting.
Come to think of it, how are we dealing with these unique values,
non-unique values conditions in ODF, which has similar range
requirement to color scales (and data bars)?
Kohei
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.