https://bugs.documentfoundation.org/show_bug.cgi?id=159330

Justin L <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #3 from Justin L <[email protected]> ---
Summary: Functionality is missing for importing/configuring the leaderLine
between the Data Label and the pie chart slice. The current implementation
simply draws a default line using the color of the Data Labels. This is a 6+
week project.

Extend LO document model
    • the leaderLines need to support the full range of line properties, so
chart:series needs something like chart:leaderLine-style containing a
chart:connector.

UNO API
    • scripting read/write for these properties

ODF filters
    • since after OOXML import, the properties are exported/re-imported using
ODF filters before being displayed, ODF support is essential.
        ◦ import
        ◦ export

OOXML filters
    • Only DOCX is needed since DOC and RTF simply import these as
alternative-format images

Layout
    • the layout will take significant effort to create, because it seems to be
unique, so there won’t be example code to copy from.
        ◦ is a single transparent overlay across the entire chart
        ◦ color (gradient/bitmap/hatch) need to be applied to the overlay as a
whole.
        ◦ leaderLines are masked onto the layer, removing the transparency and
letting the color peak out.

Unit tests
    • Ideally every feature commit has matching unit tests. Additionally, one
or two larger, comprehensive unit tests will be required.

UI
    • this should not be too much work. It is just a collection of existing
attributes (area, transparency, lines) but there are many pieces to wire
together.

Documentation
    • update help.git, release notes

Specification
    • make sure this gets into ODF next

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to