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.

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

[MINOR] Scale node size based on freshness/modification recency #291

Open
ParetoOptimalDev opened this issue Apr 26, 2023 · 0 comments
Open
Labels
minor feature Feature request inline with current graphing capabilites

Comments

@ParetoOptimalDev
Copy link

Have you checked whether this feature is not already on the project board?

Yes, I searched for scale and size.

Is your feature request related to a problem? Please describe.

Frequently older notes are of less importance to me. I'd like this to be visually reflected.

Describe the solution you'd like

Ideally you'd be able to choose just scale based on:

  • number of links (current feature)
  • freshness/modification recency
  • both number of links and freshness/modification recency

I imagine figuring out the weights for the case where both are taken into account would be difficult and it would be easiest to make that configurable as well?

Describe alternatives you've considered

Not having it and not using the graph as much because I have to mentally calculate the freshness of my notes.

Additional context

None at this time.

@ParetoOptimalDev ParetoOptimalDev added the minor feature Feature request inline with current graphing capabilites label Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
minor feature Feature request inline with current graphing capabilites
Projects
None yet
Development

No branches or pull requests

1 participant