Home >> All >> jpicedt >> graphic >> io >> [ parser Javadoc ]

•	jpicedt.graphic.io.parser.eepic.* (2)	•	jpicedt.graphic.io.parser.latex.* (10)
•	jpicedt.graphic.io.parser.picedt.* (9)	•	jpicedt.graphic.io.parser.pstricks.* (26)

• jpicedt.graphic.io.parser: Javadoc index of package jpicedt.graphic.io.parser.


Package Samples:

• jpicedt.graphic.io.parser.eepic
• jpicedt.graphic.io.parser.latex
• jpicedt.graphic.io.parser.picedt
• jpicedt.graphic.io.parser.pstricks

Classes:

• 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 ...
• 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 ...
• 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
• 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.
• 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.
• EnclosingExpression: An expression that can encompass a sub-expression it encloses with markers, e.g. "{" + sub-expression + "}" The interpret() methods work as follows : look up an endMarker matching beginMarker in Context.getRemainingSubstring (that is, skip enclosed blocks with the same markers type) set this endMarker as the new Context's endMarker save enclosed expression as "value", and interpret it restore old Context's endMarker
• 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 !
• LaTeXParser: LaTeX (including epic/eepic and pstricks macros) parser This class consists essentially of LaTeX grammar rules (subexpression included in the "root" sequence expression) and a method "parse()" which kicks off the parsing process. Being a SequenceExpression, this is indeed the root expression, which encompasses every other grammar rules as childrens of this SequenceExpression.
• Context: A class that stores context information about the parsing process, like : current line number, current parsed substring, block markers, stack for markers... By convention, end markers (EOF, EndOfBlocks, ...) always refer to a position one character ahead of the last character (e.g. of the block), so that String.substring() works properly w/o adding 1 to the end-index.
• LaTeXBoxExpression: Used by LaTeXPutExpression - PicText : argument = \\makebox(w,h)[vh]{text or LaTeX command} \\framebox(w,h)[vh]{text or LaTeX command} \\dashbox{dash}(w,h)[vh]{text or LaTeX command} interpret(c) return false if none of this has been found, and cursor position is left unchanged
• PSTColorExpression: expression involving colours, e.g. "linecolor=green" (predefined colour) or "fillcolor=MyGray" (user-defined colours) If no native colour is found that matches the RHS, we look up the hashtable "userDefinedColors" in the parser's pool This hashtable may've been filled by UserDefinedColor in the same package.
• LineThicknessExpression: \linethickness or \thinlines or \thicklines or (eepic) \Thicklines Legal syntax : \linethickness{0.4pt} \linethickness{0.4mm} \linethickness{0.4cm} \linethickness{0.4} // en mm par défaut note : 1pt = 1/72.27 inch = 0.3515 mm cf. LaTeX Book (Leslie Lamport) p.192
• BeginPsPictureExpression: PsTricks : \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
• ParserException: An Exception manager used by Parsers The main purpose is to build a meaningfull string so that the user may be able to know where the syntax error comes from and what kind of error it is. See also the various locale strings starting with "ParserException" in the resource files.
• DefaultParser: Default implementation of the parser interface [pending : create interface !]. This expression doesn't contains rules in itself. On the contrary, it simply lumps sub-trees together, each sub-tree containing grammar rules for a particular format, e.g. PsTricks, epic,...
• 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).
• LaTeXPicPointExpression: an expression that parses "(x,y)" string (LaTeX-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).
• PsPolygonExpression: PsPolygon -> close path ; PsLine -> open path. \\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)
• PicLineExpression: PicLine : %Line 0 0 (x0,y0)(x1,y1) dash=value %Line 0 1 (x0,y0)(x1,y1) dash=value %Line 1 0 (x0,y0)(x1,y1) dash=value %Line 1 1 (x0,y0)(x1,y1) dash=value (dash is optional) Any string (\multiput, etc...) %End Line
• WordExpression: A string, - either composed of letters only, or letters and digits (see java.lang.Character.isLetter() for details) only, - or ended by the specified end-delimiter (in which case it may contain other chars than letters)
• PSTInstanciationExpression: instanciates a new Element by cloning the given object, when it finds the given tag, then adds it to the current PicGroup ; same as InstanciationExpression except that we use pool.pstSet instead of pool.ltxSet
• PsLineExpression: \\psline[linecolor=blue,linewidth=1,linestyle=dashed,dash=0.1 0.1]{>->>}(2,4)(3,15) \\psline(5,1)(5,8)...(xN,yN) \\psline* ... [todo] - handle polylines (with more than two points) and "\\psline*"

Home | Contact Us | Privacy Policy | Terms of Service