JSpec tests are cool. JSpec comes bundled in a ruby gem which you install and after that you get a command line runner for firing browsers, or rhino, and looking up syntax and doing other neat stuff to your test suite. It looks like a good project with steady releases and progress. Here’s an example of how a test looks with the DSL in action:
we write it like this.
The point is that I’m not sure I’m fond of this technique since I find the code to get a bit muddled and the “that” keyword has a strange ring to it. Next time round I’ll probably stick to the normal way of setting up objects.
I ended up with and object encapsulating the graph, one for the node, one wrapping the twitter API and lastly one wrapping neo4j-rest for storing and retrieving data. The code, if you’re interested can be found on github (very unpolished and probably won’t ever be polished so take it with a grain of salt or two).
Gephi is an open source tool for visualizing a graph using Open GL for fast and fancy rendering capabilities. A version released a short time ago (get it here) has support for connecting directly to a (sadly, not running) instance of Neo4J and import the whole graph.
For this little pet project the main focus for using Gephi was to test it out and see how it works, but the potential is huge for graphs with more data in them. Gephi can do all sorts of graph manipulation and analysis and showing the graph according to values stored in the nodes etc. In the twitter graph I stored the number of followers in each of my followers as a number and Gephi could easily be configured to draw the node size relative to that, color edges based on data and much more. And all in nice openGL smooth graphics performance.