Skip to content

[ENH] Different background for upper and lower triangles #1324

Description

@henrydingliu

Description

Add an option to differentiate cell shading, such as this exhibit in Friedland

Image

Is your feature request aligned with the scope of the package?

  • Yes, absolutely!
  • No, but it's still worth discussing.
  • N/A (this request is not a codebase enhancement).

Describe the solution you'd like, or your current workaround.

No response

Do you have any additional supporting notes?

No response

Would you be willing to contribute this ticket?

  • Yes, absolutely!
  • Yes, but I would like some help.
  • No.

Activity

  1. added this to the v1.0.0 milestone on Sep 9, 2026
  2. modified the milestones: v1.0.0, v2.0.0 on Sep 10, 2026
  3. genedan commented on Sep 10, 2026

    @genedan
    Member

    I think it's time to adapt the pandas Styler to act upon a Triangle class. We can technically access it by doing Triangle.to_frame().style, but challenges remain:

    • Highlighting the lower triangle (as you mentioned) without having to define a super-complicated formula, e.g., out of the box
    • Likewise, highlighting individual diagonals and styling other triangle components
    • Lack of support for origin/development axes

    And, check out this feature to concat stylers:

    https://pandas.pydata.org/docs/user_guide/style.html#Concatenating-DataFrame-Outputs

    What this means is that if we adapt the styler, we can make displays that concat Triangles with each other and on top of tables of patterns - i.e., a unified triangle/patterns exhibit, which means we could make some very slick presentations in the Friedland recreation.

  4. henrydingliu commented on Sep 10, 2026

    @henrydingliu
    MemberAuthor

    And, check out this feature to concat stylers:

    thanks a ton! I'm going to use this right now in chapter 11.

    I think it's time to adapt the pandas Styler to act upon a Triangle class.

    i think i understand the concept. do you envision stylers to be in addition to or superseding #1281?

  5. genedan commented on Sep 10, 2026

    @genedan
    Member

    Yeah I think we can close that one. It was superseded by #1309, too.

  6. updated Priority High, Scope Both and Effort Medium on Sep 11, 2026
  7. added theissue type on Sep 11, 2026
  8. self-assigned this
    on Sep 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Fields

Priority

High

Effort

Medium

Scope

Both

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions