Comments for Tulip
Tulip Forum and Bug report on sourceforge
Management of bug reports, new features and forum is
now available for Tulip on Sourceforge. The new 2.0.0
version includes a lot of new features, we need your help
to test it. Feel free to give comment on the new HCI.
URL: sourceforge.net/projects/auber (sorry for the project's
name but tulip was already taken on freshmeat :-( )
Thanks for your help since the begining.
David Auber
Very powerful, but a bit rough
Tulip is indeed a very powerful tool, but does suffer from a few problems.
- there is no developer's mailing list
- you have to go through a silly interface on their web site to get source tar balls (unless you go through freshmeat)
- there's no programmer's documentation
- there's no file format documentation
Mind, that's almost a nit all the formats, except for the native Tulip format, are fairly easy to reverse engineer. Note, however, that GML does *not* stand for Geographic Markup Language as I initially thought; GML is an acronym for Graph Modelling Language. You can get more information on that file format at www.infosun.fmi.uni-pa....
Reading information garnered at that site I learned that Tulip supports a simple subset of GML and not the entire language. Morever, as with all the other file formats, the Tulip GML importer uses a hand-written lexer and parser and not, say, lex and yacc. Again, this isn't egregious, but in my experience this raises a red flag.
- user interface design is ad hoc and difficult to use
Why have the initial dialog that has per graph functionality (and buttons X-ed out) when that makes more sense to have that functionality soley on the graph dialog?
- use of void*'s is Evil
- Code comments? WHAT code comments? Hell, I'll even take the French over nothing. Murd!
- there is a LOT of member data in class public and protected sections
Still it's a potent tool, but it can be infuriating to use and develop for.
Really powerful and flexible
I'm really happy to have found such a powerful tool:
I'm working in Biocomputing and I'm used to deal with huge graphs (100000 nodes) to represent biological behaviours such as metabolical pathways.
It's also really easy to implement ad-hoc layout/graph management plug-ins to focus on what really matters to oneself.
The tlp format is something we've been waiting for years: as flexible as XML, but far more compact and cleverly designed.
With the efficient memory management, it's also really easy to manipulate many graphs at once in order to compare them, like in molecular 3D structure comparison.
Tulip: A nice program for graph visualisation.
Hello,
I try Tulip for watching complex systems behavoirs,
and i'm glade to see that it's very fast.
You can easily manipulate sub-graphs to have other views.
The software have power tools like clustering or property management.
I encourage other people to make other plugings to enhance the software capabilities.
Re: Very powerful, but a bit rough
> - there is no developer's mailing list
One is available on sourceforge.
> - you have to go through a silly
> interface on their web site
I need to have some feed back from people that use
Tulip. It is not silly !
> - there's no programmer's documentation
Use doxygen on the source code you will have some.
> - there's no file format documentation
See the web page of Tulip.
> Mind, that's almost a nit all the
> formats, except for the native Tulip
> format, are fairly easy to reverse
> engineer.
I don't think that you have open a tlp file. It is text
using Lisp syntax and behavior.
%Note, however, that GML does
> *not* stand for Geographic Markup
> Language
Tulip is a graph visualization software not a
Geographic map viewer.
> Reading information garnered at that
> site I learned that Tulip supports a
> simple subset of GML and not the entire
> language. Morever, as with all the
> other file formats, the Tulip GML
> importer uses a hand-written lexer and
> parser and not, say, lex and yacc.
I do not use lex and yacc because it is too slow for
the size of graph we want to import. From my
knowledge all the basic properties of the GML format
are supported, others properties are specific to
Graphlet.
> - user interface design is ad hoc and
> difficult to use
Give me some idea... Version 2.0.0 uses MDI
interface that should be more easy to use.
> - use of void*'s is Evil
Why does it exist ? There is not a lot of void* in Tulip
instead when we are using typeinfo mechanism. I
don't think that it is possible to remove them without
building a silly and unefficient hierachy of classes.
> - Code comments? WHAT code comments?
> Hell, I'll even take the French over
> nothing. Murd!
Read XP programming... If the code is well done with
good name function we do not need code comment.
> - there is a LOT of member data in class
> public and protected sections
You are right, some refactoring is needed.
> Still it's a potent tool, but it can be
> infuriating to use and develop for.
It is your point of view. A lot of people are using Tulip
and are programming with it.