mightyscape-1.1-deprecated/extensions/fablabchemnitz/contourscanner/contour_scanner.inx

<?xml version="1.0" encoding="UTF-8"?>
<inkscape-extension xmlns="http://www.inkscape.org/namespace/inkscape/extension">
    <name>Contour Scanner</name>
    <id>fablabchemnitz.de.contour_scanner</id>
    <param name="main_tabs" type="notebook">
        <page name="tab_active" gui-text="Active">
			<hbox>
				<vbox>
					<label appearance="header">Highlight paths</label>
					<param name="highlight_opened" type="bool" gui-text="Highlight opened contours">true</param>
					<param name="color_opened" type="color" appearance="colorbutton" gui-text="Color opened contours">4012452351</param>
					<param name="highlight_closed" type="bool" gui-text="Highlight closed contours">true</param>
					<param name="color_closed" type="color" appearance="colorbutton" gui-text="Color closed contours">2330080511</param>
					<param name="highlight_selfintersecting" type="bool" gui-text="Highlight self-intersecting contours" gui-description="Due to the nature of the algorithm this might detect non-closed contours too.">true</param>
					<param name="color_selfintersecting" type="color" appearance="colorbutton" gui-text="Color self-intersecting contours">1923076095</param>
					<param name="highlight_intersectionpoints" type="bool" gui-text="Highlight self-intersecting points">true</param>
					<param name="color_intersectionpoints" type="color" appearance="colorbutton" gui-text="Color self-intersecting points">4239343359</param>
					<param name="dotsize" type="int" min="0" max="10000" gui-text="Dot size (px) for self-intersecting points">10</param>
					<param name="addlines" type="bool" gui-text="Add closing lines for open self-crossing contours" gui-description="They will have the same color as the intersection points and help to better visualize possible virtual crossings. The algorithm can only detect intersections for closed contours by it's nature, but we handle open contours like they were closed. This may put put too much intersection points.">true</param>
					<param name="polypaths" type="bool" gui-text="Add polypath outline for self-crossing contours" gui-description="This makes only sense if your path is actually a curve. If it's already a polyline you just get a duplicate line (but with reduced nodes)">true</param>
				</vbox>
				<separator/>
				<vbox>
					<label appearance="header">Remove paths</label>
					<param name="remove_opened" type="bool" gui-text="Remove opened contours">false</param>
					<param name="remove_closed" type="bool" gui-text="Remove closed contours">false</param>
					<param name="remove_selfintersecting" type="bool" gui-text="Remove self-intersecting contours">false</param>
					<separator/>
					<label appearance="header">General</label>
					<param name="apply_transformations" type="bool" gui-text="Use 'Apply Transformations' extension" gui-description="Run 'Apply Transformations' extension before running to avoid IndexErrors in calculation.">false</param>
					<param name="breakapart" type="bool" gui-text="Break apart selection into single contours" gui-description="(with ignoring the group hirarchy by taking all children elements)">false</param>
					<param name="removefillsetstroke" type="bool" gui-text="Remove fill and define stroke">false</param>
					<param name="strokewidth" min="0.0" max="10000.0" gui-text="Stroke width (px)" type="float">1.0</param>
					<param name="show_debug" type="bool" gui-text="Show debug info">false</param>
				</vbox>
			</hbox>
        </page>
        <page name="tab_info" gui-text="About">
            <label appearance="header">About</label>
            <separator/>
            <label>Contour Scanner by Mario Voigt / Stadtfabrikanten e.V. (2020)</label>
            <label>This piece of software is part of the MightyScape for InkScape 1.0/1.1dev Extension Collection</label>
            <label>you found a bug or got some fresh code? Just report to mario.voigt@stadtfabrikanten.org. Thanks!</label>
            <label appearance="url">https://fablabchemnitz.de</label>
            <label>License: GNU GPL v3</label>
            <separator/>
            <label>This tool helps you to find nasty contours which might bug you and prevent your work from being ready for production. Ideally you should convert your paths to polylines because the algorithm used by Contour Scanner is not able to distinguish between curves and polylines. It will handle curves like polylines but that creates visual and measurable errors. Either use "Split Bezier (Subdivide Path)" or "Add Nodes" extension to split into smaller segments which makes more precise. You can also run "Flatten Bezier" to make smooth polylines. For roughest approximation use "Convert to Polylines" extension to create real polylines. You can find the complete documentation at the Wiki space of https://fablabchemnitz.de</label>
        </page>
    </param>
    <effect>
      <object-type>path</object-type>
      <effects-menu>
        <submenu name="FabLab Chemnitz">
            <submenu name="Nesting/Cut Optimization"/>
        </submenu>
      </effects-menu>
    </effect>
    <script>
       <command location="inx" interpreter="python">contour_scanner.py</command>
    </script>
</inkscape-extension>