Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

jpicedt.format.* (81)jpicedt.graphic.* (151)jpicedt.test.* (2)jpicedt.ui.* (30)
jpicedt.widgets.* (9)

jpicedt: Javadoc index of package jpicedt.


Package Samples:

jpicedt.ui.action: Some classes and interfaces that help building concrete implementation of MDIManager's.  
jpicedt.ui.util: Some classes and interfaces that help building concrete implementation of MDIManager's.  
jpicedt.format.latex.parser: Classes (formatter, view factory,...) related to the LaTeX (standard) content-type.  
jpicedt.format.eepic.parser: Classes (formatter, view factory,...) related to the epic/eepic content-type.  
jpicedt.format.pstricks.parser: Classes (formatter, view factory,...) related to the PsTricks content-type.  
jpicedt.format.pstricks: Contains the main JPicEdt class, as well as some utilities.  
jpicedt.widgets: Contains the main JPicEdt class, as well as some utilities.  
jpicedt.graphic.view: jPicEdt library core classes and packages.  
jpicedt.format.eepic
jpicedt.format.latex
jpicedt.graphic.event
jpicedt.graphic
jpicedt.graphic.grid
jpicedt.graphic.io.formatter
jpicedt.graphic.io.parser.eepic
jpicedt.graphic.io.parser
jpicedt.graphic.io.parser.latex
jpicedt.graphic.io.parser.picedt
jpicedt.graphic.io.parser.pstricks
jpicedt.graphic.model

Classes:

PECanvas: This is a JComponent on which graphic elements are drawn. It's has an underlying model (a Drawing) to represent the content, an EditorKit to manipulate the content, and a View responsible for rendering the content. EditorKit, Drawing, and View's are pluggable : the EditorKit is responsible for creating 1) a default Drawing and 2) a ViewFactory that will populate the View tree associated with the Drawing, by attaching a View to each element in the model. Depending on the content type this Component is loaded with, it may plug a new EditorKit on-the-fly that's suited for the given content type (e.g. ...
EditorKit: A pluggable EditorKit for a PECanvas, that mainly provides mouse-tool management, e.g. zooming, selecting and drawing capabilities, together with a set of Action's. Action's that make sense for this EditorKit are implemented as static inner classes to reduce name space. They can be shared across multiple PECanvas through the use of an ActionDispatcher given to the Action constructor. New mouseTool's can be registered via the registerMouseTool method ; they're backed by a hashMap, and can be activated (i.e. set as the current mouse-tool) by using setCurrentMouseTool with the tool name as the parameter ...
View: a View is a graphic representation of a Element. It can be rendered using its paint method. It provides the following capabilities : Rendering to a Graphics2D context ; Highlighting ; Mouse-hit testing (this is here because a View knows better than anyone how a graphic element looks on the screen, and thus where a user should click to select/whatever/... the element). As an example, consider a rectangle element that has a "fill-color" attribute set to "green", and is indeed paint in green in some View implementation, but is transparent in some other implementation : then when the user clicks inside ...
RunExternalCommand: A class implementing methods for calling external processes like latex, (x)dvi, ghostscript... on the current picture file (e.g. the active internal frame) A "tmp" file is generated on-the-fly in the "tmp" directory of the underlying platform, This tmp file contains an adequate preamble (e.g. usepackage{epic}) depending on current options, and LaTeX commands (or PsTricks or eepic commands) corresponding to each object found in the given picture. These command lines may include the following special symbols : - {f} : tmp file name w/o extension (the user need to specify explicitely any extension ...
PSTParametersExpression: PsTricks graphics parameters, e.g. : - either "[linewidth=5pt, fillcolor=blue,...]" associated with an object command (\\psline...) - or the same thing w/o opening and closing brackets, and in this case it's a register command (e.g. \\psset{...}) Currently supported parameters : - xunit, yunit, runit, unit - linestyle=xxx - linewidth=xxx (with unit) + dash'n dot parameters - linecolor=xxx (may be a native PsTrick colour, see predefined colours in PsTricksFormater, OR a user-defined colours) - fillstyle=xxx - fillcolor=xxx (same note as for linecolor) - shadow parameters - hatch parameters. If pushInObject ...
LatexConstants: "emulated latex" parameters : these parameters get used by LatexFormatter, LatexParser and LatexViewFactory. lineThickness : (mm) ; used when parsing LaTeX file, when no \\lineThickness command is found emLineLength : (mm) when in "em. latex" mode, a line whose slope doesn't match an existing LaTeX slope (cf. picture environment) is emulated by tiny horizontal and/or vertical segments ; this parameter determines the length of these segments maxLatexCircleDiameter (mm) : circles whose diameter is greater than this value are emulated ; this ususally depends on available "lasym" fonts maxLatexDiskDiameter ...
Element: An interface for graphic elements that can be added to a Drawing. A graphic element is basically defined by : A set of control-point (sometimes called end-points) that specify their geometry An attribute set A parent and possibly children once the element has been added to a tree defining a model. This allows us to let the root element only hold state about the tree while still maintaining the ability for a child to retrieve this state at any time through a (possibly recursive) call to getParent. Besides, each Element may have a View attached to it (but this is not necessary as long as it has not ...
PEAction: An abstract subclass of Swing's AbstractAction that can (but may as well not) be shared across multiple PECanvas. This implementation uses the same set of properties as AbstractAction. The constructor gives a convenient way of automatically building localized properties associated with this PEAction from a simple String (the "actionName" parameter), using a user-provided ActionLocalizer. Note : if an ActionLocalizer is provided to the constructor, and some of its methods return null values, the corresponding properties are set to null. However, all jPicEdt components (e.g. PEMenu, PEToolBar,...), ...
PSTParametersExpression: PsTricks graphics parameters, e.g. "linewidth=5pt, fillcolor=blue,..." (no leading, nor trailing brackets, these should be added to an enclosing expression) Currently supported parameters : xunit, yunit, runit, unit linestyle=xxx linewidth=xxx (with unit) + dash'n dot parameters linecolor=xxx (may be a native PsTrick colour, see predefined colours in PsTricksFormater, OR a user-defined colours) fillstyle=xxx fillcolor=xxx (same note as for linecolor) shadow parameters hatch parameters. Depending on the value of "attributeSetKey" given to the constructor, these parameters may act on the attribute ...
PicTextFormatter: A formatter for PicText objects in the PsTricks format : \\rput[refpoint]{rotation}(x,y){stuff} where : stuff can be any of the following : \\psframebox[param]{text}} \\pscirclebox[param]{text}} \\psovalbox[param]{text}} refpoint = B|b|t for vertical and l|r for horizontal (B = baseline) rotation = any angle in degree or U,L,D,R,N,W,S or E. The following are built from "frame", "oval" or "circle", but are allegedly more efficient : \\psdblframebox[param]{stuff} % same as psframebox with doubleline=true \\psshadowbox[param]{stuff} % same as psframebox with shadow=true \\cput[shadow=true](x,y){a ...
PsUnitLengthExpression: Used by PSTParamExpression to parse statement involving the 4 pstricks length registers, that is "unit=1mm,xunit=1mm,yunit=1mm,runit=1mm" (or pt or cm), where setting "unit" sets "xunit", "yunit" and "runit" simultaneously. Parsed value are stored in Pool's hashtable using PstricksParser.KEY_X_UNIT and related keys. Note that default PsTricks's unit is 1cm ! (whereas jPicEdt default unit is 1mm) hence no unit leads to pstXunit = 0.1, etc... Allowed syntaxs are : "0.11" (i.e. cm), "0.11mm", "0.11cm", "0.11pt" According to PsTricks's doc, whitespaces are allowed ONLY after the comma (see PsTricks ...
InternalFrameMDIManager: An MDI Manager implementation for "childframe" mode (i.e. using JInternalFrame's) Layer management : PEDrawingBoard's are added to JDesktopPane.DEFAULT_LAYER (bottom most layer) Unfortunately, with the current scheme used for action dispatching, only PEDrawingBoard's can be added to the JDesktopPane. Other components (e.g. toolbars) CAN'T be used as a click on a toolbar belonging to, say, the PALETTE_LAYER, would immediately make it the active internal frame, and since action dispatching relies on the fact that the active internal frame is supposed to host a PEDrawingBoard, this wouldn't work. ...
BranchElement: An abstract class for Element's that allow children The implementation of the Collection interface is done through calls to addChild , removeChild , children , removeAllChildren , except for the addAll method which is implemented from scratch so as to fire a changed-event only once all elements have been added. As a result, subclasses only need to override these methods to change the behaviour of content-modifying methods. This element has only one control point, namely, the bottom-left corner of the bounding box. Moving this point result in a global translation of the element (no rescale, use ...
UserDefinedColorExpression: Parse statement defining user-colours, that is : \\newgray{user-def colour name}{num} (where num is a gray scale specification b/w 0 and 1) \\newrgbcolor{user-def-colour-name}{num1 num2 num3} (where num are numbers b/w 0 and 1) \\newhsbcolor{user-def-colour-name}{num1 num2 num3} (where num are numbers b/w 0 and 1) \\newcmykcolor{user-def-colour-name}{num1 num2 num3 num4} (where num are numbers b/w 0 and 1) Colour names may contain letters and numbers. Spaces are NOT allowed, except as separators b/w colour numbers. New colours are then added to the pool's hashtable associated with key = PstricksParser ...
PSTLengthParameter: Every statement involving length units (as set by PsTricks's "runit" register), e.g. "linewidth=13mm" or "doublesep=5.6" (default to current "runit") Numerical parsed value is pushed (after conversion to mm) in currentObj.attributeSet or in pool.ltx.attributeSet, depending on "pushInPool" flag. This expression contains a StatementExpression with parameters "DOUBLE" and "POSITIVE". So far, this expression parses "cm", "mm" and "pt". This expression MUST NOT be used to parse expressions that modify one of "xunit", "yunit" or "runit", since it relies on the value of these registers to compute the ...
TerminalExpression: This expression works a bit like a "CR-greedy" expression : it scans each line until it can successfully parse the reg-exp given in the constructor, POSSIBLY preceded by wild-chars (as given in the construror). Say we create a new TerminalExpression(new LiteralExpression("%End Line")>/code> (as in picedt.PicLineExpression . Then this expression will drop every line (whatever it may contain) until it finds "^(\s)*%End Line". Hence the type of WildCharExpression specified in the constructor is solely used when parsing the beginning of each line [pending] : would "CRGreedyExpression" be a more appropriate ...
PSTLengthParameter: Parses statement involving length units (as set by PsTricks's "runit" register), e.g. "linewidth=13mm" or "doublesep=5.6" (default to current "runit") Numerical parsed value is pushed in the Pool's PicAttributeSet having the given key, (after conversion to mm) This expression contains a StatementExpression with parameters "DOUBLE" and "POSITIVE". So far, this expression parses "cm", "mm" and "pt". This expression MUST NOT be used to parse expressions that modify one of "xunit", "yunit" or "runit", since it relies on the value of these registers to compute the actual length value in case no unit ...
UserDefinedColorExpression: parse expression like : - \\newgray{user-def colour name}{num} (where num is a gray scale specification b/w 0 and 1) - \\newrgbcolor{user-def-colour-name}{num1 num2 num3} (where num are numbers b/w 0 and 1) - \\newhsbcolor{user-def-colour-name}{num1 num2 num3} (where num are numbers b/w 0 and 1) - \\newcmykcolor{user-def-colour-name}{num1 num2 num3 num4} (where num are numbers b/w 0 and 1) Colour names may contain letters and numbers. Spaces are NOT allowed, except as separators b/w colour numbers. Implementation is done through an AlternateExpression. New colours are then added to the pool's UserDefinedColors ...
PsUnitLengthExpression: To be used by PSTParamExpression. "unit=1mm,xunit=1mm,yunit=1mm,runit=1mm" (or pt or cm), where setting unit sets xunit, yunit and runit simult. Default PsTricks's unit is 1cm ! (whereas jPicEdt default unit is 1mm) hence no unit leads to pstXunit = 0.1, etc... Allowed syntaxs are : "0.11" (i.e. cm), "0.11mm", "0.11cm", "0.11pt" According to PsTricks's doc, whitespaces are allowed ONLY after the comma (see PsTricks doc. page 6), though here we use a StatementExpression which swallows them, which makes it less stringent. Once parsed, we set "psXunit", "psRunit" and "psYunit" in the pool
DefaultAttributeSet: This an immutable attribute set that stores default attributes value, and can thus serve as the default resolving parent for mutable PicAttributeSet's. setAttribute method is overriden to do nothing. This set can't have any resolving parent. How to add a new attribute name : In PicObjectConstants , define a new static final PicAttributeName with an explicit name (possibly following PsTricks syntax) give it an adequate index increment value of PicObjectConstants.MaxAttributeNameIndex to reflect change. Refactored 30/03/2002 (hashtable)
PsRPutExpression: \\rput[refpoint]{rotation}(x,y){stuff} \\rput*[refpoint]{rotation}(x,y){stuff} (line-breaks being allowed b/w each "block"), where : refpoint = B|b|t for vertical and l|r for horizontal (B = baseline), used only for psframebox and rel. rotation = any angle in degree or U,L,D,R,N,W,S or E. stuff = whatever ! (this allows in particular to rotate things) Depending on the "stuff" found, instanciates : PicText : \\psframebox, \\pscirclebox, \\psovalbox, LR-argument huuu... [pending] instanciate other elements + handle rotations.
AbstractRegularExpression: This is the abstract superclass for all regular expression that build up the LaTeX parser. It mimics the RegExp scheme, while at the same time allowing expression to send ParserEvent when a piece of text was successfully parsed (instead of delegating to a separate ParserHandler, events are handled directly in the core of the action method). A Context is then used to feed successive pieces of text to the reg-exp's that build up the grammar tree, and a Pool (currently implemented as an inner class of the LaTeXParser) allow reg-exp to share data.
DefaultViewFactory: This is the default factory used to create a View for a given Element ; should be used when one wants to render all Element's attributes ; otherwise subclass with your own ViewFactory and override : createView : to return your own View for some or all Element's (then call super.createView) createStroke, createPaintForInterior, createPaintForOutline : these methods are called by various View's to extract rendering information from PicAttributeSet's when common behaviour is expected whatever the particular Element is being actually rendered.
PsRPutExpression: \\rput[refpoint]{rotation}(x,y){stuff} \\rput*[refpoint]{rotation}(x,y){stuff} where : refpoint = B|b|t for vertical and l|r for horizontal (B = baseline), used only for psframebox and rel. rotation = any angle in degree or U,L,D,R,N,W,S or E. stuff = whatever ! (this allows in particular to rotate things) Depending on the "stuff" found, instanciates : - PicText : PsBoxExpression (psframebox, pscirclebox,...) - PicPut : Non-recognized argument [pending] instanciate other elements for rotation.

Home | Contact Us | Privacy Policy | Terms of Service