elementary / elementary/code

Outline plugin should differentiate by visibility and member type

Aperta
#498 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
Needs Design Priority: Medium Status: Confirmed
Lingua principale
Vala
Stelle
521
Fork
118
Merge medio
1g 8h
PR unite (30g)
14

Descrizione

I'm documenting a vala project and I realised that the reason why outline has been so useless to me is that when I'm using outline to review the code of a class I've been trying to understand an instance of I just need the public members not the internal stuff but there's no clear way to understand what's public or private from the outline plugin. I had a few ideas about how to fix this but it's a design task, and I don't really do mockups.

- icons: most aesthetic, requires excessive design
- collapsible tree for public and private: gets stuff out of the way
- format the labels in UML: quick, easy, unambiguous, not beginner friendly

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/62656956-outline-plugin-should-differentiate-by-visibility-and-member-type?utm_campaign=plugin&utm_content=tracker%2F61917289&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F61917289&utm_medium=issues&utm_source=github).

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.