Projects tagged ‘dot’ and ‘graphviz’

A fluent interface for .NET for generating graphs with GraphViz.

A Java binding for Grahphviz built on top of the existing SWIG-generated api. This provides a more flexible object-oriented interface to the graph model, and support for rendering the generated graphs using GEF/draw2d.

visualdot is a simple GUI tool that lets you edit .dot files ,run dot, neato, or twopi on the .dot source and see a preview of the graph output. It assumes dot, neato, and twopi(and other graphviz ... [More] tools) have already been installed via MacPorts. The user can drag and drop an existing .dot file or edit inside the app. See the visualdot online help for more info. [Less]

This is the homepage of pydot, a Python interface to Graphviz's Dot language. pydot allows to easily create both directed and non directed graphs from Python. Currently all attributes implemented in ... [More] the Dot language are supported (up to Graphviz 2.16). Output can be inlined in Postscript into interactive scientific environments like TeXmacs, or output in any of the format's supported by the Graphviz tools dot, neato, twopi. Requirementspyparsing in order to load DOT files. Graphviz to render the graphs. ChangelogThe release 1.0.2 of pydot boasts the following: The parser has been improved a lot. It passes all of GraphViz's regression tests (which I consider quite an accomplishment seeing the kind of crazy constructs on those ) Different charsets should now be dealt with properly. The search of GraphViz's executables has been improved for all platforms. On Windows, paths and registry keys are searched. On Unix now it should exhibit the same behavior as the traditional shell path search. (Thanks Andy Gimblett and many others) Double-quoted paths in Windows are nor properly handled. The os.path.exists() check fails if a valid path is enclosed within quotes. 'type' keyword has been changed everywhere to 'graph_type' Better handling of Node/Edge/Graph defaults. Added methods: set_graph_defaults, set_node_defaults, set_edge_defaults, get_graph_defaults, get_node_defaults, get_edge_defaults Now it's possible to use rank to lay out nodes at the same level graph = pydot.Dot('graphname', graph_type='digraph') subg = pydot.Subgraph('', rank='same') subg.add_node(pydot.Node('a')) graph.add_subgraph(subg) subg.add_node(pydot.Node('b')) subg.add_node(pydot.Node('c')) Multiple main graphs in a file are now supported, will be returned as a list of graph instances Handling of shapefiles Dot().set_shape_files() Added method "add_style()" to the Node class to easily append styles to a node Attribute lists updated to reflect the available ones in graphviz 2.16 Added error reporting when rendering graphs with GraphViz executables. There was an often reported problem where the output graphs would have 0 size. In most cases this was due to Graphviz missing a library for a format that pydot assumed to be there. Now the error given by the executable will be reported instead of being silently ignored (Thanks Jarno) Improved parsing of identifiers Added non-GraphViz attributes needed by dot2tex Jose Fonseca contributed a fix dealing with quoted strings the the dot parsing module setup.py updated so that it's possible to install pydot through Setuptools' easy_install Edge()'s can be created passing two Node objects as well as, the previously supported, two strings with node names. Warning: when passing two Node instances, the attributes won't be taken into account. The edge will only read the Nodes' names to create an edge, the Nodes must be separately added to the graph so all their attributes are "remembered". Substituted all str()'s for unicode()'s It's possible now to manually specify the path to GraphViz's executables in the case they can't be found automatically. The method 'set_graphviz_executables(paths)' will take a dictionary specifying the location of the executables. Please refer to the documentation for usage detailed information. And too many bugfixes to list... Performance: The new pydot stores graphs and their objects using a hierarchy of nested dictionaries and lists. Graph, Node, Edge objects are mere proxies to the data and are created on demand. So that now it's possible to have a graph with a 1 million edges and there will not be a single Edge instance (only if requested, then they will be created on demand, mapping the data and providing with all the methods to act on the data in the global dictionary). Storing a graph with 1 million edges in pydot 1.0 has approximately the same memory requirements (~813MiB) as dealing with one with only 40.000 edges in pydot 0.9 (~851MiB), the 40.000 edges graph needs ~35MiB in pydot 1.0 . Handling graphs should be much faster, as no linear searches are performed in pydot 1.0 Related Projectsdot2tex XDot [Less]

QDotFeatures: AutoCompletition Some wizards to element insertion CrossPlatform

一个分析python代码结构的工具，后端先通过dot生成png吧。

A Macintosh application that creates graphviz diagrams from a folder's contents.

Command line tool for finding dependencies between classes, outputting dependencies to GraphViz dot configuration files.

TIMEGRAPHItems in the enterprise have dependencies and relationships of different types. They also have temporal relations to each other. Examples are projects, technical roadmaps, departments ... [More] , roles, applications, rollouts etc etc etc. Each person that tackles this problem tackles this in a different manner. They use Visio and/or Excel to create their artifacts and then print this out. Thus, the information is kept and stored in the desktop of that specific person, and is lost to the overall big picture. How would you correlate information across domains, across people, departments etc.? This requires lots of meetings, cross-references. Tools that do this are very complicated, cost hundreds of thousands of dollars, requires years of training or costly consultants. Once implemented, they are difficult to maintain without costing a huge bundle. Take CONTROL. Use TIMEGRAPH FAQQ. How do we make this available for viewing consistently throughout the enterprise? Q. How do we make this uniform and make the creation of this information easy, consistent and available in an enterprise repository? Q. How do we make the source information versioned? Q. How we make this information? A. To all of the above, use "TIMEGRAPH". Store your information in a CMS like Sharepoint or Confluence and use timegraph to generate the website for you for communicating the information. This way, your information is versioned in a repository of your choice, and the website communicates your info across the intranet or the internet. Deploy "timegraph" in a java appserver of your choice. How do we depict this is a common and consistent manner? This is usually done using Visio or Excel or other tools and requires a lot of manual effort. Also to make them available over the intranet/internet requires a lot of effort. This project allows you to author CSV files using Excel or OpenOffice and generates the website that shows the graphical and timeline views of your items. Please see the blog and wiki for more details. [Less]

一个分析python代码结构的工具。