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

Adjust branch label and vaccine cross styling #529

Merged
merged 2 commits into from
Mar 22, 2018
Merged

Adjust branch label and vaccine cross styling #529

merged 2 commits into from
Mar 22, 2018

Conversation

trvrb
Copy link
Member

@trvrb trvrb commented Mar 21, 2018

@jameshadfield ---

The changes to branch label styling shouldn't be controversial. However, I've decided to remove the dashed lines from the vaccine crosses. I believe it was adding confusion rather than removing it. If we go in this direction I think we need the full description of choice and deployment. But even then I really feel like it will be overloading the tree. Perhaps the best thing to think toward is a separate vaccine panel.

Also, I think the symbols (vaccine crosses, serum gears) look much better with a bit of white space surrounding them. This was accomplished previously by using a character as the cross and giving a stroke of #fff and a fill of #333. Something to think about.

old

new

Add weight and lighten clade labels, shrink mutation labels
Remove the extra dashed branch.
@trvrb trvrb merged commit 929494b into master Mar 22, 2018
@trvrb trvrb deleted the styling branch March 22, 2018 17:51
@jameshadfield
Copy link
Member

@trvrb the reason they are SVG shapes not crosses with the nice styling is to do with attaching handlers to them - see #498. If they are always going to be directly over the tip then I guess it's not necessary. However I think there is some work in the future on this where we could show info regarding deployment time etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants