2018-07-18 02:06:10 +02:00
|
|
|
# $NetBSD: Makefile,v 1.26 2018/07/18 00:06:21 joerg Exp $
|
Initial import of graphopt-0.1, a graph layout optimizer:
In contrast to Graphviz and other graph optimizers, graphopt does
not use a heuristic approach to layout optimization. Instead, it
uses basic principles of physics to iteratively determine optimal
layout. Each node is given mass and an electric charge, and each
edge is represented as a spring. Node mass, electric charge,
optimal spring length, and the spring constant are tweakable in
the gui in realtime.
For most graphs, this is all that is needed - hit 'go' and the
graph organizes itself much as the analagous real-life system would
if constrained to two dimensions. For more complex graphs, some
fiddling with the physical parameters at different stages of
optimization usually does the trick.
To accomodate very large graphs, an additional mechanism called
layering was added. When a graph is loaded, nodes are assigned to
layers based on their relative positions. During optimization,
you can choose to hide any number of layers. Any nodes assigned
to a layer lower than the selected layer are not only hidden, but
neither their electric charges nor the forces of the springs attached
to them are figured into the forces acting on the visible nodes.
In effect, those nodes cease to exist, and a smaller graph is
allowed to lay itself out without being constrained by an excessive
number of nodes.
2003-01-23 20:27:12 +01:00
|
|
|
#
|
|
|
|
|
|
2003-05-07 17:29:47 +02:00
|
|
|
DISTNAME= graphopt-0.4.1
|
2011-04-22 15:41:54 +02:00
|
|
|
PKGREVISION= 5
|
Initial import of graphopt-0.1, a graph layout optimizer:
In contrast to Graphviz and other graph optimizers, graphopt does
not use a heuristic approach to layout optimization. Instead, it
uses basic principles of physics to iteratively determine optimal
layout. Each node is given mass and an electric charge, and each
edge is represented as a spring. Node mass, electric charge,
optimal spring length, and the spring constant are tweakable in
the gui in realtime.
For most graphs, this is all that is needed - hit 'go' and the
graph organizes itself much as the analagous real-life system would
if constrained to two dimensions. For more complex graphs, some
fiddling with the physical parameters at different stages of
optimization usually does the trick.
To accomodate very large graphs, an additional mechanism called
layering was added. When a graph is loaded, nodes are assigned to
layers based on their relative positions. During optimization,
you can choose to hide any number of layers. Any nodes assigned
to a layer lower than the selected layer are not only hidden, but
neither their electric charges nor the forces of the springs attached
to them are figured into the forces acting on the visible nodes.
In effect, those nodes cease to exist, and a smaller graph is
allowed to lay itself out without being constrained by an excessive
number of nodes.
2003-01-23 20:27:12 +01:00
|
|
|
CATEGORIES= math graphics
|
2003-05-07 17:29:47 +02:00
|
|
|
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=graphopt/}
|
Initial import of graphopt-0.1, a graph layout optimizer:
In contrast to Graphviz and other graph optimizers, graphopt does
not use a heuristic approach to layout optimization. Instead, it
uses basic principles of physics to iteratively determine optimal
layout. Each node is given mass and an electric charge, and each
edge is represented as a spring. Node mass, electric charge,
optimal spring length, and the spring constant are tweakable in
the gui in realtime.
For most graphs, this is all that is needed - hit 'go' and the
graph organizes itself much as the analagous real-life system would
if constrained to two dimensions. For more complex graphs, some
fiddling with the physical parameters at different stages of
optimization usually does the trick.
To accomodate very large graphs, an additional mechanism called
layering was added. When a graph is loaded, nodes are assigned to
layers based on their relative positions. During optimization,
you can choose to hide any number of layers. Any nodes assigned
to a layer lower than the selected layer are not only hidden, but
neither their electric charges nor the forces of the springs attached
to them are figured into the forces acting on the visible nodes.
In effect, those nodes cease to exist, and a smaller graph is
allowed to lay itself out without being constrained by an excessive
number of nodes.
2003-01-23 20:27:12 +01:00
|
|
|
EXTRACT_SUFX= .tgz
|
|
|
|
|
|
2006-06-15 15:31:28 +02:00
|
|
|
MAINTAINER= pkgsrc-users@NetBSD.org
|
2017-08-16 22:21:03 +02:00
|
|
|
HOMEPAGE= https://sourceforge.net/projects/graphopt/
|
2003-07-21 18:56:41 +02:00
|
|
|
COMMENT= Optimize graph layouts
|
Initial import of graphopt-0.1, a graph layout optimizer:
In contrast to Graphviz and other graph optimizers, graphopt does
not use a heuristic approach to layout optimization. Instead, it
uses basic principles of physics to iteratively determine optimal
layout. Each node is given mass and an electric charge, and each
edge is represented as a spring. Node mass, electric charge,
optimal spring length, and the spring constant are tweakable in
the gui in realtime.
For most graphs, this is all that is needed - hit 'go' and the
graph organizes itself much as the analagous real-life system would
if constrained to two dimensions. For more complex graphs, some
fiddling with the physical parameters at different stages of
optimization usually does the trick.
To accomodate very large graphs, an additional mechanism called
layering was added. When a graph is loaded, nodes are assigned to
layers based on their relative positions. During optimization,
you can choose to hide any number of layers. Any nodes assigned
to a layer lower than the selected layer are not only hidden, but
neither their electric charges nor the forces of the springs attached
to them are figured into the forces acting on the visible nodes.
In effect, those nodes cease to exist, and a smaller graph is
allowed to lay itself out without being constrained by an excessive
number of nodes.
2003-01-23 20:27:12 +01:00
|
|
|
|
2018-07-18 02:06:10 +02:00
|
|
|
USE_LANGUAGES= c c++03
|
Initial import of graphopt-0.1, a graph layout optimizer:
In contrast to Graphviz and other graph optimizers, graphopt does
not use a heuristic approach to layout optimization. Instead, it
uses basic principles of physics to iteratively determine optimal
layout. Each node is given mass and an electric charge, and each
edge is represented as a spring. Node mass, electric charge,
optimal spring length, and the spring constant are tweakable in
the gui in realtime.
For most graphs, this is all that is needed - hit 'go' and the
graph organizes itself much as the analagous real-life system would
if constrained to two dimensions. For more complex graphs, some
fiddling with the physical parameters at different stages of
optimization usually does the trick.
To accomodate very large graphs, an additional mechanism called
layering was added. When a graph is loaded, nodes are assigned to
layers based on their relative positions. During optimization,
you can choose to hide any number of layers. Any nodes assigned
to a layer lower than the selected layer are not only hidden, but
neither their electric charges nor the forces of the springs attached
to them are figured into the forces acting on the visible nodes.
In effect, those nodes cease to exist, and a smaller graph is
allowed to lay itself out without being constrained by an excessive
number of nodes.
2003-01-23 20:27:12 +01:00
|
|
|
GNU_CONFIGURE= YES
|
|
|
|
|
|
|
|
|
|
post-install:
|
2009-12-11 18:47:28 +01:00
|
|
|
${INSTALL_DATA_DIR} ${DESTDIR}${PREFIX}/share/doc/graphopt
|
|
|
|
|
${INSTALL_DATA} ${WRKSRC}/README ${DESTDIR}${PREFIX}/share/doc/graphopt
|
Initial import of graphopt-0.1, a graph layout optimizer:
In contrast to Graphviz and other graph optimizers, graphopt does
not use a heuristic approach to layout optimization. Instead, it
uses basic principles of physics to iteratively determine optimal
layout. Each node is given mass and an electric charge, and each
edge is represented as a spring. Node mass, electric charge,
optimal spring length, and the spring constant are tweakable in
the gui in realtime.
For most graphs, this is all that is needed - hit 'go' and the
graph organizes itself much as the analagous real-life system would
if constrained to two dimensions. For more complex graphs, some
fiddling with the physical parameters at different stages of
optimization usually does the trick.
To accomodate very large graphs, an additional mechanism called
layering was added. When a graph is loaded, nodes are assigned to
layers based on their relative positions. During optimization,
you can choose to hide any number of layers. Any nodes assigned
to a layer lower than the selected layer are not only hidden, but
neither their electric charges nor the forces of the springs attached
to them are figured into the forces acting on the visible nodes.
In effect, those nodes cease to exist, and a smaller graph is
allowed to lay itself out without being constrained by an excessive
number of nodes.
2003-01-23 20:27:12 +01:00
|
|
|
|
2004-04-18 21:30:52 +02:00
|
|
|
.include "../../x11/gtk/buildlink3.mk"
|
Initial import of graphopt-0.1, a graph layout optimizer:
In contrast to Graphviz and other graph optimizers, graphopt does
not use a heuristic approach to layout optimization. Instead, it
uses basic principles of physics to iteratively determine optimal
layout. Each node is given mass and an electric charge, and each
edge is represented as a spring. Node mass, electric charge,
optimal spring length, and the spring constant are tweakable in
the gui in realtime.
For most graphs, this is all that is needed - hit 'go' and the
graph organizes itself much as the analagous real-life system would
if constrained to two dimensions. For more complex graphs, some
fiddling with the physical parameters at different stages of
optimization usually does the trick.
To accomodate very large graphs, an additional mechanism called
layering was added. When a graph is loaded, nodes are assigned to
layers based on their relative positions. During optimization,
you can choose to hide any number of layers. Any nodes assigned
to a layer lower than the selected layer are not only hidden, but
neither their electric charges nor the forces of the springs attached
to them are figured into the forces acting on the visible nodes.
In effect, those nodes cease to exist, and a smaller graph is
allowed to lay itself out without being constrained by an excessive
number of nodes.
2003-01-23 20:27:12 +01:00
|
|
|
.include "../../mk/bsd.pkg.mk"
|
