search

okfn-brasil / mosaico

Visualization on the brazilian budget for FGV
GNU Affero General Public License v3.0
5 stars 0 forks source link

Mini-treemap for navigation and visualization #30

Open ltartari opened 11 years ago

trickvi commented 11 years ago

Could you explain this in a bit more detail. I'm not sure I understand entirely.

vitorbaptista commented 11 years ago

This is still in the treemap page. The idea is that whenever you drilldown on a tile in the treemap, you miss the big view. For example, if I'm at http://weiss-staging.herokuapp.com/treemap/2013/10-saude, I don't know how big is it considering the total. Does it represent 10%? 15%? or what?

So the idea is to have a mini-treemap (like a minimap) with everything greyed-out, except the tile you're currently viewing. So you'll see a small treemap like in http://weiss-staging.herokuapp.com/treemap/2013, with the SAUDE tile highlighted.

It'll also work as a back button.

Got it?

trickvi commented 11 years ago

Ah so this isn't a part of the bubbletree (orbital)? Is this incorrectly labelled?

vitorbaptista commented 11 years ago

I thought that as well, and we might want to change it. The labels are basically telling milestones. The phase 1 (named "Treemap"), and phase 2 (named "Orbital"). It doesn't mean that in phase 2 we'll only do stuff about the bubbles, but that it's the main deliverable.

vitorbaptista commented 11 years ago

BTW, I'm concerned with this card because of possible performance issues, as the treemap feels a bit slow when we have too many tiles (i.e. http://weiss-staging.herokuapp.com/treemap/2013/12-educacao/364-ensino-superior/26000-ministerio-da-educacao). Having two on a single page would make it worse.

Also about how to highlight the current tile being shown. This might be easy, but I'm not sure.

trickvi commented 11 years ago

If you have too many tiles won't a small treemap be kind of difficult to use, especially if you highlight one of the smaller tiles? But I agree with you that this might not be optimal. Have you tried turning off the animation (or maybe you like the animation).

ltartari commented 11 years ago

We discussed this functionality a long time ago (during the inception to be precise) and it would be used for navigation and showing the current tile inside the previous context. I agree that it would be of no use for smaller tiles, but as I said, this was decided in the past and the context has changed. We need to check with the client if this is still valid and let them decide if we really need this. Although this issue is a valid one (unreadable sizes) my greatest concern is around the general performance of the page rendering.

Regarding the animation, it is one of my few pet peeves on the graph… I just don't like it and I think it does not reflect the data in a proper way. Having it zooming into the tile after clicking on it instead of zooming in the whole graph at the beginning would be a far better way to do it IMHO. Is that something we can easily do?

vitorbaptista commented 11 years ago

Not sure how hard it would be, but JIT, the framework OpenSpending uses under the hood, already has this animation implemented.