dnrops
/
gimp
mirror of https://github.com/GNOME/gimp.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
gimp/devel-docs/gimp-module-dependencies.svg

394 lines
24 KiB
XML
Raw Permalink Normal View History

devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
"http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<!-- Generated by graphviz version 2.26.3 (20100126.1600)
-->
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
<!-- Title: _anonymous_0 Pages: 1 -->
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<svg width="862pt" height="1008pt"
viewBox="0.00 0.00 862.00 1008.00" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<g id="graph1" class="graph" transform="scale(1 1) rotate(0) translate(4 1004)">
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
<title>_anonymous_0</title>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<polygon fill="white" stroke="white" points="-4,5 -4,-1004 859,-1004 859,5 -4,5"/>
<!-- app/plug&#45;in -->
<g id="node1" class="node"><title>app/plug&#45;in</title>
<ellipse fill="lawngreen" stroke="black" cx="128" cy="-981" rx="55.8614" ry="19.0919"/>
<text text-anchor="middle" x="128" y="-977.9" font-family="Times Roman,serif" font-size="14.00">app/plug&#45;in</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/composite -->
<g id="node2" class="node"><title>app/composite</title>
<ellipse fill="lawngreen" stroke="black" cx="176" cy="-907" rx="67.8823" ry="19.0919"/>
<text text-anchor="middle" x="176" y="-903.9" font-family="Times Roman,serif" font-size="14.00">app/composite</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/plug&#45;in&#45;&gt;app/composite -->
<g id="edge2" class="edge"><title>app/plug&#45;in&#45;&gt;app/composite</title>
<path fill="none" stroke="black" d="M140.112,-962.327C145.585,-953.891 152.16,-943.754 158.178,-934.475"/>
<polygon fill="black" stroke="black" points="161.219,-936.219 163.724,-925.925 155.346,-932.41 161.219,-936.219"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/base -->
<g id="node4" class="node"><title>app/base</title>
<ellipse fill="lawngreen" stroke="black" cx="285" cy="-833" rx="44.7575" ry="19.0919"/>
<text text-anchor="middle" x="285" y="-829.9" font-family="Times Roman,serif" font-size="14.00">app/base</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/composite&#45;&gt;app/base -->
<g id="edge4" class="edge"><title>app/composite&#45;&gt;app/base</title>
<path fill="none" stroke="black" d="M202.108,-889.275C217.2,-879.029 236.322,-866.047 252.396,-855.135"/>
<polygon fill="black" stroke="black" points="254.66,-857.828 260.968,-849.315 250.728,-852.037 254.66,-857.828"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/config -->
<g id="node11" class="node"><title>app/config</title>
<ellipse fill="lawngreen" stroke="black" cx="311" cy="-759" rx="51.8276" ry="19.0919"/>
<text text-anchor="middle" x="311" y="-755.9" font-family="Times Roman,serif" font-size="14.00">app/config</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/base&#45;&gt;app/config -->
<g id="edge10" class="edge"><title>app/base&#45;&gt;app/config</title>
<path fill="none" stroke="black" d="M291.696,-813.943C294.516,-805.916 297.859,-796.402 300.964,-787.565"/>
<polygon fill="black" stroke="black" points="304.314,-788.587 304.327,-777.992 297.71,-786.267 304.314,-788.587"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- libgimpcolor -->
<g id="node6" class="node"><title>libgimpcolor</title>
<ellipse fill="#ff7256" stroke="black" cx="418" cy="-167" rx="61.0181" ry="19.0919"/>
<text text-anchor="middle" x="418" y="-163.9" font-family="Times Roman,serif" font-size="14.00">libgimpcolor</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- libgimpmath -->
<g id="node7" class="node"><title>libgimpmath</title>
<ellipse fill="#ff7256" stroke="black" cx="418" cy="-93" rx="61.0181" ry="19.0919"/>
<text text-anchor="middle" x="418" y="-89.9" font-family="Times Roman,serif" font-size="14.00">libgimpmath</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- libgimpcolor&#45;&gt;libgimpmath -->
<g id="edge6" class="edge"><title>libgimpcolor&#45;&gt;libgimpmath</title>
<path fill="none" stroke="black" d="M418,-147.943C418,-140.149 418,-130.954 418,-122.338"/>
<polygon fill="black" stroke="black" points="421.5,-122.249 418,-112.249 414.5,-122.249 421.5,-122.249"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- GLib -->
<g id="node9" class="node"><title>GLib</title>
<ellipse fill="lightblue" stroke="black" cx="418" cy="-19" rx="31.8198" ry="19.0919"/>
<text text-anchor="middle" x="418" y="-15.9" font-family="Times Roman,serif" font-size="14.00">GLib</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- libgimpmath&#45;&gt;GLib -->
<g id="edge8" class="edge"><title>libgimpmath&#45;&gt;GLib</title>
<path fill="none" stroke="black" d="M418,-73.9432C418,-66.1493 418,-56.9538 418,-48.3381"/>
<polygon fill="black" stroke="black" points="421.5,-48.2494 418,-38.2495 414.5,-48.2495 421.5,-48.2494"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/core -->
<g id="node14" class="node"><title>app/core</title>
<ellipse fill="lawngreen" stroke="black" cx="336" cy="-685" rx="44.0472" ry="19.0919"/>
<text text-anchor="middle" x="336" y="-681.9" font-family="Times Roman,serif" font-size="14.00">app/core</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/config&#45;&gt;app/core -->
<g id="edge26" class="edge"><title>app/config&#45;&gt;app/core</title>
<path fill="none" stroke="black" d="M317.438,-739.943C320.15,-731.916 323.364,-722.402 326.35,-713.565"/>
<polygon fill="black" stroke="black" points="329.699,-714.586 329.584,-703.992 323.067,-712.346 329.699,-714.586"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- GEGL -->
<g id="node13" class="node"><title>GEGL</title>
<ellipse fill="lightblue" stroke="black" cx="339" cy="-315" rx="36.977" ry="19.0919"/>
<text text-anchor="middle" x="339" y="-311.9" font-family="Times Roman,serif" font-size="14.00">GEGL</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/pdb -->
<g id="node15" class="node"><title>app/pdb</title>
<ellipse fill="lawngreen" stroke="black" cx="232" cy="-611" rx="41.9273" ry="19.0919"/>
<text text-anchor="middle" x="232" y="-607.9" font-family="Times Roman,serif" font-size="14.00">app/pdb</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/core&#45;&gt;app/pdb -->
<g id="edge12" class="edge"><title>app/core&#45;&gt;app/pdb</title>
<path fill="none" stroke="black" d="M312.919,-668.577C298.276,-658.158 279.148,-644.548 263.166,-633.176"/>
<polygon fill="black" stroke="black" points="264.836,-630.068 254.659,-627.122 260.777,-635.772 264.836,-630.068"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/gegl -->
<g id="node17" class="node"><title>app/gegl</title>
<ellipse fill="lawngreen" stroke="black" cx="336" cy="-611" rx="44.0472" ry="19.0919"/>
<text text-anchor="middle" x="336" y="-607.9" font-family="Times Roman,serif" font-size="14.00">app/gegl</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/core&#45;&gt;app/gegl -->
<g id="edge14" class="edge"><title>app/core&#45;&gt;app/gegl</title>
<path fill="none" stroke="black" d="M330.012,-665.943C329.288,-658.088 329.08,-648.81 329.387,-640.136"/>
<polygon fill="black" stroke="black" points="332.891,-640.19 330.018,-629.992 325.904,-639.756 332.891,-640.19"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/xcf -->
<g id="node19" class="node"><title>app/xcf</title>
<ellipse fill="lawngreen" stroke="black" cx="438" cy="-611" rx="39.8075" ry="19.0919"/>
<text text-anchor="middle" x="438" y="-607.9" font-family="Times Roman,serif" font-size="14.00">app/xcf</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/core&#45;&gt;app/xcf -->
<g id="edge16" class="edge"><title>app/core&#45;&gt;app/xcf</title>
<path fill="none" stroke="black" d="M358.637,-668.577C372.998,-658.158 391.759,-644.548 407.434,-633.176"/>
<polygon fill="black" stroke="black" points="409.738,-635.828 415.777,-627.122 405.628,-630.162 409.738,-635.828"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
<!-- app/file -->
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<g id="node21" class="node"><title>app/file</title>
<ellipse fill="lawngreen" stroke="black" cx="80" cy="-537" rx="41.0122" ry="19.0919"/>
<text text-anchor="middle" x="80" y="-533.9" font-family="Times Roman,serif" font-size="14.00">app/file</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/pdb&#45;&gt;app/file -->
<g id="edge18" class="edge"><title>app/pdb&#45;&gt;app/file</title>
<path fill="none" stroke="black" d="M203.41,-597.081C179.101,-585.246 144.017,-568.166 117.466,-555.24"/>
<polygon fill="black" stroke="black" points="118.985,-552.087 108.462,-550.856 115.921,-558.381 118.985,-552.087"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- libgimpmodule -->
<g id="node23" class="node"><title>libgimpmodule</title>
<ellipse fill="#ff7256" stroke="black" cx="413" cy="-537" rx="70.9184" ry="19.0919"/>
<text text-anchor="middle" x="413" y="-533.9" font-family="Times Roman,serif" font-size="14.00">libgimpmodule</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/pdb&#45;&gt;libgimpmodule -->
<g id="edge20" class="edge"><title>app/pdb&#45;&gt;libgimpmodule</title>
<path fill="none" stroke="black" d="M263.528,-598.11C291.34,-586.739 332.313,-569.988 364.331,-556.898"/>
<polygon fill="black" stroke="black" points="366.024,-559.987 373.955,-552.963 363.375,-553.508 366.024,-559.987"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/gegl&#45;&gt;app/core -->
<g id="edge22" class="edge"><title>app/gegl&#45;&gt;app/core</title>
<path fill="none" stroke="black" d="M341.982,-629.992C342.709,-637.839 342.92,-647.115 342.615,-655.792"/>
<polygon fill="black" stroke="black" points="339.111,-655.746 341.988,-665.943 346.098,-656.178 339.111,-655.746"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/text -->
<g id="node26" class="node"><title>app/text</title>
<ellipse fill="lawngreen" stroke="black" cx="282" cy="-537" rx="41.9273" ry="19.0919"/>
<text text-anchor="middle" x="282" y="-533.9" font-family="Times Roman,serif" font-size="14.00">app/text</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/xcf&#45;&gt;app/text -->
<g id="edge24" class="edge"><title>app/xcf&#45;&gt;app/text</title>
<path fill="none" stroke="black" d="M409.387,-597.427C384.444,-585.595 348.056,-568.334 320.55,-555.287"/>
<polygon fill="black" stroke="black" points="321.76,-551.987 311.225,-550.863 318.76,-558.311 321.76,-551.987"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/file&#45;&gt;app/plug&#45;in -->
<g id="edge32" class="edge"><title>app/file&#45;&gt;app/plug&#45;in</title>
<path fill="none" stroke="black" d="M80,-556.158C80,-584.37 80,-638.75 80,-685 80,-833 80,-833 80,-833 80,-875.187 84.7969,-886.276 99,-926 102.309,-935.256 106.934,-944.886 111.519,-953.453"/>
<polygon fill="black" stroke="black" points="108.498,-955.223 116.415,-962.264 114.617,-951.823 108.498,-955.223"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- libgimpthumb -->
<g id="node34" class="node"><title>libgimpthumb</title>
<ellipse fill="#ff7256" stroke="black" cx="67" cy="-389" rx="67.1751" ry="19.0919"/>
<text text-anchor="middle" x="67" y="-385.9" font-family="Times Roman,serif" font-size="14.00">libgimpthumb</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/file&#45;&gt;libgimpthumb -->
<g id="edge34" class="edge"><title>app/file&#45;&gt;libgimpthumb</title>
<path fill="none" stroke="black" d="M78.3271,-517.955C76.1162,-492.784 72.1982,-448.18 69.5998,-418.598"/>
<polygon fill="black" stroke="black" points="73.0694,-418.098 68.7078,-408.442 66.0963,-418.71 73.0694,-418.098"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- libgimpbase -->
<g id="node29" class="node"><title>libgimpbase</title>
<ellipse fill="#ff7256" stroke="black" cx="418" cy="-241" rx="58.1882" ry="19.0919"/>
<text text-anchor="middle" x="418" y="-237.9" font-family="Times Roman,serif" font-size="14.00">libgimpbase</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- libgimpmodule&#45;&gt;libgimpbase -->
<g id="edge36" class="edge"><title>libgimpmodule&#45;&gt;libgimpbase</title>
<path fill="none" stroke="black" d="M413.328,-517.579C414.183,-466.967 416.483,-330.777 417.503,-270.452"/>
<polygon fill="black" stroke="black" points="421.008,-270.166 417.677,-260.108 414.009,-270.048 421.008,-270.166"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/vectors -->
<g id="node56" class="node"><title>app/vectors</title>
<ellipse fill="lawngreen" stroke="black" cx="334" cy="-463" rx="55.8614" ry="19.0919"/>
<text text-anchor="middle" x="334" y="-459.9" font-family="Times Roman,serif" font-size="14.00">app/vectors</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/text&#45;&gt;app/vectors -->
<g id="edge76" class="edge"><title>app/text&#45;&gt;app/vectors</title>
<path fill="none" stroke="black" d="M294.854,-518.708C300.933,-510.057 308.313,-499.554 315.02,-490.01"/>
<polygon fill="black" stroke="black" points="318.047,-491.79 320.933,-481.596 312.32,-487.765 318.047,-491.79"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- Pango -->
<g id="node70" class="node"><title>Pango</title>
<ellipse fill="lightblue" stroke="black" cx="225" cy="-463" rx="34.8574" ry="19.0919"/>
<text text-anchor="middle" x="225" y="-459.9" font-family="Times Roman,serif" font-size="14.00">Pango</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/text&#45;&gt;Pango -->
<g id="edge78" class="edge"><title>app/text&#45;&gt;Pango</title>
<path fill="none" stroke="black" d="M267.91,-518.708C260.905,-509.613 252.323,-498.471 244.679,-488.549"/>
<polygon fill="black" stroke="black" points="247.41,-486.359 238.535,-480.572 241.865,-490.63 247.41,-486.359"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- libgimpbase&#45;&gt;libgimpcolor -->
<g id="edge28" class="edge"><title>libgimpbase&#45;&gt;libgimpcolor</title>
<path fill="none" stroke="black" d="M418,-221.943C418,-214.149 418,-204.954 418,-196.338"/>
<polygon fill="black" stroke="black" points="421.5,-196.249 418,-186.249 414.5,-196.249 421.5,-196.249"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- libgimpconfig -->
<g id="node31" class="node"><title>libgimpconfig</title>
<ellipse fill="#ff7256" stroke="black" cx="512" cy="-315" rx="65.9683" ry="19.0919"/>
<text text-anchor="middle" x="512" y="-311.9" font-family="Times Roman,serif" font-size="14.00">libgimpconfig</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- libgimpconfig&#45;&gt;libgimpbase -->
<g id="edge30" class="edge"><title>libgimpconfig&#45;&gt;libgimpbase</title>
<path fill="none" stroke="black" d="M489.245,-297.087C477.006,-287.452 461.747,-275.439 448.493,-265.005"/>
<polygon fill="black" stroke="black" points="450.568,-262.184 440.545,-258.748 446.238,-267.684 450.568,-262.184"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- libgimpthumb&#45;&gt;libgimpbase -->
<g id="edge38" class="edge"><title>libgimpthumb&#45;&gt;libgimpbase</title>
<path fill="none" stroke="black" d="M72.6671,-369.993C80.1177,-348.474 95.3615,-314.069 121,-296 157.281,-270.43 275.454,-254.627 351.346,-246.855"/>
<polygon fill="black" stroke="black" points="352.16,-250.291 361.761,-245.811 351.462,-243.326 352.16,-250.291"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- Cairo -->
<g id="node38" class="node"><title>Cairo</title>
<ellipse fill="lightblue" stroke="black" cx="241" cy="-389" rx="33.234" ry="19.0919"/>
<text text-anchor="middle" x="241" y="-385.9" font-family="Times Roman,serif" font-size="14.00">Cairo</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/actions -->
<g id="node39" class="node"><title>app/actions</title>
<ellipse fill="lawngreen" stroke="black" cx="799" cy="-315" rx="55.1543" ry="19.0919"/>
<text text-anchor="middle" x="799" y="-311.9" font-family="Times Roman,serif" font-size="14.00">app/actions</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/dialogs -->
<g id="node40" class="node"><title>app/dialogs</title>
<ellipse fill="lawngreen" stroke="black" cx="756" cy="-685" rx="55.8614" ry="19.0919"/>
<text text-anchor="middle" x="756" y="-681.9" font-family="Times Roman,serif" font-size="14.00">app/dialogs</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/actions&#45;&gt;app/dialogs -->
<g id="edge40" class="edge"><title>app/actions&#45;&gt;app/dialogs</title>
<path fill="none" stroke="black" d="M807.896,-334.161C819.955,-361.932 840,-415.275 840,-463 840,-537 840,-537 840,-537 840,-581.164 827.852,-592.208 805,-630 798.654,-640.495 790.185,-650.846 782.075,-659.688"/>
<polygon fill="black" stroke="black" points="779.448,-657.372 775.103,-667.035 784.526,-662.19 779.448,-657.372"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/gui -->
<g id="node42" class="node"><title>app/gui</title>
<ellipse fill="lawngreen" stroke="black" cx="756" cy="-611" rx="39.8075" ry="19.0919"/>
<text text-anchor="middle" x="756" y="-607.9" font-family="Times Roman,serif" font-size="14.00">app/gui</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/dialogs&#45;&gt;app/gui -->
<g id="edge42" class="edge"><title>app/dialogs&#45;&gt;app/gui</title>
<path fill="none" stroke="black" d="M756,-665.943C756,-658.149 756,-648.954 756,-640.338"/>
<polygon fill="black" stroke="black" points="759.5,-640.249 756,-630.249 752.5,-640.249 759.5,-640.249"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/display -->
<g id="node44" class="node"><title>app/display</title>
<ellipse fill="lawngreen" stroke="black" cx="756" cy="-537" rx="55.8614" ry="19.0919"/>
<text text-anchor="middle" x="756" y="-533.9" font-family="Times Roman,serif" font-size="14.00">app/display</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/gui&#45;&gt;app/display -->
<g id="edge44" class="edge"><title>app/gui&#45;&gt;app/display</title>
<path fill="none" stroke="black" d="M756,-591.943C756,-584.149 756,-574.954 756,-566.338"/>
<polygon fill="black" stroke="black" points="759.5,-566.249 756,-556.249 752.5,-566.249 759.5,-566.249"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/widgets -->
<g id="node50" class="node"><title>app/widgets</title>
<ellipse fill="lawngreen" stroke="black" cx="754" cy="-463" rx="57.9828" ry="19.0919"/>
<text text-anchor="middle" x="754" y="-459.9" font-family="Times Roman,serif" font-size="14.00">app/widgets</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/display&#45;&gt;app/widgets -->
<g id="edge50" class="edge"><title>app/display&#45;&gt;app/widgets</title>
<path fill="none" stroke="black" d="M755.485,-517.943C755.274,-510.149 755.026,-500.954 754.793,-492.338"/>
<polygon fill="black" stroke="black" points="758.289,-492.151 754.52,-482.249 751.292,-492.34 758.289,-492.151"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- libgimpwidgets -->
<g id="node46" class="node"><title>libgimpwidgets</title>
<ellipse fill="#ff7256" stroke="black" cx="573" cy="-537" rx="70.9184" ry="19.0919"/>
<text text-anchor="middle" x="573" y="-533.9" font-family="Times Roman,serif" font-size="14.00">libgimpwidgets</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- libgimpwidgets&#45;&gt;libgimpconfig -->
<g id="edge46" class="edge"><title>libgimpwidgets&#45;&gt;libgimpconfig</title>
<path fill="none" stroke="black" d="M554.592,-518.249C545.949,-508.295 536.384,-495.374 531,-482 512.661,-436.447 510.223,-378.617 510.704,-344.337"/>
<polygon fill="black" stroke="black" points="514.209,-344.16 510.947,-334.08 507.211,-343.994 514.209,-344.16"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- GTK+ -->
<g id="node48" class="node"><title>GTK+</title>
<ellipse fill="lightblue" stroke="black" cx="577" cy="-463" rx="36.977" ry="19.0919"/>
Change GTK+ to GTK GTK got rid of the + in 2019: https://lwn.net/Articles/779305/
2022-06-29 23:40:55 +08:00
<text text-anchor="middle" x="577" y="-459.9" font-family="Times Roman,serif" font-size="14.00">GTK</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- libgimpwidgets&#45;&gt;GTK+ -->
<g id="edge48" class="edge"><title>libgimpwidgets&#45;&gt;GTK+</title>
<path fill="none" stroke="black" d="M574.03,-517.943C574.451,-510.149 574.948,-500.954 575.414,-492.338"/>
<polygon fill="black" stroke="black" points="578.915,-492.424 575.959,-482.249 571.925,-492.046 578.915,-492.424"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/menus -->
<g id="node52" class="node"><title>app/menus</title>
<ellipse fill="lawngreen" stroke="black" cx="756" cy="-389" rx="53.2379" ry="19.0919"/>
<text text-anchor="middle" x="756" y="-385.9" font-family="Times Roman,serif" font-size="14.00">app/menus</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/widgets&#45;&gt;app/menus -->
<g id="edge52" class="edge"><title>app/widgets&#45;&gt;app/menus</title>
<path fill="none" stroke="black" d="M754.515,-443.943C754.726,-436.149 754.974,-426.954 755.207,-418.338"/>
<polygon fill="black" stroke="black" points="758.708,-418.34 755.48,-408.249 751.711,-418.151 758.708,-418.34"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/tools -->
<g id="node54" class="node"><title>app/tools</title>
<ellipse fill="lawngreen" stroke="black" cx="641" cy="-759" rx="46.1672" ry="19.0919"/>
<text text-anchor="middle" x="641" y="-755.9" font-family="Times Roman,serif" font-size="14.00">app/tools</text>
</g>
<!-- app/widgets&#45;&gt;app/tools -->
<g id="edge54" class="edge"><title>app/widgets&#45;&gt;app/tools</title>
<path fill="none" stroke="black" d="M727.313,-480.099C714.423,-489.715 699.864,-502.832 691,-518 651.098,-586.285 642.758,-681.803 641.199,-729.484"/>
<polygon fill="black" stroke="black" points="637.694,-729.637 640.946,-739.72 644.692,-729.81 637.694,-729.637"/>
</g>
<!-- app/menus&#45;&gt;app/actions -->
<g id="edge66" class="edge"><title>app/menus&#45;&gt;app/actions</title>
<path fill="none" stroke="black" d="M766.851,-370.327C771.74,-361.913 777.611,-351.809 782.991,-342.55"/>
<polygon fill="black" stroke="black" points="786.155,-344.072 788.153,-333.667 780.102,-340.555 786.155,-344.072"/>
</g>
<!-- app/tools&#45;&gt;app/core -->
<g id="edge68" class="edge"><title>app/tools&#45;&gt;app/core</title>
<path fill="none" stroke="black" d="M601.127,-749.326C545.412,-735.808 444.384,-711.296 384.418,-696.747"/>
<polygon fill="black" stroke="black" points="384.983,-693.283 374.44,-694.326 383.333,-700.086 384.983,-693.283"/>
</g>
<!-- app/tools&#45;&gt;app/dialogs -->
<g id="edge70" class="edge"><title>app/tools&#45;&gt;app/dialogs</title>
<path fill="none" stroke="black" d="M665.953,-742.943C682.076,-732.569 703.289,-718.918 721.076,-707.473"/>
<polygon fill="black" stroke="black" points="722.979,-710.41 729.495,-702.055 719.191,-704.524 722.979,-710.41"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/tools&#45;&gt;libgimpwidgets -->
<g id="edge72" class="edge"><title>app/tools&#45;&gt;libgimpwidgets</title>
<path fill="none" stroke="black" d="M638.418,-739.973C633.758,-708.448 622.562,-643.73 603,-592 599.525,-582.81 594.767,-573.258 590.065,-564.744"/>
<polygon fill="black" stroke="black" points="593.052,-562.918 585.047,-555.978 586.977,-566.395 593.052,-562.918"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/vectors&#45;&gt;Cairo -->
<g id="edge56" class="edge"><title>app/vectors&#45;&gt;Cairo</title>
<path fill="none" stroke="black" d="M311.96,-445.463C298.849,-435.031 282.111,-421.712 268.184,-410.63"/>
<polygon fill="black" stroke="black" points="270.362,-407.891 260.358,-404.403 266.004,-413.368 270.362,-407.891"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/paint -->
<g id="node58" class="node"><title>app/paint</title>
<ellipse fill="lawngreen" stroke="black" cx="339" cy="-389" rx="46.8775" ry="19.0919"/>
<text text-anchor="middle" x="339" y="-385.9" font-family="Times Roman,serif" font-size="14.00">app/paint</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/vectors&#45;&gt;app/paint -->
<g id="edge58" class="edge"><title>app/vectors&#45;&gt;app/paint</title>
<path fill="none" stroke="black" d="M335.288,-443.943C335.814,-436.149 336.436,-426.954 337.018,-418.338"/>
<polygon fill="black" stroke="black" points="340.517,-418.463 337.699,-408.249 333.533,-417.991 340.517,-418.463"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/paint&#45;&gt;GEGL -->
<g id="edge60" class="edge"><title>app/paint&#45;&gt;GEGL</title>
<path fill="none" stroke="black" d="M339,-369.943C339,-362.149 339,-352.954 339,-344.338"/>
<polygon fill="black" stroke="black" points="342.5,-344.249 339,-334.249 335.5,-344.249 342.5,-344.249"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/paint&#45;&gt;libgimpconfig -->
<g id="edge62" class="edge"><title>app/paint&#45;&gt;libgimpconfig</title>
<path fill="none" stroke="black" d="M371.54,-375.081C398.124,-363.71 436.03,-347.496 465.765,-334.777"/>
<polygon fill="black" stroke="black" points="467.29,-337.931 475.108,-330.781 464.537,-331.495 467.29,-337.931"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/paint&#45;funcs -->
<g id="node62" class="node"><title>app/paint&#45;funcs</title>
<ellipse fill="lawngreen" stroke="black" cx="201" cy="-315" rx="70.9184" ry="19.0919"/>
<text text-anchor="middle" x="201" y="-311.9" font-family="Times Roman,serif" font-size="14.00">app/paint&#45;funcs</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/paint&#45;&gt;app/paint&#45;funcs -->
<g id="edge64" class="edge"><title>app/paint&#45;&gt;app/paint&#45;funcs</title>
<path fill="none" stroke="black" d="M310.406,-373.667C290.562,-363.026 263.832,-348.692 241.761,-336.857"/>
<polygon fill="black" stroke="black" points="243.401,-333.765 232.934,-332.124 240.092,-339.934 243.401,-333.765"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<!-- app/paint&#45;funcs&#45;&gt;app/composite -->
<g id="edge74" class="edge"><title>app/paint&#45;funcs&#45;&gt;app/composite</title>
<path fill="none" stroke="black" d="M192.538,-334.205C181.067,-362.03 162,-415.437 162,-463 162,-759 162,-759 162,-759 162,-800.375 167.49,-847.969 171.594,-877.768"/>
<polygon fill="black" stroke="black" points="168.161,-878.487 173.031,-887.896 175.092,-877.504 168.161,-878.487"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
<!-- libgimp -->
<g id="node72" class="node"><title>libgimp</title>
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<ellipse fill="#ff7256" stroke="black" cx="553" cy="-611" rx="41.2167" ry="19.0919"/>
<text text-anchor="middle" x="553" y="-607.9" font-family="Times Roman,serif" font-size="14.00">libgimp</text>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
<!-- libgimp&#45;&gt;libgimpmodule -->
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<g id="edge80" class="edge"><title>libgimp&#45;&gt;libgimpmodule</title>
<path fill="none" stroke="black" d="M525.674,-596.556C505.302,-585.788 477.131,-570.898 454.054,-558.7"/>
<polygon fill="black" stroke="black" points="455.641,-555.58 445.164,-554.001 452.369,-561.768 455.641,-555.58"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
<!-- libgimp&#45;&gt;libgimpwidgets -->
app: Get rid of config -> display module dependency In order to make a clear separation between the core modules and the UI modules, move the necessary enums from display-enums.h and widgets-enums.h to config-enums.h and the files gimpdisplayoptions.[ch] from the display to the config module. This removes the config -> display dependency. This change has three main benefits * It lets us remove includes of display files from the config module * We don't have to link gimp-console and test-config with a subset of object files from the display module * It is reflected in devel-docs/gimp-module-dependencies.svg that the application is made up of core modules and UI modules and that no core module depends on any UI module
2010-02-02 04:55:18 +08:00
<g id="edge82" class="edge"><title>libgimp&#45;&gt;libgimpwidgets</title>
<path fill="none" stroke="black" d="M558.15,-591.943C560.297,-584.002 562.836,-574.606 565.203,-565.851"/>
<polygon fill="black" stroke="black" points="568.637,-566.559 567.867,-555.992 561.879,-564.733 568.637,-566.559"/>
</g>
<!-- app/tests -->
<g id="node75" class="node"><title>app/tests</title>
<ellipse fill="lawngreen" stroke="black" cx="756" cy="-759" rx="44.7575" ry="19.0919"/>
<text text-anchor="middle" x="756" y="-755.9" font-family="Times Roman,serif" font-size="14.00">app/tests</text>
</g>
<!-- app/tests&#45;&gt;app/dialogs -->
<g id="edge84" class="edge"><title>app/tests&#45;&gt;app/dialogs</title>
<path fill="none" stroke="black" d="M756,-739.943C756,-732.149 756,-722.954 756,-714.338"/>
<polygon fill="black" stroke="black" points="759.5,-714.249 756,-704.249 752.5,-714.249 759.5,-714.249"/>
devel-docs: Add gimp-module-dependencies.svg Add an SVG illustration of GIMP library and core modules and the dependencies between them, created with tools/module-dependencies.py. One obvoiusly evil dependency is app/config -> app/display, if we get rid of that the cycle between core modules might be broken.
2010-01-05 00:00:50 +08:00
</g>
</g>
</svg>