summaryrefslogtreecommitdiff
path: root/graphics/jpicedt
diff options
context:
space:
mode:
authorNorbert Preining <norbert@preining.info>2019-09-02 13:46:59 +0900
committerNorbert Preining <norbert@preining.info>2019-09-02 13:46:59 +0900
commite0c6872cf40896c7be36b11dcc744620f10adf1d (patch)
tree60335e10d2f4354b0674ec22d7b53f0f8abee672 /graphics/jpicedt
Initial commit
Diffstat (limited to 'graphics/jpicedt')
-rw-r--r--graphics/jpicedt/doc/ArcChord.gifbin0 -> 73 bytes
-rw-r--r--graphics/jpicedt/doc/ArcOpen.gifbin0 -> 76 bytes
-rw-r--r--graphics/jpicedt/doc/ArcPie.gifbin0 -> 85 bytes
-rw-r--r--graphics/jpicedt/doc/ArrowStyleButton.gifbin0 -> 220 bytes
-rw-r--r--graphics/jpicedt/doc/AttributeEditor.gifbin0 -> 15024 bytes
-rw-r--r--graphics/jpicedt/doc/Bezier.gifbin0 -> 77 bytes
-rw-r--r--graphics/jpicedt/doc/Cubic.gifbin0 -> 74 bytes
-rw-r--r--graphics/jpicedt/doc/DashButton.gifbin0 -> 265 bytes
-rw-r--r--graphics/jpicedt/doc/EditPointsMode.gifbin0 -> 118 bytes
-rw-r--r--graphics/jpicedt/doc/Ellipse.gifbin0 -> 173 bytes
-rw-r--r--graphics/jpicedt/doc/FillButton.gifbin0 -> 149 bytes
-rw-r--r--graphics/jpicedt/doc/FillColorButton.gifbin0 -> 174 bytes
-rw-r--r--graphics/jpicedt/doc/GridButton.gifbin0 -> 181 bytes
-rw-r--r--graphics/jpicedt/doc/Line.gifbin0 -> 73 bytes
-rw-r--r--graphics/jpicedt/doc/PicPut.gifbin0 -> 855 bytes
-rw-r--r--graphics/jpicedt/doc/Polygon.gifbin0 -> 84 bytes
-rw-r--r--graphics/jpicedt/doc/PropertiesToolbar.gifbin0 -> 937 bytes
-rw-r--r--graphics/jpicedt/doc/Rectangle.gifbin0 -> 79 bytes
-rw-r--r--graphics/jpicedt/doc/SnapStepButton.gifbin0 -> 241 bytes
-rw-r--r--graphics/jpicedt/doc/StrokeColorButton.gifbin0 -> 275 bytes
-rw-r--r--graphics/jpicedt/doc/Text.gifbin0 -> 82 bytes
-rw-r--r--graphics/jpicedt/doc/ThicknessButton.gifbin0 -> 469 bytes
-rw-r--r--graphics/jpicedt/doc/ToolkitPalette.gifbin0 -> 2207 bytes
-rw-r--r--graphics/jpicedt/doc/ZoomFactorButton.gifbin0 -> 234 bytes
-rw-r--r--graphics/jpicedt/doc/actions.html161
-rw-r--r--graphics/jpicedt/doc/commandline.html34
-rw-r--r--graphics/jpicedt/doc/documentation.html15
-rw-r--r--graphics/jpicedt/doc/drawingcap.html58
-rw-r--r--graphics/jpicedt/doc/editing.html97
-rw-r--r--graphics/jpicedt/doc/gpl.html533
-rw-r--r--graphics/jpicedt/doc/help.html15
-rw-r--r--graphics/jpicedt/doc/index.html15
-rw-r--r--graphics/jpicedt/doc/menu.html22
-rw-r--r--graphics/jpicedt/doc/parsing.html158
-rw-r--r--graphics/jpicedt/doc/preferences.html176
-rw-r--r--graphics/jpicedt/doc/scripting.html92
-rw-r--r--graphics/jpicedt/jPicEdtReadme_1_3_2.html62
37 files changed, 1438 insertions, 0 deletions
diff --git a/graphics/jpicedt/doc/ArcChord.gif b/graphics/jpicedt/doc/ArcChord.gif
new file mode 100644
index 0000000000..96160539d2
--- /dev/null
+++ b/graphics/jpicedt/doc/ArcChord.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/ArcOpen.gif b/graphics/jpicedt/doc/ArcOpen.gif
new file mode 100644
index 0000000000..b7766f1656
--- /dev/null
+++ b/graphics/jpicedt/doc/ArcOpen.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/ArcPie.gif b/graphics/jpicedt/doc/ArcPie.gif
new file mode 100644
index 0000000000..3487211ccd
--- /dev/null
+++ b/graphics/jpicedt/doc/ArcPie.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/ArrowStyleButton.gif b/graphics/jpicedt/doc/ArrowStyleButton.gif
new file mode 100644
index 0000000000..5c25ea99ef
--- /dev/null
+++ b/graphics/jpicedt/doc/ArrowStyleButton.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/AttributeEditor.gif b/graphics/jpicedt/doc/AttributeEditor.gif
new file mode 100644
index 0000000000..d60635ccfe
--- /dev/null
+++ b/graphics/jpicedt/doc/AttributeEditor.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/Bezier.gif b/graphics/jpicedt/doc/Bezier.gif
new file mode 100644
index 0000000000..2f846b666f
--- /dev/null
+++ b/graphics/jpicedt/doc/Bezier.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/Cubic.gif b/graphics/jpicedt/doc/Cubic.gif
new file mode 100644
index 0000000000..9fb6f2c94b
--- /dev/null
+++ b/graphics/jpicedt/doc/Cubic.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/DashButton.gif b/graphics/jpicedt/doc/DashButton.gif
new file mode 100644
index 0000000000..a1acc046eb
--- /dev/null
+++ b/graphics/jpicedt/doc/DashButton.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/EditPointsMode.gif b/graphics/jpicedt/doc/EditPointsMode.gif
new file mode 100644
index 0000000000..1eb565861e
--- /dev/null
+++ b/graphics/jpicedt/doc/EditPointsMode.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/Ellipse.gif b/graphics/jpicedt/doc/Ellipse.gif
new file mode 100644
index 0000000000..ac8b2fd6e4
--- /dev/null
+++ b/graphics/jpicedt/doc/Ellipse.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/FillButton.gif b/graphics/jpicedt/doc/FillButton.gif
new file mode 100644
index 0000000000..f4314196fe
--- /dev/null
+++ b/graphics/jpicedt/doc/FillButton.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/FillColorButton.gif b/graphics/jpicedt/doc/FillColorButton.gif
new file mode 100644
index 0000000000..2040ed35f7
--- /dev/null
+++ b/graphics/jpicedt/doc/FillColorButton.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/GridButton.gif b/graphics/jpicedt/doc/GridButton.gif
new file mode 100644
index 0000000000..5af5336020
--- /dev/null
+++ b/graphics/jpicedt/doc/GridButton.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/Line.gif b/graphics/jpicedt/doc/Line.gif
new file mode 100644
index 0000000000..4ab067f77b
--- /dev/null
+++ b/graphics/jpicedt/doc/Line.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/PicPut.gif b/graphics/jpicedt/doc/PicPut.gif
new file mode 100644
index 0000000000..4b44763c37
--- /dev/null
+++ b/graphics/jpicedt/doc/PicPut.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/Polygon.gif b/graphics/jpicedt/doc/Polygon.gif
new file mode 100644
index 0000000000..29d7ae0020
--- /dev/null
+++ b/graphics/jpicedt/doc/Polygon.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/PropertiesToolbar.gif b/graphics/jpicedt/doc/PropertiesToolbar.gif
new file mode 100644
index 0000000000..665241a861
--- /dev/null
+++ b/graphics/jpicedt/doc/PropertiesToolbar.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/Rectangle.gif b/graphics/jpicedt/doc/Rectangle.gif
new file mode 100644
index 0000000000..4577d231b2
--- /dev/null
+++ b/graphics/jpicedt/doc/Rectangle.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/SnapStepButton.gif b/graphics/jpicedt/doc/SnapStepButton.gif
new file mode 100644
index 0000000000..6179bd4986
--- /dev/null
+++ b/graphics/jpicedt/doc/SnapStepButton.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/StrokeColorButton.gif b/graphics/jpicedt/doc/StrokeColorButton.gif
new file mode 100644
index 0000000000..d2fc643cbf
--- /dev/null
+++ b/graphics/jpicedt/doc/StrokeColorButton.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/Text.gif b/graphics/jpicedt/doc/Text.gif
new file mode 100644
index 0000000000..9fb292b0ec
--- /dev/null
+++ b/graphics/jpicedt/doc/Text.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/ThicknessButton.gif b/graphics/jpicedt/doc/ThicknessButton.gif
new file mode 100644
index 0000000000..65c9c33590
--- /dev/null
+++ b/graphics/jpicedt/doc/ThicknessButton.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/ToolkitPalette.gif b/graphics/jpicedt/doc/ToolkitPalette.gif
new file mode 100644
index 0000000000..245db6a74e
--- /dev/null
+++ b/graphics/jpicedt/doc/ToolkitPalette.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/ZoomFactorButton.gif b/graphics/jpicedt/doc/ZoomFactorButton.gif
new file mode 100644
index 0000000000..ec082986bb
--- /dev/null
+++ b/graphics/jpicedt/doc/ZoomFactorButton.gif
Binary files differ
diff --git a/graphics/jpicedt/doc/actions.html b/graphics/jpicedt/doc/actions.html
new file mode 100644
index 0000000000..d8223cf5b1
--- /dev/null
+++ b/graphics/jpicedt/doc/actions.html
@@ -0,0 +1,161 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <META key="author" CONTENT="Sylvain Reynal">
+ <TITLE>jPicEdt 1.3.2 Help Content </TITLE>
+ </HEAD>
+
+ <BODY BGCOLOR="#ffffff">
+
+<H2>Toolbars</H2>
+<P><IMG SRC="PropertiesToolbar.gif"></P>
+<TABLE BORDER=1>
+ <TR><TD><IMG SRC="GridButton.gif"></TD><TD>Displays the grid</TD></TR>
+ <TR><TD><IMG SRC="SnapStepButton.gif"></TD><TD>Sets the snap snep. You can type your own value.</TD></TR>
+ <TR><TD><IMG SRC="ZoomFactorButton.gif"></TD><TD>Sets the zoom-factor. You can type your own value.</TD></TR>
+ <TR><TD><IMG SRC="EditPointsMode.gif"></TD><TD>Toggle the edition-mode between group-mode and single-object mode.</TD></TR>
+</TABLE>
+<HR>
+</HR>
+
+<H2>Menus</H2>
+<TABLE border=1>
+ <TR><TD colspan=2><B>File menu</B></TD></TR>
+ <TR><td>New</TD><td>create a new drawing sheet.</TD></TR>
+ <TR><td>Open</td><td>load an existing file from disk.</td></TR>
+ <TR><td>Reload</TD><td>reload current drawing from disk</TD></TR>
+ <TR><td>Save</td><td>save current file in LaTeX, epic or PsTricks format, depending on the
+ current content-type; default directories can be
+ specified in the preferences tabsheet.</td></TR>
+ <TR><td>Save As</td><td>let you choose another file name.</td></TR>
+ <TR><td>Save All</TD><TD>save all currently open sheets.</TD></TR>
+ <TR><TD>Save Selection As</TD><td>let you save only selected (namely : highlighted) parts of your
+ drawing ; useful to create fragments ; the user's fragment directory is automatically
+ pre-selected in the file-chooser, but you can save fragments in other places...</td></TR>
+ <TR><td>Insert Fragment</TD><td>insert a prerecorded fragment into the current active sheet
+ (the topmost internal frame), placing it in the bottom-left corner
+ of the frame ; by default, the filechooser points to the user's fragment directory,
+ but you can obviously insert fragments from other places...</td></TR>
+ <TR><td>Recent Files</TD><td>this mutable menu keeps track of the last four loaded or
+ updated files, and let you quickly load one of them.</TD></TR>
+ <TR><td>Close</TD><td>Close active frame</TD></TR>
+ <TR><td>Exit</TD><td>Save every open sheet to disk, then quit.<td></TR>
+
+ <TR><td colspan=2><b>Edit menu</B></TD></TR>
+ <TR><td>Undo/Redo</TD><td>undo/redo last change (the number of undoable steps is
+ specified in the preferences menu). </TD></TR>
+ <TR><td>Cut</TD><td>cut current selection and send it to clipboard.</TD></TR>
+ <TR><td>Copy</TD><td>copy selection to clipboard.</TD></TR>
+ <TR><td>Paste</TD><td>
+ paste selection from JPicEdt graphic clipboard, starting from bottom-left
+ corner.
+ </TD></TR>
+ <TR><td>Paste special</TD><td>
+ paste selection by trying to parse the content of the system
+ clipboard. For example, you may first copy a LaTeX string to the system clipboard
+ from your favorite editor, then paste it to jPicEdit using
+ PasteSpecial.
+ This can obviously lead to a parser-error if the text content is not syntaxically correct.
+ <br>
+ Under <b>Linux</b>, use <code>xclipboard</code> to copy a piece of text to the primary selection...
+ Direct data transfer b/w the jEdit editor and jPicEdt works flawlessly however.
+ </TD></TR>
+ <TR><td>Select All</TD><td>
+ select every object in the current board.
+ </TD></TR>
+ <TR><td>Page format</TD><td>
+ set the page format of the current drawing board, if any. If there's no open board,
+ set the default page format for new boards (this is identical as setting the
+ page format from the Preferences).
+ </TD></TR>
+ <TR><td>Content type</TD><td>
+ set the content-type of the current drawing board, if any. This sets the formatter
+ used to format the current drawing to LaTeX (i.e. LaTeX picture env, epic or PsTricks),
+ and also affects the way elements are displayed (for example, colour is supported by
+ PsTricks only, filling ellipses by PsTricks and eepic only,...).
+ </TD></TR>
+ <TR><td>Preferences</TD><td>
+ opens the &quot;set preference&quot; tab. See <i>setting preferences</i>.
+ </TD></TR>
+ <TR><td>Attributes editor</TD><td>
+ toggle the visibility of the floating &quot;set attribute editor&quot;.
+ This can be useful on laptops, because this palette takes up a significant amount
+ of the screen ;-).
+ </TD></TR>
+
+ <TR><TD colspan=2><B>Command menu</B></TD></TR>
+ <TR><td>LaTeX</TD><td>
+ run LaTeX on the current drawing; to sum up : jPicEdt creates a
+ temporary LaTeX file on-the-fly, containing all the necessary stuff
+ (see how to set the prolog and epilog in
+ the preferences tabpane), in the <I>temporary</I> directory of the underlying
+ platform (e.g. /tmp under Unix and MacOS-X, c:\windows\temp under Win9x,...)
+ then run LaTeX on it.
+ <br>
+ Contrary to previous releases, you don't need to save your picture anymore
+ before running the LaTeX/DVI/etc... commands.
+
+ </TD></TR>
+ <TR><td>Dvi viewer</TD><td>
+ same thing, but run a dvi viewer on the same file (actually the one with a ".dvi" extension, which
+ then assume you ran LaTeX before).
+ </TD></TR>
+ <TR><td>Dvips</TD><td>
+ run the referenced Dvips program.
+ </TD></TR>
+ <TR><td>Ghostview</TD><td>
+ run the referenced Ghostview program.
+ </TD></TR>
+ <TR><TD colspan=2>External program path and names (as well as their calling syntax)
+ can be specified in the preferences.
+ </TD></TR>
+
+ <TR><TD colspan=2><B>Fragments menu</B></TD></TR>
+ <TR><td>List of fragments</TD><td>
+ Depending on fragments found in the system-wide's and the user's fragments directory,
+ you may see zero, one or
+ more items here. Click to insert. Fragments saved by user go into the "fragments" subdirectory
+ of the user-settings directory (for instance : <b>/home/user/.jpicedt/fragments</b> on Unix).
+ </TD></TR>
+ <TR><td>Rescan</TD><td>
+ Rescan the list of fragments.
+ </TD></TR>
+
+ <TR><TD colspan=2><B>Script menu</B>
+ </TD></TR>
+ <TR><td>BSH Console</TD><td>
+ Open a BSH Console for interacting on-the-fly with jpicedt, or for debugging your scripts.
+ </TD></TR>
+ <TR><td>List of scripts</TD><td>
+ Depending on scripts installed in the system-wide's and the user's script directory,
+ you may see zero, one or more items here. Click to run.
+ </TD></TR>
+ <TR><td>Rescan</TD><td>
+ Rescan the list of installed scripts from the script directory.
+ </TD></TR>
+
+ <TR><TD colspan=2><B>Window menu</B>
+ </TD></TR>
+ <TR><td>Cascade</TD><td>
+ cascade all internal windows.
+ </TD></TR>
+ <TR><td>Tile horizontal</TD><td>
+ tile windows horizontally, creating as new rows as necessary.
+ </TD></TR>
+ <TR><td>Tile vertical</TD><td>
+ tile windows vertically, creating as new columns as necessary.
+ </TD></TR>
+ <TR><TD colspan=2>Window menu also maintains a list of currently open sheets so
+ that you can quickly switch between them (Note : keyboard
+ shortcuts may not work on Linux and MacOS platforms).
+ </TD></TR>
+</TABLE>
+<HR>
+
+</HR>
+</BODY>
+</HTML>
+
+
+
diff --git a/graphics/jpicedt/doc/commandline.html b/graphics/jpicedt/doc/commandline.html
new file mode 100644
index 0000000000..5d6e210c2d
--- /dev/null
+++ b/graphics/jpicedt/doc/commandline.html
@@ -0,0 +1,34 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <META key="author" CONTENT="Sylvain Reynal">
+ <TITLE>jPicEdt 1.3.2 Help Content </TITLE>
+ </HEAD>
+
+ <BODY BGCOLOR="#ffffff">
+ <H2>Command line</H2>
+ The command line accepts the following arguments :
+ <UL>
+ <LI><CODE>-redir=standard</CODE>:
+ redirect standard error stream (System.err) to the console
+ </LI>
+ <LI><CODE>-redir=file</CODE>
+ (default): redirect standard error stream to a file named
+ <CODE>error.log</CODE> and located in jPicEdt's user-settings
+ directory, for instance
+ <b>/home/user/.jpicedt/error.log</b> on Unix. You can view this file by
+ clicking on "View Error Log" in the Help menu.
+ </LI>
+ <LI>A list of space-separated file names to be loaded on start-up.
+ </LI>
+ </UL>
+ <P>Example of use :</P>
+ <P><CODE>jpicedt -redir=standard picture1.tex picture2.tex</CODE>
+ (where <b>jpicedt</b> denotes the name of the start-up script).
+ </P>
+</BODY>
+</HTML>
+
+
+
diff --git a/graphics/jpicedt/doc/documentation.html b/graphics/jpicedt/doc/documentation.html
new file mode 100644
index 0000000000..f556cb9ae3
--- /dev/null
+++ b/graphics/jpicedt/doc/documentation.html
@@ -0,0 +1,15 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN" "http://www.w3.org/TR/REC-html40/frameset.dtd">
+<HTML>
+ <HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <META key="author" CONTENT="Sylvain Reynal">
+ <TITLE>jPicEdt 1.3.2 Help Content </TITLE>
+ </HEAD>
+
+ <FRAMESET cols="160,*">
+ <FRAME src="menu.html" name="menu">
+ <FRAME src="drawingcap.html" name="content">
+ <NOFRAMES></NOFRAMES>
+ </FRAMESET>
+</HTML>
+
diff --git a/graphics/jpicedt/doc/drawingcap.html b/graphics/jpicedt/doc/drawingcap.html
new file mode 100644
index 0000000000..0825e0b59f
--- /dev/null
+++ b/graphics/jpicedt/doc/drawingcap.html
@@ -0,0 +1,58 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <META key="author" CONTENT="Sylvain Reynal">
+ <TITLE>jPicEdt 1.3.2 Help Content </TITLE>
+</HEAD>
+
+<BODY BGCOLOR="#ffffff">
+
+ <H2>Drawing objects</H2>
+ <P>
+ To draw a new object on the sheet, first select a shape by
+ clicking on one of the drawing tools on the floating toolbar.
+ </P>
+ <p>
+ <IMG SRC="ToolkitPalette.gif">
+ </IMG>
+ <p>
+ Each button can display a tooltip
+ if the mouse stays more than two seconds on it. Then CLICK with the
+ mouse's LEFT button anywhere on the canvas to set the object's first
+ point. Now MOVING the mouse let you choose the second point. When
+ you're ok, simply CLICK again.
+ </P>
+ <P>Graphical objects defined by more than two control points, e.g. polygons or
+ splines, work the same way, except that you'll have to "move-then-click" as many
+ times as there are control points to the curve, then DOUBLE-CLICK to end up the drawing process.
+ </P>
+ <p>
+ If a right click occurs before the element is totally drawn, this cancels the whole
+ operation.
+ </p>
+ <P>The following is a list of all available objects as well as their
+ associated icon on the toolbar :</P>
+ <TABLE BORDER=2>
+ <TR><TD><IMG SRC="Line.gif"></TD><TD>Lines</P></TD></TR>
+ <TR><TD><IMG SRC="Bezier.gif"></TD><TD>Bezier quadratic splines</TD></TR>
+ <TR><TD><IMG SRC="Cubic.gif"></TD><TD>Bezier cubic splines</TD></TR>
+ <TR><TD><IMG SRC="Rectangle.gif"></TD><TD>Rectangles. </TD></TR>
+ <TR><TD><IMG SRC="Ellipse.gif"></TD><TD>Circles, ellipses.</TD></TR>
+ <TR><TD><IMG SRC="ArcOpen.gif"></TD><TD>Open arcs.</TD></TR>
+ <TR><TD><IMG SRC="ArcPie.gif"></TD><TD>Pies.</TD></TR>
+ <TR><TD><IMG SRC="ArcChord.gif"></TD><TD>Chord arcs. </TD></TR>
+ <TR><TD><IMG SRC="Polygon.gif"></TD><TD>Polygons. Double-click to end the drawing operation.</TD></TR>
+ <TR><TD><IMG SRC="Text.gif"></TD><TD>Text (possibly boxed). </TD></TR>
+ </TABLE>
+ <p>For rectangles, ellipses and arcs, press the <b>CONTROL</b> key to draw with centre kept fixed.</p>
+ <p>For all objects, pressing F2 open a properties-panel. This in particular allows to change the
+ alignement and box type for texts, and the arc type for arcs.</p>
+ <p><b>Please note :</b> PsTricks doesn't support elliptic arcs. There have been some add-ons which
+ circumvent this limitation, yet these aren't included YET in jPicEdt. LaTeX and eepic don't support these
+ objects neither, hence these are emulated. I know, the question of adopting the same policy for PsTricks has been mooted
+ several times... PsTricks is beautiful, emulation is cack. The answer is definitely NO.
+ </p>
+</BODY>
+</HTML>
+
diff --git a/graphics/jpicedt/doc/editing.html b/graphics/jpicedt/doc/editing.html
new file mode 100644
index 0000000000..c05ab1c045
--- /dev/null
+++ b/graphics/jpicedt/doc/editing.html
@@ -0,0 +1,97 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <META key="author" CONTENT="Sylvain Reynal">
+ <TITLE>jPicEdt 1.3.2 Help Content </TITLE>
+</HEAD>
+
+<BODY BGCOLOR="#ffffff">
+
+ <H2>Editing shapes</H2>
+ <P>
+ To edit an object, first <B>click on its stroke path</B> to select it :
+ </P>
+ <UL>
+ <LI>if this object is a <B>single</B>
+ object, its anchor points transform to small squares ; </LI>
+ <LI>if this object is a <B>group</B>
+ of objects, and
+ <IMG SRC="EditPointsMode.gif"></IMG>
+ button isn't active, group's end-points are displayed instead (this
+ allows you to scale the entire group content); if this button's
+ active, you can edit inwards object end-points separately;
+ </LI>
+ <LI>the floating attribute-editor gets
+ updated according to the selected object properties (e.g.
+ fill-colour, stroke thickness, arrows...).
+ </LI>
+ </UL>
+ <P>
+ You can move a particular anchor point by clicking on it and
+ dragging the mouse, or you can translate the whole selection by
+ clicking somewhere on a stroke path. When moving a <B>group</B> of
+ object, the clicked object serves as a reference for <B>alignment</B>
+ on the grid.
+ </P>
+ <p>
+ If you want precise control over the object location,
+ pressing <B>F2</B> directly pops up a properties panel
+ that lets you alter the object shape using numerical entries rather than the mouse
+ </P>
+ <p>
+ <b>Tip : </b> clicking on a selected object with SHIFT pressed let you deselect it.
+ </p>
+
+ <H2>Context menu</H2>
+ <P>
+ Right-clicking on an object raises a <B>popup menu</B>
+ which lets you do various operations on that object. More
+ operations (e.g. rotations, ...) should be available in future
+ releases.
+ </P>
+
+ <h2>Resizing rectangles, ellipses and arcs</h2>
+ <p>
+ Pressing the <b>CONTROL</b> key during a resize-operation leaves the centre fixed.
+ </p>
+
+ <h2>Adding points to polygons</h2>
+ <p>
+ Pressing the <b>CONTROL</b> key when the mouse hovers on a polygon stroke-path,
+ allows to add/remove points to/from the polygon.
+ </p>
+
+ <H2>Multiple selections and groups</H2>
+ <P>
+ You can afford <B>multiple selections</B> either by holding the
+ <B>SHIFT</B> key pressed during the select operation or by &quot;wrapping&quot;
+ objects you want to select in a selection rectangle that you create by
+ dragging the mouse from anywhere on the sheet. <I>Translation</I> and
+ <I>scaling</I> operations are then possible using the same rules as
+ in the previous paragraph. You can also <B>group</B> selected objects
+ so that they get linked one to each other ; besides, groups are
+ nestables. To <B>ungroup</B> previously grouped objects, click with
+ the <B>right mouse button</B> somewhere on a selected group to raise
+ a <B>popup menu</B>, then select the <I>ungroup</I> operation.
+ </P>
+
+ <h2>Changing attributes</h2>
+ <p>
+ Graphical attributes, e.g. line thickness, fill colour, etc... can be changed by first
+ selecting objects of interest, then changing fields values in the floating <b>Attribute Editor</b>
+ palette.
+ </p>
+ <p>
+ <img src="AttributeEditor.gif">
+ </p>
+ Depending on the current content-type, some attributes aren't displayed, though they can be changed
+ in the Attribute Editor. In particular, the LaTeX picture environment content-type supports only a
+ very limited subset of all the attributes available in the palette (e.g. no colour, no texture, only
+ simple arrows, no shadow,...).
+ If you'd like to use the whole gamus of graphical attributes offered by the palette, including shadows,
+ texture and colour filling, or fine-grained dashing, please switch to the PsTricks content-type, and
+ add an <b>\usepackage{pstricks.sty}</b> in your LaTeX files. You won't regret it !
+</BODY>
+</HTML>
+
diff --git a/graphics/jpicedt/doc/gpl.html b/graphics/jpicedt/doc/gpl.html
new file mode 100644
index 0000000000..c5d33de56b
--- /dev/null
+++ b/graphics/jpicedt/doc/gpl.html
@@ -0,0 +1,533 @@
+<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
+<HTML>
+<HEAD>
+<TITLE>GNU General Public License - GNU Project - Free Software Foundation (FSF)</TITLE>
+<LINK REV="made" HREF="mailto:webmasters@www.gnu.org">
+</HEAD>
+<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#1F00FF" ALINK="#FF0000" VLINK="#9900DD">
+<H1>GNU General Public License</H1>
+<A HREF="http://www.gnu.org/graphics/philosophicalgnu.html"><IMG SRC="philosophical-gnu-sm.jpg"
+ ALT=" [image of a Philosophical GNU] "
+ WIDTH="160" HEIGHT="200"></A>
+<!-- It is best to not enumerate the translations here in a menu bar, -->
+<!-- It is best to have the users follow this link, so they have the FSF' -->
+<!-- explanation about translations being unofficial, etc. -->
+<P>
+<UL>
+ <LI><A HREF="http://www.gnu.org/copyleft/gpl-violation.html">What to do if you see a possible GPL violation</A></LI>
+ <LI><A HREF="http://www.gnu.org/copyleft/copyleft.html#translations">Translations of the GPL</A></LI>
+</UL>
+<P>
+<HR>
+
+<P>
+
+<H2>Table of Contents</H2>
+<UL>
+
+ <LI><A NAME="TOC1" HREF="gpl.html#SEC1">GNU GENERAL PUBLIC LICENSE</A>
+<UL>
+<LI><A NAME="TOC2" HREF="gpl.html#SEC2">Preamble</A>
+<LI><A NAME="TOC3" HREF="gpl.html#SEC3">TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</A>
+<LI><A NAME="TOC4" HREF="gpl.html#SEC4">How to Apply These Terms to Your New Programs</A>
+
+</UL>
+</UL>
+
+<P>
+
+<HR>
+
+<P>
+
+
+
+<H2><A NAME="SEC1" HREF="gpl.html#TOC1">GNU GENERAL PUBLIC LICENSE</A></H2>
+<P>
+Version 2, June 1991
+
+</P>
+
+<PRE>
+Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+</PRE>
+
+
+
+<H2><A NAME="SEC2" HREF="gpl.html#TOC2">Preamble</A></H2>
+
+<P>
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) You can apply it to
+your programs, too.
+
+</P>
+<P>
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+</P>
+<P>
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+</P>
+<P>
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+</P>
+<P>
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+</P>
+<P>
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+</P>
+<P>
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+</P>
+<P>
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+</P>
+
+
+<H2><A NAME="SEC3" HREF="gpl.html#TOC3">TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</A></H2>
+
+
+<P>
+
+<STRONG>0.</STRONG>
+ This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+<P>
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+<P>
+
+<STRONG>1.</STRONG>
+ You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+<P>
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+<P>
+
+<STRONG>2.</STRONG>
+ You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+<P>
+
+<UL>
+
+<LI><STRONG>a)</STRONG>
+ You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+<P>
+<LI><STRONG>b)</STRONG>
+ You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+<P>
+<LI><STRONG>c)</STRONG>
+ If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+</UL>
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+<P>
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+<P>
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+<P>
+
+<STRONG>3.</STRONG>
+ You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+
+<!-- we use this doubled UL to get the sub-sections indented, -->
+<!-- while making the bullets as unobvious as possible. -->
+<UL>
+
+<LI><STRONG>a)</STRONG>
+ Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+<P>
+<LI><STRONG>b)</STRONG>
+ Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+<P>
+<LI><STRONG>c)</STRONG>
+ Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+</UL>
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+<P>
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+<P>
+
+<STRONG>4.</STRONG>
+ You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+<P>
+
+<STRONG>5.</STRONG>
+ You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+<P>
+
+<STRONG>6.</STRONG>
+ Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+<P>
+
+<STRONG>7.</STRONG>
+ If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+<P>
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+<P>
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+<P>
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+<P>
+
+<STRONG>8.</STRONG>
+ If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+<P>
+
+<STRONG>9.</STRONG>
+ The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+<P>
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+<P>
+
+
+<STRONG>10.</STRONG>
+ If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+
+
+<P><STRONG>NO WARRANTY</STRONG></P>
+
+<P>
+
+<STRONG>11.</STRONG>
+ BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+<P>
+
+<STRONG>12.</STRONG>
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+<P>
+
+
+<H2>END OF TERMS AND CONDITIONS</H2>
+
+
+
+<H2><A NAME="SEC4" HREF="gpl.html#TOC4">How to Apply These Terms to Your New Programs</A></H2>
+
+<P>
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+</P>
+<P>
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+</P>
+
+<PRE>
+<VAR>one line to give the program's name and an idea of what it does.</VAR>
+Copyright (C) <VAR>yyyy</VAR> <VAR>name of author</VAR>
+
+This program is free software; you can redistribute it and/or
+modify it under the terms of the GNU General Public License
+as published by the Free Software Foundation; either version 2
+of the License, or (at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; if not, write to the Free Software
+Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
+</PRE>
+
+<P>
+Also add information on how to contact you by electronic and paper mail.
+
+</P>
+<P>
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+</P>
+
+<PRE>
+Gnomovision version 69, Copyright (C) <VAR>year</VAR> <VAR>name of author</VAR>
+Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
+type `show w'. This is free software, and you are welcome
+to redistribute it under certain conditions; type `show c'
+for details.
+</PRE>
+
+<P>
+The hypothetical commands <SAMP>`show w'</SAMP> and <SAMP>`show c'</SAMP> should show
+the appropriate parts of the General Public License. Of course, the
+commands you use may be called something other than <SAMP>`show w'</SAMP> and
+<SAMP>`show c'</SAMP>; they could even be mouse-clicks or menu items--whatever
+suits your program.
+
+</P>
+<P>
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+</P>
+
+<PRE>
+Yoyodyne, Inc., hereby disclaims all copyright
+interest in the program `Gnomovision'
+(which makes passes at compilers) written
+by James Hacker.
+
+<VAR>signature of Ty Coon</VAR>, 1 April 1989
+Ty Coon, President of Vice
+</PRE>
+
+<P>
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Library General
+Public License instead of this License.
+
+<HR>
+
+Go to GNU's home page: <A HREF="http://www.gnu.org/home.html">http://www.gnu.org/home.html</A>.
+<P>
+FSF &amp; GNU inquiries &amp; questions to <A HREF="mailto:gnu@gnu.org"><EM>gnu@gnu.org</EM></A>.
+Other ways to contact the FSF: <A HREF="http://www.gnu.org/home.html#ContactInfo">http://www.gnu.org/home.html#ContactInfo</A>
+<P>
+Comments on these web pages to
+<A HREF="mailto:webmasters@www.gnu.org"><EM>webmasters@www.gnu.org</EM></A>,
+send other questions to
+<A HREF="mailto:gnu@gnu.org"><EM>gnu@gnu.org</EM></A>.
+<P>
+Copyright notice above.<BR>
+Free Software Foundation, Inc.,
+59 Temple Place - Suite 330, Boston, MA 02111, USA
+<P>
+Updated:
+<!-- hhmts start -->
+Last modified: Wed Mar 1 15:55:10 MET 2000
+<!-- hhmts end -->
+<HR>
+</BODY>
+</HTML>
diff --git a/graphics/jpicedt/doc/help.html b/graphics/jpicedt/doc/help.html
new file mode 100644
index 0000000000..f556cb9ae3
--- /dev/null
+++ b/graphics/jpicedt/doc/help.html
@@ -0,0 +1,15 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN" "http://www.w3.org/TR/REC-html40/frameset.dtd">
+<HTML>
+ <HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <META key="author" CONTENT="Sylvain Reynal">
+ <TITLE>jPicEdt 1.3.2 Help Content </TITLE>
+ </HEAD>
+
+ <FRAMESET cols="160,*">
+ <FRAME src="menu.html" name="menu">
+ <FRAME src="drawingcap.html" name="content">
+ <NOFRAMES></NOFRAMES>
+ </FRAMESET>
+</HTML>
+
diff --git a/graphics/jpicedt/doc/index.html b/graphics/jpicedt/doc/index.html
new file mode 100644
index 0000000000..f556cb9ae3
--- /dev/null
+++ b/graphics/jpicedt/doc/index.html
@@ -0,0 +1,15 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN" "http://www.w3.org/TR/REC-html40/frameset.dtd">
+<HTML>
+ <HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <META key="author" CONTENT="Sylvain Reynal">
+ <TITLE>jPicEdt 1.3.2 Help Content </TITLE>
+ </HEAD>
+
+ <FRAMESET cols="160,*">
+ <FRAME src="menu.html" name="menu">
+ <FRAME src="drawingcap.html" name="content">
+ <NOFRAMES></NOFRAMES>
+ </FRAMESET>
+</HTML>
+
diff --git a/graphics/jpicedt/doc/menu.html b/graphics/jpicedt/doc/menu.html
new file mode 100644
index 0000000000..744ac76b01
--- /dev/null
+++ b/graphics/jpicedt/doc/menu.html
@@ -0,0 +1,22 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE>jPicEdt 1.3.2 Help Content </TITLE>
+ </HEAD>
+
+ <BODY BGCOLOR="#ffffff">
+ <H2>jPicEdt 1.3.2 On-line Help</H2>
+ <table>
+ <tr><td><A HREF="commandline.html" target="content">1.Command line</A></td></tr>
+ <tr><td><A HREF="drawingcap.html" target="content">2.Drawing objects</A> </td></tr>
+ <tr><td><A HREF="editing.html" target="content">3.Editing objects</A> </td></tr>
+ <tr><td><A HREF="actions.html" target="content">4.Menus and toolbars</A> </td></tr>
+ <tr><td><A HREF="preferences.html" target="content">5.Setting preferences</A> </td></tr>
+ <tr><td><A HREF="parsing.html" target="content">6.Parsing TeX files</A></td></tr>
+ <tr><td><A HREF="scripting.html" target="content">7.Scripting</A></td></tr>
+ <tr><td><A HREF="http://www.jpicedt.org">http://www.jpicedt.org</A> </td></tr>
+ </table>
+</BODY>
+</HTML>
+
diff --git a/graphics/jpicedt/doc/parsing.html b/graphics/jpicedt/doc/parsing.html
new file mode 100644
index 0000000000..169312198f
--- /dev/null
+++ b/graphics/jpicedt/doc/parsing.html
@@ -0,0 +1,158 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <META key="author" CONTENT="Sylvain Reynal">
+ <TITLE>jPicEdt 1.3.2 Help Content </TITLE>
+ </HEAD>
+
+ <BODY BGCOLOR="#ffffff">
+
+ <H2>Parsing input files</H2>
+
+ <P>When parsing input files, jPicEdt can handle a variety of, say,
+ syntax <I>deviations</I>... I carved it fairly robust :-), and you
+ needn't worry too much about whether your syntax is perfectly
+ <I>LaTeX-, epic- or PsTricks- compliant</I> or not, since jPicEdt will issue a pretty
+ informative message as soon as it finds a syntax error, an incorrect
+ format number, etc... However, we strongly encourage you to follow
+ these rules :</P>
+ <UL>
+ <LI>jPicEdt expects to find a
+ <CODE>\unitlength</CODE> or a <CODE>\psset{unit=xxx}</CODE> (or xunit, yunit, runit)
+ command at the very beginning of your file, or at least before the
+ first command you want to be processed ; it not, default unitlength will be
+ assumed, e.g. 1cm for PsTricks until one of these commands are found.
+ </LI>
+ <LI>jPicEdt accepts almost every command of the LaTeX picture
+ environment, the epic/eepic packages, and the PsTricks base-package, though for the later
+ add-ons packages are not supported yet, e.g. pst-nodes.sty or pst-coils.sty.
+ <code>\multiput</code> (and its PsTricks equivalent) are not handled yet.
+ </LI>
+ <li>
+ It is perfectly possible to mix LaTeX, eepic and Pstricks commands in the same file.
+ PsTricks default parameters (those set by <code>\psset</code> commands) won't interfere
+ with LaTeX or eepic ones (e.g. <code>linethickness</code>).
+ </LI>
+ <li>As of LaTeX boxes (e.g. framebox,...), don't expect true WYSIWYG behaviour ! JPicEdt doesn't
+ embed any TeX compiler, hence only a limited set of LR-commands is handled (specifically : only
+ very commands related to the picture environment, see <i>LaTeX, a documentation preparation system,
+ Leslie Lamport, p.97 and p.108</i>).
+ </li>
+ <li>The parsing process ends if, either an End-of-file is encountered, or a
+ <code>\end{picture}</code> (or its equivalent for PsTricks) is found.
+ </UL>
+
+<P>In case you are still fathoming out what those weird comment lines that jPicEdt adds to your
+file really mean, here are some hints. We rely on this trick for commands that cannot be put on a single line : using a
+<i>%Begin</i> and <i>%End</i> blocks is a way of making jpicedt understand that every command that lies
+inside the block belongs to the same graphical element, e.g. a circle, a line,.... Obviously,
+for graphical elements whose
+formatted string holds on a single line (which is always the case for PsTricks, so far),
+there's no need to rely on this trick however.
+</P>
+<p><i>Note : this small grammar was designed at a time where only the LaTeX picture environment and the
+epic/eepic package were handled by jPicEdt.
+Don't expect to find parameters related to colours, shadows or textures ! (please use PsTricks in this case).
+Only rules needed to properly represent a compound graphical object with the set of graphical attributes
+offered by the eepic package are part of this grammar, no less, no more...</i>
+<TABLE BORDER=3 CELLPADDING=2 CELLSPACING=2>
+ <TR>
+ <TD><P>Line</P></TD>
+ <TD><P>%Line 0 0 (x1,y1)(x2,y2)<BR>%End Line</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Vector (arrow on first end)</P></TD>
+ <TD><P>%Line 1 0 (x1,y1)(x2,y2)<BR>%End Line</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Vector (arrow on second end)</P></TD>
+ <TD><P>%Line 0 1 (x1,y1)(x2,y2)<BR>%End Line</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Vector (two arrows)</P></TD>
+ <TD><P>%Line 1 1 (x1,y1)(x2,y2)<BR>%End Line</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Dashed line (or vector) *</P></TD>
+ <TD><P>%Line 0 0 (x1,y1)(x2,y2) dash=value_in_mm<BR>%End Line</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Ellipse (hollowed)</P></TD>
+ <TD><P>%Ellipse (x_centre,y_centre)(width)(height)<BR>%End Ellipse</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Black-, gray- or white-filled ellipse *</P></TD>
+ <TD><P>%Ellipse (x_centre,y_centre)(width)(height) blacken|shade|whiten<BR>%End Ellipse</P>
+ </TD>
+ </TR>
+ <TR>
+ <TD><P>Dashed ellipse *</P></TD>
+ <TD><P>%Ellipse (x_centre,y_centre)(diameter)(diameter) dash=value_in_mm<BR>%End Ellipse</P>
+ </TD>
+ </TR>
+ <TR>
+ <TD><P>Arc</P></TD>
+ <TD><P>%Ellipse (x_centre,y_centre)(diameter)(diameter) arcStart=angle_in_degree arcExtent=angle_in_degree<BR>%End Ellipse</P>
+ </TD>
+ </TR>
+ <TR>
+ <TD><P>Rectangle (First point = bottom left corner ; second point = top right corner)</P></TD>
+ <TD><P>%Rectangle(x1,y1)(x2,y2)<BR>%End Rectangle</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Black-, gray- or white-filled rectangle *</P></TD>
+ <TD><P>%Rectangle(x1,y1)(x2,y2) blacken|shade|whiten<BR>%End Rectangle</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Dashed rectangle</P></TD>
+ <TD><P>%Rectangle(x1,y1)(x2,y2) dash=value_in_mm<BR>%End Rectangle</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Bezier splines (quadratic)</P></TD>
+ <TD><P>%Bezier 0 0 (x1,y1)(x_control,y_control)(x2,y2)<BR>%End Bezier</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Bezier splines (quadratic) with an arrow on the first point</P></TD>
+ <TD><P>%Bezier 1 0 (x1,y1)(x_control,y_control)(x2,y2)<BR>%End Bezier</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Bezier splines (quadratic) with an arrow on the second point</P></TD>
+ <TD><P>%Bezier 0 1 (x1,y1)(x_control,y_control)(x2,y2)<BR>%End Bezier</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Bezier splines (quadratic) with two arrows</P></TD>
+ <TD><P>%Bezier 1 1 (x1,y1)(x_control,y_control)(x2,y2)<BR>%End Bezier</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Filled Polygons (possibly closed) *</P></TD>
+ <TD><P>%Polygon (x1,y1)...(xN,yN) blacken|shade|whiten closed<BR>%End Polygon</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Dashed Polygons (possibly closed)</P></TD>
+ <TD><P>%Polygon (x1,y1)...(xN,yN) dash=value_in_mm closed<BR>%End Polygon</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Begin group</P></TD>
+ <TD><P>%Begin group</P></TD>
+ </TR>
+ <TR>
+ <TD><P>End group</P></TD>
+ <TD><P>%End group</P></TD>
+ </TR>
+ <TR>
+ <TD><P>Text</P></TD>
+ <TD><P>See LaTeX and PsTricks documentation about using \makebox,\framebox, \dashbox, \psframebox,... commands.</P></TD>
+ </TR>
+</TABLE>
+<p>Please note : </p>
+<ul>
+<li>commands marked with an * are supported by eepic only.</li>
+<li>Order of optional params (such as dash=..., fill-colour, etc...) is not significant.</li>
+<li>Cubic splines, which are not
+ supported by the LaTeX picture environment, are converted to a pair of quad
+ splines before formatting (see "Numerical Recipes in Fortran" for the algorithm
+ used to convert a cubic to two quads).</li>
+</ul>
+</BODY>
+</HTML>
diff --git a/graphics/jpicedt/doc/preferences.html b/graphics/jpicedt/doc/preferences.html
new file mode 100644
index 0000000000..569384b069
--- /dev/null
+++ b/graphics/jpicedt/doc/preferences.html
@@ -0,0 +1,176 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <META key="author" CONTENT="Sylvain Reynal">
+ <TITLE>jPicEdt 1.3.2 Help Content </TITLE>
+ </HEAD>
+
+ <BODY BGCOLOR="#ffffff">
+
+ <H2>Setting preferences</H2>
+
+ <hr>
+ <H3>General</H3>
+ <UL>
+ <LI>Look'n feel : let you choose your
+ favorite Look'n Feel ; defaults to <I>metal</I> (a SUN look'n feel)
+ on startup.
+ <LI>Language : English, French,... </LI>
+ <LI><P>Undoable steps : let you specify the number of undoable steps
+ ; 0 means that undo is deactivated. </P></LI>
+ <li>Default content-type : this is the default formatter used when creating
+ a new drawing. The preferred way is to use PsTricks, because then you get a
+ real high quality rendering (colours, textures, shadows,...), but if you
+ don't want to rely on add-ons packages, simply choose the Emulated LaTeX
+ content-type (then you'll get only a minimal subset of those graphical attributes,
+ i.e. no-filling, no colours,...). The epic/eepic choice is a reasonable
+ choice for those who don't need colours and textures, but are
+ willing to draw ellipses, arcs, polygons,... with a satisfying rendering quality.
+ Note also that PsTricks uses PostScript in the background so if your DVI
+ Viewer dooesn't handle PostScript special, use <code>dvips</code> first to
+ convert your DVI file to a PS file, then run <code>ghostscript</code> to
+ display it.
+</UL>
+<P>You must restart jPicEdt if you want a new language choice to take
+effect.</P>
+
+ <hr>
+
+
+<H3>LaTeX, epic and PsTricks tab panes</H3>
+<p>Let you set format specific parameters.
+One thing common to all formats is the prolog/epilog string, and
+is used when running LaTeX on your picture from within
+jPicEdt.
+<br>
+These strings get prepended/appended to
+the text generated by the formatter (i.e. the text starting with <code>\begin{picture}</code>) so that the
+resulting text is a &quot;stand-alone&quot; LaTeX file, and can be directly compiled by
+LaTeX. The default prolog/epilog simply include necessary packages, but you can add your own
+macro definition here, so that, for example, arguments of text-boxes which use macros of your own are
+compiled properly.
+
+
+<P>Unitlength is always set to 1 mm at the beginning of
+the saved file. OK, this is rather stringent, but (useless to say) you
+sure CAN load a file containing a different value ! jPicEdt will
+simply scale the drawing accordingly. (There's actually another
+efficient way to scale the entire drawing by using the SCALE tool in the
+tool-bar).
+
+<H4>LaTeX picture environment specific parameters</H4>
+
+<UL>
+ <LI><B>Linethickness</B> : set the default
+ linethickness (in <B>mm</B>). This value is used when loading a TeX file only, when
+ no <code>\linethickness</code> has been found.
+
+ <LI><B>Max LaTeX circle/disk diameter</B> : this depends on your own LaTeX installation.
+ You'll have to set it to
+ the biggest circle/disk diameter contained in your LaTeX font
+ (actually, 14mm for circles, and 5.4mm for disks, which incidentally
+ are the default values, match almost every TeX distribution).
+
+
+</UL>
+<P>LaTeX picture environment only allows for a small number of line
+slopes ; in <B>emulated mode</B>, jPicEdt use the <CODE>\multiput</CODE>
+command to emulate lines of any slope, using a set of very closed and
+tiny horizontal or vertical segments. As a result, lines of any
+thickness can now be drawn (FYI, the <CODE>\thickness</CODE> command
+doesn't work with standard slanted lines).
+</P>
+<UL>
+ <LI><B>Emulated line segment length</B>
+ : this is the length of the small segments that compose emulated
+ lines.
+ </LI>
+ <LI><B>Emulated line max slope</B> :
+ when do we have to switch between an almost (hence emulated)
+ vertical emulated line and a TRUE vertical line ?
+ </LI>
+ <LI><B>Emulated circle segment length</B> : this is the length of
+ the small segments that compose emulated circles (that is, circles
+ having a radius greater than Max-LaTeX-Circle-Diameter). Note : big
+ disk can't be emulated using LaTeX picture environment commands, but
+ they can if you decide to use the <I>eepic</I> package.
+ </LI>
+</UL>
+</P>
+
+<hr>
+
+<H3>External commands</H3>
+<p>
+<B>How it works...</B>
+
+<p>
+When running LaTeX/DVI/... from within jPicEdt, a LaTeX file is created on
+the fly by jPicEdt in the standard temp' directory of the OS you're using (e.g. c:\windows\temp),
+or another temp' dir if you changed it (see Directories panel).
+The variety of operating systems and LaTeX distributions made it impossible to
+design a scheme for running external commands that wouldn't rely on scripts
+(e.g. batches under DOS, AppleScript on MacOS).
+</p>
+<P>So the best thing to do is (as for me) to use external scripts
+which call the adequate programs (latex, dviwin32.exe/xdvi,...). You can
+pass argument to this script by using the predefinite symbols
+&quot;{p}&quot; and &quot;{f}&quot;.
+ <ul>
+ <li>&quot;{p}&quot; gets replaced by your temp. directory (this is where the LaTeX file gets created),
+ e.g. <code>/tmp/</code> under Linux, <code>c:\windows\temp</code> under Win9x, etc...</li>
+ <li>
+ &quot;{f}&quot; gets replaces by the name of the temp. file (usually &quot;jpicedt&quot;
+ with a random number appended to it, e.g. &quot;jpicedt542163&quot;), w/o any &quot;tex&quot; extension.
+ </li>
+ <li>{i} gets replaced by the location of the &quot;add-ons&quot; directory where some scripts already
+ reside for some LaTeX distributions.</li>
+</ul>
+Here's an example of an external batch that will work under Linux's bash-shell :
+</P>
+<P><b>
+<CODE>#!/bin/sh</CODE><BR>
+<CODE>cd $1</CODE><BR>
+<CODE>$2 $3</CODE></B></P>
+<P>Suppose this script was saved in the &quot;add-ons&quot; directory, then
+the command line which appears under the &quot;external-commands&quot;'s
+tab in the preferences-setting tabsheet will be typesetted as
+follows:</P>
+
+<P><b><CODE>{i}/ext_proc {p} latex {f}</CODE> </b></P>
+
+<P>(where &quot;latex&quot; can be replaced by any appropriate name,
+e.g. xdvi, kghostview, kdvi,...). <p>
+This will lead, once &quot;{p}&quot; and &quot;{f}&quot; have been
+replaced, to :
+<p>
+ <b><code>ext_proc /tmp latex jpicedt46858</code></b>
+<p>which finally yields,
+<p>
+ <b><code>cd /tmp</code><br>
+ <code>latex jpicedt46858</code></b><p>
+ (latex accept a file w/o extension on the command line, otherwise add ".tex"
+ manually in your script).
+</P>
+
+ <B>Loading predefined configurations</B>
+ <P>
+ There currently exist scripts and predefined configurations for the following LaTeX distribution :
+ </P>
+ <p>
+ <ul>
+ <li>Unix : TeTeX</li>
+ <li>Windows : MikTeX, WinGUT, and ScientificWorkplace.</li>
+ </ul>
+ These scripts reside in the <b>add-ons</b> subdirectory of where jPicEdt got installed
+ (you need to have installed the <b>add-ons</b> package during jPicEdt's installation).
+ <br>
+ To load a predefined configuration file, go to the Preferences->Commands pane,
+ press the <b>LOAD PREDEFINED CONFIGURATION</b> button, and browse the directory tree until
+ you find a file matching your LaTeX distribution.
+</p>
+<HR>
+</HR>
+</BODY>
+</HTML>
diff --git a/graphics/jpicedt/doc/scripting.html b/graphics/jpicedt/doc/scripting.html
new file mode 100644
index 0000000000..8e054d51d6
--- /dev/null
+++ b/graphics/jpicedt/doc/scripting.html
@@ -0,0 +1,92 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <META key="author" CONTENT="Sylvain Reynal">
+ <TITLE>jPicEdt 1.3.2 Help Content </TITLE>
+</HEAD>
+
+<BODY BGCOLOR="#ffffff">
+
+ <H2>Using and writing BeanShell scripts</H2>
+
+ <p>
+ jPicEdt now supports scripting (aka "macros") through an embedded BeanShell interpreter. BeanShell is a
+ lightweight, extensible and embedabble scripting extension to Java, written by
+ Pat Niemeyer (pat@pat.net). It follows the Java grammar (though with higher tolerance towards
+ syntax errors ; in particular it has weak typing capabilities),
+ hence anyone having a smattering of Java can write BeanShell scripts.
+ </p>
+
+ <p>
+ A comprehensive documentation about BeanShell can be found at :
+ <a href="http://www.beanshell.org">www.beanshell.org</a>. Yet scrutinizing into
+ the scripts shipped with jPicEdt is a good starting point. You might also need the
+ <b>jPicEdt API documentation</b> at some point (please download it from www.jpicedt.org),
+ especially if you would like to
+ write scripts involving complex operations. The <b>jpicedt.JPicEdt</b> class offers
+ a variety of static methods (e.g. <code>JPicEdt.newBoard()</code>)
+ that might fullfill basic needs. Other classes of importance are :
+ </p>
+ <ul>
+ <li><b>jpicedt.ui.MDIManager</b> for managing drawing-boards (creating a new board, moving it, cascading boards,...)</li>
+ <li><b>jpicedt.ui.PEDrawingBoard</b> and <b>jpicedt.graphic.PECanvas</b> (PEDrawingBoard comprises a PECanvas
+ and a PEScrollPane) for interacting with selected objects, zooming, performing I/O operations, or even
+ fiddling about with the UndoManager :-), ...</li>
+ <li><b>jpicedt.graphic.model.Drawing</b> for adding objects to a drawing-board ;</li>
+ <li><b>jpicedt.graphic.model.Element</b> and concrete implementations (ellipses, rectangles,...)
+ for altering objects shape and attributes ;</li>
+ <li><b>jpicedt.graphic.view.View</b> and concrete implementations (ellipses, rectangles,...)
+ for changing how object LOOK on the screen (but not how they're formatted to a LaTeX string);</li>
+ <li><b>jpicedt.graphic.toolkit.EditorKit</b> for changing the way objects are edited with the mouse
+ (that is, either altering existing behaviours, or adding new ones).</li>
+ <li>Classes in the <b>jpicedt.format.*</b> package, for interacting with content-types,
+ i.e. changing the way objects are formatted to LaTeX
+ and/or TeX-file are parsed for a given format (LaTeX, eepic,...).</li>
+ </ul>
+ </p>
+ <p>
+ All those classes are easily extensible, and can be plugged to each other (well, the so famous
+ View-Model-Controller scheme, like...).
+ Besides, <b>jpicedt.JPicEdt</b> and <b>jpicedt.graphic.toolkit.EditorKit</b> contains a variety
+ of <i>Actions</i> (implemented as static classes) that you can subclass, then add to your own graphical
+ interface. Look at the documentation in <b>jpicedt.graphic.toolkit.PEAction</b> to know what is an
+ <i>Action</i> and how you may use it into your own code.
+ </p>
+ <p>
+ For convenience, some useful variables and methods have been predefined, and are available on start-up
+ both in the BSH Console, and
+ from scripts being run from the script-menu. These are :
+ </p>
+ <ul>
+ <li><b>board()</b> : return the currently selected PEDrawingBoard, or null if there's no open board ;</li>
+ <li><b>canvas()</b> : return a reference to the active PECanvas, i.e. being hosted by the currently selected PEDrawingBoard ;</li>
+ <li><b>drawing()</b> : return a reference to the Drawing (aka MODEL) attached to the active PECanvas ;</li>
+ <li><b>editorkit()</b> : return a reference to the EditorKit (aka CONTROLER) attached to the active PECanvas ;</li>
+ <li><b>mdimgr</b> : predefined variable referencing the current MDIManager.</li>
+ <li><b>clipboard</b> : predefined variable referencing the local clipboard shared across all drawing boards
+ (as opposed to the system's clipboard,
+ which you can access from jPicEdt using the Paste Special menu item, yet which doesn't accept anything else but
+ text data) ; needed for copying and pasting things from/into a PECanvas.</li>
+ <li><b>preferences</b> : predefined variable referencing a Properties object holding user's prefs.</li>
+ </ul>
+
+ <h2>OK, where do I put my scripts ?</h2>
+ <p>
+ User's scripts must reside in the "macros" subdirectory of the user-settings directory
+ (for instance, /home/user/.jpicedt/macros on Unix).
+ Scripts must have a ".bsh" extension.
+ Names having underscores will have these replaced by white-spaces
+ in the script-menu (e.g. Repeat_copy.bsh will show up as "Repeat copy").
+ You can call other scripts from inside a script by using
+ the BSH <code>source(path_to_other_script)</code> command, and even add your own classes by using
+ the <code>addClassPath()</code> command.
+ </p>
+ <p>
+ Use the BSH console to test your script, then put them in the script-directory and they'll show up!
+ </p>
+</BODY>
+</HTML>
+
+
+
diff --git a/graphics/jpicedt/jPicEdtReadme_1_3_2.html b/graphics/jpicedt/jPicEdtReadme_1_3_2.html
new file mode 100644
index 0000000000..dad571ecee
--- /dev/null
+++ b/graphics/jpicedt/jPicEdtReadme_1_3_2.html
@@ -0,0 +1,62 @@
+<html>
+<body>
+<H1>Running the installer</H1>
+ <p>
+ You need a JDK >= 1.3, which you can download from either
+ <a href="http://java.sun.com">Java.SUN</a> (Windows, Unix),
+ <a href="http://www-106.ibm.com/developerworks/java/jdk/linux140/">IBM's developerworks</a>
+ (especially suited for Linux), or
+ <a href="http://www.blackdown.org">Blackdown</a> (direct Linux port of SUN's
+ implementation). MacOS users may
+ refer to <a href="www.apple.com">Apple</a> website for instruction about
+ installing Java on MacOS.
+ <p>
+ Then simply type :
+ <br>
+ <code>java -jar jpicedt-install.jar</code>
+ <br>
+ in a Unix-console or a DOS-commando,
+ or double-click the JAR file (Windows's
+ </P>
+
+<h1>Getting the latest release</h1>
+ Just visit jPicEdt's official website at <a href="http://www.jpicedt.org">www.jpicedt.org</a>.
+
+<h1>What is jPicEdt ?</h1>
+
+ <p>
+ jPicEdt is a software aimed at alleviating the burden of using PsTricks, eepic or LaTeX's picture environment macros in a LaTeX file.
+ It allows the user to draw graphical objects using graphic primitives (e.g. splines, arcs, polygons,...), position them
+ easily with the mouse, and add text using LaTeX/PsTricks box commands (e.g. dashbox, psframebox,...). Yet this is not a 100% WYSIWYG software,
+ and arguments of box commands are displayed as is (jpicedt doesn't include any TeX compiler !).
+ </p>
+ <p>
+ As of release 1.3.2, pictures can be saved to one of the three following formats :
+ <ul>
+ <li>LaTeX's standard picture environment, including emulated objects, e.g. lines of any slope</li>
+ (which LaTeX doesn't support natively), circles of any size, ellipses, arcs and polygons.
+ <li>epic/eepic, including dashed lines, shading, filled arcs,... </li>
+ <li>PsTricks macro packages : almost every macro in the pstricks.sty package are supported, yet support for add-ons (i.e. pst-node.sty, pst-coil.sty
+ and gradient.sty) is still underway.
+ </li>
+ </ul>
+ </p>
+ <p>
+ jPicEdt can also parse files that include macros in one of these three formats.
+ This allows in particular to load files generated by
+ GnuPlot with a "gset term eepic" or "gset term pstricks" command.
+ </p>
+ <p>
+ jPicEdt is written in Java, and is therefore 100% multiplatform. Older releases (1.2 and older) are JDK1.1.x compliant ;
+ current release works with any JDK 1.3 or 1.4.
+ Latest JDK1.1-compliant releases can be downloaded at
+ <a href="http://www.jpicedt.org">http://www.jpicedt.org/</a>.
+ <p>
+ jPicEdt is free software, and is licensed under GNU Public License.
+ It has i18n support for the english, french, portuguese and spanish languages.
+ </p>
+
+
+
+</body>
+</html>