I've totally new to gremlin. I've been using yed (http://
www.yworks.com/en/products_yed_about.html) for a while for any diagram
related activity. Yed saves its data in graphml format and I've just
discovered gremlin could save graphs into this format also.
Unfortunately, a lot of information is left out of the grahml file as
yWorks is fairly rich.
So my question is just about the roadmap... Is it planned to add more
compatible serialization for getting nice view of graph ?
Thanks,
jg
PS I'm pleased to see Peyo's world has crawled up to graph (Gargamel
project) world. So why not Smurf (Schtroumpf) instead of Gremlins??!
Anders Nawroth found another interesting visualization JavaScript lib
for graphviz files, http://www.ryandesign.com/canviz/ which renders
them directly on the client side. This would allow for both command
line tools and client side visualization, if only there can be some
more animation etc to the visualization. WDYAT?
Cheers,
/peter neubauer
COO and Sales, Neo Technology
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter http://twitter.com/peterneubauer
http://www.neo4j.org - Your high performance graph database.
http://www.tinkerpop.com - Processing for Internet-scale graphs.
http://www.thoughtmade.com - Scandinavias coolest Bring-a-Thing party.
> Yes, right now Gremlin is saving just rudimentary info in the GraphML
> files. feel free to extend that to a degree where they can hold even
> layout information!
No, Gremlin does not "just save rudimentary info".
Gremlin stores all the information that it has for every vertex and edge into the GraphML file. That is, if its a metadata property, its saved. If you want to add more data, simply add it as a key/value pair to an element. Likewise, when loading data from a GraphML file, it includes all the key/value pair data that is provided to it as vertex/edge metadata.
Please see: http://wiki.github.com/tinkerpop/blueprints/graphml-reader-and-writer-library
In short, the GraphML spec is fully implemented ----- save it does not provide support for nested and hyper graphs.
Take care,
Marko.
When you get some example with yed integration working, we would be
most interested to look at a demo!
Cheers,
/peter neubauer
COO and Sales, Neo Technology
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter http://twitter.com/peterneubauer
http://www.neo4j.org - Your high performance graph database.
http://www.tinkerpop.com - Processing for Internet-scale graphs.
http://www.thoughtmade.com - Scandinavias coolest Bring-a-Thing party.
For layout information, you can provide vertex metadata like this:
gremlin> $v/@x := 10.023
gremlin> $v/@y := 1.346
In other words, provide x/y metadata for laying out a graph in a plane. Then you can load the GraphML file in something like iGraph (http://igraph.sourceforge.net) and visualize it. However, if you are just interested in visualization, then Gremlin is perhaps not your tool -- Gremlin is good for graph traversals. I would recommend R:Statistics/iGraph as a great combo with lots of layout algorithms, visualization techniques in 2D/3D, etc.
Hope that helps,
Marko.
thanks a lot for your responses. So I guess it would be OK to add the
information required by yed through XSLT. I have to explore gremlin a
lot more!
jg
> >http://www.thoughtmade.com- Scandinavias coolest Bring-a-Thing party.
>
> > On Thu, Mar 4, 2010 at 8:49 PM, Marko Rodriguez <okramma...@gmail.com> wrote:
> >> Hi,
>
> >>> Yes, right now Gremlin is saving just rudimentary info in the GraphML
> >>> files. feel free to extend that to a degree where they can hold even
> >>> layout information!
>
> >> No, Gremlin does not "just save rudimentary info".
>
> >> Gremlin stores all the information that it has for every vertex and edge into the GraphML file. That is, if its a metadata property, its saved. If you want to add more data, simply add it as a key/value pair to an element. Likewise, when loading data from a GraphML file, it includes all the key/value pair data that is provided to it as vertex/edge metadata.
>
> >> Please see:http://wiki.github.com/tinkerpop/blueprints/graphml-reader-and-writer...