Hi Simone,
While rearranging stuff to prepare the merge, I noticed that the
NamedExportSelector disappeared in favor of specifying the graph name
inside the usingXXXFormat() method.
I honestly think that in that way it lost part of the expressiveness -
even if it is less verbose.
I am in
Hi Claud.io,
which becomes something like:
export( actual ).usingDotNotation().withName( my graph )
.withVertexLabels( new VertexLabelMapper() )
.withEdgeWeights( new EdgeWeightMapper() )
.withEdgeLabels( new
branches reintegrated, have a good work!
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Sun, Mar 25, 2012 at 1:22 PM, Simone Tripodi
simonetrip...@apache.org wrote:
Hi Claud.io,
which becomes
Hi all guys,
in order to speedup things, I'd propose to reintegrate the
experimental branch[1] where Claudio finalized my work of dropping the
Vertex/Edge (and few other) marker interfaces, defining a clean set of
abstract APIs for the graph exporter.
Reintegrating the branch on trunk implies
Hi,
we could merge the branch and open some issues on Jira to track the
exporter problems, so people can contribute to fix them.
ciao
--
Marco Speranza marcospera...@apache.org
Google Code: http://code.google.com/u/marco.speranza79/
2012/3/23 Simone Tripodi simonetrip...@apache.org:
Hi all
Hi,
we could merge the branch and open some issues on Jira to track the
exporter problems, so people can contribute to fix them.
+1.
Note that the exporters are not complete yet, and there are still
interesting architectural decisions left unanswered.
Let's go for it!
Claudio
--
Claudio
While rearranging stuff to prepare the merge, I noticed that the
NamedExportSelector disappeared in favor of specifying the graph name
inside the usingXXXFormat() method.
I honestly think that in that way it lost part of the expressiveness -
even if it is less verbose.
I am in favor of having it
