Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SPIKE: Experiment with placing multiple, non-overlapping labels #334

Open
Richargh opened this issue Jan 28, 2019 · 3 comments
Open

SPIKE: Experiment with placing multiple, non-overlapping labels #334

Richargh opened this issue Jan 28, 2019 · 3 comments
Labels
feature Feature requests pr-visualization Issues that touch the visualization pr(oject) which means web and desktop features. priority:medium Set by PO research Task that requires significant research into what other people do
Milestone
audit-readiness

Comments

@Richargh
Copy link

Richargh commented Jan 28, 2019 •
edited
Loading

CodeCharta currently displays labels for the tallest x buildings. When multiple labels are enabled they tend to overlap each other.

For audits especially we want to show the names of big packages so people can recognize where they are and big buildings to see the main offenders.

This spike should experiment with placing multiple labels for the 10 tallest buildings and for 5 top-level packages (root/*) and for 5 second-level packages (root/*/*).

  • The labels don't necessarily have to be overlay-free but all should be readable
  • Experiments with transparancy are also encouraged
  • Labels can be connected with visible edges to their building/package
  • They should not be hidden behind buildings

Side-note, it's a win if the notes are colored differently and they look better than our current ones. :)

Existing automated label placement algorithms are:

  • Greedy Depth-First
  • Discrete Gradient Descent
  • Hirsch's Algorithm
  • Zoraster's Algorithm
  • Simulated Annealing
@Richargh Richargh added this to the audit-readiness milestone Jan 28, 2019
@Richargh Richargh added spike pr-visualization Issues that touch the visualization pr(oject) which means web and desktop features. labels Jan 28, 2019
@alschmut alschmut mentioned this issue Jul 12, 2019
Closed
@Richargh Richargh added pr-prototype Issues that prototype or spike but do not modify our regular pr(ojects) and removed spike labels Aug 16, 2019
@Richargh Richargh added the research Task that requires significant research into what other people do label Sep 13, 2019
@Richargh Richargh removed the pr-prototype Issues that prototype or spike but do not modify our regular pr(ojects) label Nov 16, 2019
@BridgeAR BridgeAR added the feature Feature requests label May 15, 2020
@BridgeAR BridgeAR added the priority:medium Set by PO label Jul 4, 2020
@RomanenkoVladimir
Copy link
Member

RomanenkoVladimir commented Oct 9, 2020 •
edited
Loading

Maybe connected to #1348 and #1347?

@BridgeAR
Copy link
Member

Partially, yes.

This was referenced Nov 20, 2020
Closed
Closed
@Richargh
Copy link
Author

Maybe also connected with #1491 and #1029 :) I added a comment to those issues as well.

@BridgeAR BridgeAR added priority:high Set by PO and removed priority:medium Set by PO labels Dec 23, 2020
@Shivan-997 Shivan-997 assigned Shivan-997 and unassigned Shivan-997 May 4, 2021
@BridgeAR BridgeAR added priority:medium Set by PO and removed priority:high Set by PO labels May 7, 2021
@BridgeAR BridgeAR mentioned this issue Nov 15, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature Feature requests pr-visualization Issues that touch the visualization pr(oject) which means web and desktop features. priority:medium Set by PO research Task that requires significant research into what other people do
Projects
None yet
Milestone
audit-readiness
Development

No branches or pull requests
4 participants
@BridgeAR @RomanenkoVladimir @Richargh @Shivan-997