great topic! We may move this to an Idea card for further discussion. And if we make enough progress, we may make a Blueprint.
Short answer is that yes this is on our radar (lots of folks really want viz tools) but we don't have very polished plans yet. Some things we do have:
- a lot in the works for JSON calls that could be used by a lot of visualization tools. See improve JSON rendering
- a Blueprint for Hands of Cards that implies the need for querying functionally related cards
- a site that managed to build a visualization tool with existing queries (see http://grouppatternlanguage.org/Full_Map). Though I just tried it and it isn't working for me. That site was mostly for generating their data and isn't in frequent use now.
The JSON is going to happen reasonably soon. The way I see this happening in a really robust way is for us to team up with projects that have very concrete, fundable visualization goals and apply for funding to meet their needs via Wagn (making sure the funding allows for generalizable solutions).
visualization+*tagged
--Ethan McCutchen.....2013-03-27 16:37:38 +0000
Also see organizing.
Curious, when you say "tree structure" do you mean you have cards named something like foo, foo+bar, foo+baz, foo+bar+moo, foo+bar+moo+cow, etc.?
--John Abbe.....2013-03-27 19:21:30 +0000
@Ethan: I tried that Full_Map, but it does not work for me neither. Looking forward for the JSON implementation - hopefully some doc (dev, users,etc.) will be there too ;).
@John: Well since there was no recommended way how to store data I came up with my solution.
At first I decided to go with "basic cards" till the leaf level, where I would put simple [[cards]]. The next one was discovery of {{card}}. However, I found out that having too many {{}} on one card makes it nearly impossible to use - it is really slow (the number of such cards was around 15)
The last improvement, mostly because I found out there is condition of uniqueness, on the structure was that I stayed with the basic cards for the core nodes (do not want to have links because I want to have some information on the cards) and the leafs are now +cards.
The structure looks like this [[foo]]->[[bar]]->bar+moo, bar+moo+cow, etc. So the main difference is that I have those in front like anchors. I'm still thinking what is the optimal structure, this is where I ended up for now.
Btw. the links for: DabbleDB, Google Squared are dead...