A little bit of topic, but why is the module Graphics.Ubigraph hidden in your package? I've been trying to use Ubigraph directly, and your module helped me a lot. (I just patched the cabal file to expose Graphics.Ubigraph as well)

Is there a specific reason for it to be hidden?

As far as I know, there is another wrapper for Ubigraph in Haskell, Hubigraph[1], but it's not on hackage. (licensing issues?) Your module contains all the basics, and should be enough in general.

[1] http://ooxo.org/hubigraph/index.html

Best,
Ozgur

On 13 May 2010 10:32, Ozgur Akgun <ozgurakgun@gmail.com> wrote:
Thanks! It looks better now!

PS: I actually knew about the oriented attribute, but I thought this might be something else. Anyway..

On 13 May 2010 09:23, Gleb Alexeyev <gleb.alexeev@gmail.com> wrote:
Ozgur Akgun wrote:
Thanks for the answer.

I see your point, that Ubigraph does some magic* to place vertices and
edges.
This makes me wonder, how they generate the binary tree demo:
http://ubietylab.net/ubigraph/content/Demos/random_binary_tree.html
Is there a way to disable this optimal graph layout determination process?

Best,
Ozgur


Ozgur,
I've just compared the way vacuum-ubigraph visualizes binary trees to the random_binary_tree demo and found that I had missed an important edge attribute called "oriented", it seems to produce the output you want.

I hope to upload the new package version soon, meanwhile you can do the following (assuming you use Linux):

cabal unpack vacuum-ubigraph
patch -d vacuum-ubigraph-0.1.0.3/ -p 1 < vacuum-ubigraph-oriented.patch
cd vacuum-ubigraph-0.1.0.3
cabal configure && cabal build && cabal install

_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe




--
Ozgur Akgun



--
Ozgur Akgun