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

Quick Search    Search Deep

jpicedt.format.pstricks.parser: Javadoc index of package jpicedt.format.pstricks.parser.

Package Samples:

jpicedt.format.pstricks.parser: Classes (formatter, view factory,...) related to the PsTricks content-type.  


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 ...
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 ...
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: 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 ...
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.
PstricksParser: Root expression for the Pstricks parser, containing grammar rules for the pstricks format. Pstricks support is pretty ok, though add-ons (like pst-nodes.sty) are still missing. This class consists of grammar rules, wrapped in a RootExpression which can itself be directly added to the main tree (for instance, using DefaultParser.addGrammar()). Note : the current parser used across the JPicEdt application can be retrieved using jpicedt.JPicEdt.getParser(). [TODO] : \psgrid, \psaxes, arrow size, dot style.
PsPolygonExpression: Parses \\pspolygon, \\psdots and \\psline commands : \\pspolygon[param](2,4)(3,15) // NO ARROW ALLOWED HERE ! \\pspolygon*[param](5,1)(5,8)...(xN,yN) \\psline[param]{arrows}(5,1)(5,8)...(xN,yN) \\psline*[param]{arrows}(5,1)(5,8)...(xN,yN) \\psdots[param]{arrows}(5,1)(5,8)...(xN,yN) \\psdots*[param]{arrows}(5,1)(5,8)...(xN,yN) (same as above, '*' being unused) Note : PsPolygon -> close path ; PsLine -> open path ; PsDots -> dots only
PSTColorExpression: Used by PSTParametersExpression to parse statements involving colours, for instance "linecolor=green" (predefined colour) or "fillcolor=MyGray" (user-defined colours). If no pstricks's native colour matches the RHS, we fetch a HashMap from the Pool's hashtable (value associated with key PstricksParser.KEY_USER_COLOURS) and look up the given colour ; this HashMap may've been filled by UserDefinedColorExpression in the course of the parsing process.
PSTArrowExpression: Parses Pstricks's arrows, as given by the PsTricks's documentation (p.29). This is based on the following rules : an opening "{" ; " ", "(",... or even "", to set the first arrow ; a "-" in the middle ; same thing on the right side to set the second arrow ; a closing "}". If this expression is successfully parsed, the attribute set associated with the Pool's currentObj is modified accordingly.
PsEllipticalArcExpression: See PicEllipseFormater for details on the trick used to build elliptical arcs %PSTEllipticArc arcStart=xxx arcExtent=xxx \psclip{\pswedge[linecolor=white](xC,yC){radius}{Ang1}{Ang2}}\psellipse[param](xC,yC)(hradius,vradius)\endpsclip %End PSTEllipticArc We expect the parsed expression to have EXACTLY the same syntax as that produced by the formatter. [pending] of course, need to be improved ! Not used anymore.
BeginPsPictureExpression: \begin{pspicture}(x0,y0)(x1,y1) -> defines a box with BL=(x0,y0) and TR=(x1,y1) \begin{pspicture}*(x0,y0)(x1,y1) -> clipped \begin{pspicture}[baseline](x0,y0)(x1,y1) -> changes baseline (see pstricks's doc p.41) \begin{pspicture}[](x0,y0)(x1,y1) -> baseline passes across the origine And the same commands with \pspicture (that is, TeX-like).
PsBezierExpression: Rules for parsing cubic splines with a PsTricks syntax : \\psbezier[parameters]{arrows}(x0,y0)(x1,y1)(x2,y2)(x3,y3) \\psbezier*[parameters]{arrows}(x0,y0)(x1,y1)(x2,y2)(x3,y3) or PsTricks's object previously defined by help of a \\newpsobject command.
PSTPicPointExpression: an expression that parses "(x,y)" string (PsTricks-like PicPoint) and gives the corresponding numerical values to the point number "ptNumber" of the current Element (see jpicedt.graphic.model.Element interface for details on the setPoint()/getPoint() methods).
PsArcExpression: Parses \\psarc commands : \\psarc[parameters]{ }(x0,y0){rad}{angleA}{angleB} ; where at least "arrows" or (x0,y0) args must be included \\psarc*[parameters]{ }(x0,y0){rad}{angleA}{angleB} ; idid. but filled
EndPsPictureExpression: \end{pspicture} and/or \endpspicture. A ParserException.EndOfPicture is thrown when this expression gets successfully parsed, which give a chance to the receiver to end up the parsing process here.
PsObjectExpression: Handles \\newpsobject{myobj}{ps_object}{par1=val1,...} , for instance \\newpsobject{myline}{psline}{linecolor=green} (param is optional, though in this case, it'd be pretty useless!)
StarExpression: Handles (usually optional) "*" after \\psframebox,\\pspolygon,... by setting FILL_STYLE to SOLID. Note : this expression is NOT implemented as an OptionalExpression !
PSTBooleanExpression: Used by PSTParametersExpression to parse statements involving true/false parameters values, for instance "shadow=true" or "shadow=false" ...
PSTInstanciationExpression: Instanciates a new Element by cloning the given object, when the given tag gets found. Then adds it to the current PicGroup in the Pool.
PsEllipseExpression: Parses \\psellipse commands : \\psellipse[parameters](x0,y0)(hrad,vrad) \\psellipse*[parameters](x0,y0)(hrad,vrad)
PSTAngleParameter: Used by PSTParametersExpression to parse statements involving angles, for instance "hatchangle=45" or "shadowangle=90".

Home | Contact Us | Privacy Policy | Terms of Service