Hi, is there someone doing like this http://cs.joensuu.fi/jeliot/description.php in ruby? if not, it would be great as a SoC project (w universal plugin to editors and supports outputs including asciitext/curses). This will be very useful for ruby beginners and those who would like to study ruby-written frameworks like rails :) kind regards -botp
on 2007-03-26 06:56
on 2007-03-26 09:02
Hmmm, the visualization itself seems like it will be very messy on implementation deisions. How about a visualization where you see the code and animation over it, with smooth zooming where needed (out and then in, not just up or down, that works better to show the user where in the code the result is), and for stuff that can't be found in the code, just have the text zoom towards the viewer while becoming transparent until it escapes the screen? Easy to do if you know a bit of OpenGL. Great to follow along. The Ruby part is easy since writing profilers is so trivial in Ruby. It'll greatly benefit the community. IMHO. Anyone up for it?
on 2007-03-26 09:56
From: SonOfLilit [mailto:email@example.com] : # The Ruby part is easy since writing profilers is so trivial in Ruby. i cannot wait on how one would picture method_missing, meta methods that magically springs into existence, and garbage collection; maybe picture them w balloons, magic wands, and witch brooms :)) # It'll greatly benefit the community. IMHO. indeed. ultimately, assumming one could come up w a generic multi-language visualizer, it would be one of the best tools to use to study a language. a killer app, imho. kind regards -botp
on 2007-03-26 10:47
A generic language visualiser won't be. It just won't, IMHO, since language execution models are so different. A framework for language visualization that does the graphics and lets you tell it how to visualize would be possible, tho. I can easily tell you how method_missing would be visualised: you'd see the call to method_missing, like any other call to code that is written out in the .rb files. Methods that don't exist in code, like those created by metaprogramming, would be visualised as I described - they method name and parameters would zoom towards the camera and dissapear. Garbage collection is simple to visualize - collected objects just fade away, if any memory visualization is done (which with my first proposal isn't the case). It will indeed greatly benefit the community. Anyone up for the task?