Hy all,
any idea how to implementd a hyperbolic browser in touch? Basically this site covers it
but of course more advanced, i.e. more levels, irregular placement …
Hy all,
any idea how to implementd a hyperbolic browser in touch? Basically this site covers it
but of course more advanced, i.e. more levels, irregular placement …
yah this would be a super cool thing to do in touch.
I’m keen to give this a go too but I can’t get my head around what it needs.
I have a map in Freemind xml format that I want to play around with different visualisations for but it’s sat on the back burner for a while now…
being able to browse a piece of music in mxml format would be pretty swasome too.
rod.
Just off the top of my under-slept head, you could have positions in the data space given weights then use blends to determine where the ‘thing’ actually comes to rest when all the weights are taken into account. It would be cool if each node could be a geometry component and generated by replicators etc. s truckload of spring SOPs could be a way to do it and have each one tied to stationary points at the boundaries of the apce and maybe the center as well.
anyway, not making sense, I know, just bouncing ideas and partly talking to myself. try and lure Felix into this conversation, something weird always happens when I do that.
Rod.
and achim’s link links on to this page: [url]http://thejit.org/[/url] a Javascript toolkit for info visualisation.
… and the same guy has been doing a weGL version of this stuff too…
[url]http://senchalabs.github.com/philogl/[/url] whup-ass touchDesigner in a browser (but quite a bit of code-learning to do what we spaghetti programmers do in Touch).
Rod.
here’s a way to do something like that
hyperbolicrender.toe (12.2 KB)
thx guys. the circular mapping is a good start, thx james.
I still wonder how to implement the (possibly infinite) structure of nodes and their connections. And how to automatically and inteligently move them around depending on selections…
And of course the springs? spring SOP wont work as i can efficiently create them on demand …
The other problem i see is how to create text on demand. Creating text TOPs at runtime will result in (small) freezes … updating a predefined set of 200 text TOPs might also cause a freeze if i need to update them all at once, especially if i need high resolutions of them (to support zooming)
Generally, i find that creating dynamic “structures” in touch very hard to do, but maybe im missing something?