Changeset 113
- Timestamp:
- 08/17/08 18:34:02 (4 months ago)
- Files:
-
- trunk/doc-en/Makefile (modified) (1 diff)
- trunk/doc-en/chapter-1-en.tex (modified) (3 diffs)
- trunk/doc-en/chapter-2-en.tex (modified) (3 diffs)
- trunk/doc-en/par-affinage-en.tex (modified) (4 diffs)
- trunk/doc-en/par-anneaux-en.tex (modified) (3 diffs)
- trunk/doc-en/par-annoterschema-en.tex (modified) (2 diffs)
- trunk/doc-en/par-axes3D-en.tex (modified) (2 diffs)
- trunk/doc-en/par-chanfrein-en.tex (modified) (2 diffs)
- trunk/doc-en/par-codejps-en.tex (modified) (2 diffs)
- trunk/doc-en/par-colorierfacettes-en.tex (modified) (5 diffs)
- trunk/doc-en/par-commandestrace-en.tex (modified) (1 diff)
- trunk/doc-en/par-couleurs-en.tex (modified) (10 diffs)
- trunk/doc-en/par-courbeR3-en.tex (modified) (1 diff)
- trunk/doc-en/par-cylindres-cones-en.tex (modified) (4 diffs)
- trunk/doc-en/par-datfile-en.tex (modified) (7 diffs)
- trunk/doc-en/par-definirfonction-en.tex (modified) (1 diff)
- trunk/doc-en/par-definirplanquelconque-en.tex (modified) (6 diffs)
- trunk/doc-en/par-definitionmaillage-en.tex (modified) (8 diffs)
- trunk/doc-en/par-eclairageponctuel-en.tex (modified) (4 diffs)
- trunk/doc-en/par-enleverfacettes-en.tex (modified) (2 diffs)
- trunk/doc-en/par-face-en.tex (modified) (1 diff)
- trunk/doc-en/par-fusion-en.tex (modified) (2 diffs)
- trunk/doc-en/par-fusionjps-en.tex (modified) (12 diffs)
- trunk/doc-en/par-geode-en.tex (modified) (4 diffs)
- trunk/doc-en/par-ligne3D-en.tex (modified) (2 diffs)
- trunk/doc-en/par-lignedeniveau-en.tex (modified) (3 diffs)
- trunk/doc-en/par-modes-en.tex (modified) (1 diff)
- trunk/doc-en/par-new-en.tex (modified) (6 diffs)
- trunk/doc-en/par-nommersolide-en.tex (modified) (3 diffs)
- trunk/doc-en/par-numeroterfacettes-en.tex (modified) (2 diffs)
- trunk/doc-en/par-opacity-en.tex (modified) (1 diff)
- trunk/doc-en/par-parametres-en.tex (modified) (8 diffs)
- trunk/doc-en/par-plan-en.tex (modified) (12 diffs)
- trunk/doc-en/par-point-en.tex (modified) (4 diffs)
- trunk/doc-en/par-pointagesommets-en.tex (modified) (1 diff)
- trunk/doc-en/par-positionnerpointconnu-en.tex (modified) (1 diff)
- trunk/doc-en/par-positionnersolide-en.tex (modified) (2 diffs)
- trunk/doc-en/par-prisme-en.tex (modified) (8 diffs)
- trunk/doc-en/par-projectionangledroit-en.tex (modified) (1 diff)
- trunk/doc-en/par-projectioncercle-en.tex (modified) (2 diffs)
- trunk/doc-en/par-projectioncourbe-en.tex (modified) (6 diffs)
- trunk/doc-en/par-projectiondroite-en.tex (modified) (3 diffs)
- trunk/doc-en/par-projectionligne-en.tex (modified) (1 diff)
- trunk/doc-en/par-projectionpoint-en.tex (modified) (6 diffs)
- trunk/doc-en/par-projectionpolygone-en.tex (modified) (5 diffs)
- trunk/doc-en/par-projectiontexte-en.tex (modified) (11 diffs)
- trunk/doc-en/par-projectionvecteur-en.tex (modified) (2 diffs)
- trunk/doc-en/par-projectionvisibility-en.tex (modified) (1 diff)
- trunk/doc-en/par-projpresentation-en.tex (modified) (1 diff)
- trunk/doc-en/par-ruban-en.tex (modified) (3 diffs)
- trunk/doc-en/par-section-en.tex (modified) (13 diffs)
- trunk/doc-en/par-solidescreux-en.tex (modified) (3 diffs)
- trunk/doc-en/par-solidespredefinis-en.tex (modified) (25 diffs)
- trunk/doc-en/par-surfaces-en.tex (modified) (11 diffs)
- trunk/doc-en/par-surfacesparametrees-en.tex (modified) (6 diffs)
- trunk/doc-en/par-tracerpolygone-en.tex (modified) (1 diff)
- trunk/doc-en/par-transform-en.tex (modified) (7 diffs)
- trunk/doc-en/par-transformpointconnu-en.tex (modified) (1 diff)
- trunk/doc-en/par-tronque-en.tex (modified) (1 diff)
- trunk/doc-en/par-tube-en.tex (modified) (7 diffs)
- trunk/doc-en/par-vecteur-en.tex (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
trunk/doc-en/Makefile
r111 r113 31 31 makeindex -s gglo.ist -t $(basename $<).glg -o $(basename $<).gls \ 32 32 $(basename $<).glo 33 makeindex - t $(basename $<).ilg -o $(basename $<).ind \33 makeindex -s Letter.ist -t $(basename $<).ilg -o $(basename $<).ind \ 34 34 $(basename $<).idx 35 35 bibtex $(basename $<) trunk/doc-en/chapter-1-en.tex
r112 r113 109 109 110 110 From the user's standpoint, most of its functionalities are 111 accessible by way of three \TeX{} macros: \ bs{psSolid}, which can112 manipulate objects in 3 dimensions, \ bs{psSurface}, related to the111 accessible by way of three \TeX{} macros: \Lcs{psSolid}, which can 112 manipulate objects in 3 dimensions, \Lcs{psSurface}, related to the 113 113 first macro and designed to represent surfaces that are defined by 114 an equation of the type $f(x,y) = z$ and \ bs{psProjection} which114 an equation of the type $f(x,y) = z$ and \Lcs{psProjection} which 115 115 allows the user to project two-dimensional graphics/text onto any 116 116 plane face of a 3D solid. … … 141 141 142 142 \begin{itemize} 143 \item The macro \ bs{psProjection} has been completely rewritten. We now need to use an144 object of type \ verb+plan+to define a projection.145 \item The object \ verb+courbe+now uses the argument $r$. To reproduce the previous behaviour143 \item The macro \Lcs{psProjection} has been completely rewritten. We now need to use an 144 object of type \Lkeyword{plan} to define a projection. 145 \item The object \Lkeyword{courbe} now uses the argument $r$. To reproduce the previous behaviour 146 146 we now have to specify $r=0$. 147 \item The option \ verb+resolution+ of the object \verb+courbe+is replaced with the option148 \ verb+ngrid+149 \item Suppression of the argument \ verb+tracelignedeniveau+.147 \item The option \Lkeyword{resolution} of the object \Lkeyword{courbe} is replaced with the option 148 \Lkeyword{ngrid} 149 \item Suppression of the argument \Lkeyword{tracelignedeniveau}. 150 150 \end{itemize} 151 151 … … 153 153 154 154 \begin{itemize} 155 \item The option \ verb+hue+is not a Boolean anymore.155 \item The option \Lkeyword{hue} is not a Boolean anymore. 156 156 \item The scaling in PostScript will from now on follow the workings of \textit{jps code}. 157 157 To be consistent, the commands \verb+smoveto+, trunk/doc-en/chapter-2-en.tex
r112 r113 119 119 \end{center} 120 120 121 The coordinates of the object, in this case the bluish cube, are setup in the axes of coordinates $Oxyz$. The coordinates of the view point ($V$), are setup in the same axes of coordinates, either in spherical coordinates---with the adding option \verb+[rtp2xyz]+, or in Cartesian coordinates---which is the default option.121 The coordinates of the object, in this case the bluish cube, are setup in the axes of coordinates $Oxyz$. The \Index{coordinates} of the \Index{view point} ($V$), are setup in the same axes of coordinates, either in \Index{spherical coordinates}---with the adding option \verb+[rtp2xyz]+, or in Cartesian coordinates---which is the default option. 122 122 123 123 Example: \verb+[viewpoint=50 30 20 rtp2xyz]+ \qquad (here the notation with spherical coordinates) … … 175 175 \end{pspicture} 176 176 177 \section{The definition of the option \texttt{ Decran}}178 The projection screen is placed perpendicular to the direction $OV$---central179 perspective, at a distance $D$ from the view point $V$: We call that distance 180 `Decran', with the default value of \texttt{ [\Lkeyword{Decran}=50]}; this value can177 \section{The definition of the option \texttt{\Index{Decran}}} 178 The \Index{projection screen} is placed perpendicular to the direction $OV$---central 179 perspective, at a distance $D$ from the view point $V$: We call that distance 180 `Decran', with the default value of \texttt{\Lkeyword{Decran}=50}; this value can 181 181 either be positive or negative. 182 182 … … 239 239 240 240 241 If you keep the view point and make the \Lkeyword{Decran} value smaller, then the 241 If you keep the view point and make the \Lkeyword{Decran} value smaller, then the 242 242 image gets smaller. If you make the \Lkeyword{Decran} value larger, then the image gets larger. 243 243 244 Here are some examples, where we keep the same object, the same view point 244 Here are some examples, where we keep the same object, the same view point 245 245 and just vary the \Lkeyword{Decran} value: 246 246 trunk/doc-en/par-affinage-en.tex
r112 r113 1 \section{ Hollowing outa solid's faces}1 \section{\Index{Hollowing out} a solid's faces} 2 2 3 We call \textit{hollowing by the ratio $k$} an operation, which for a given 4 face with the center $G$, executes a dilation on that face with the ratio 3 We call \textit{hollowing by the ratio $k$} an operation, which for a given 4 face with the center $G$, executes a dilation on that face with the ratio 5 5 $k$, then divides the original face with using this new face. 6 6 … … 11 11 \psset{lightsrc=10 0 10,viewpoint=50 -20 30 rtp2xyz,Decran=50} 12 12 \begin{pspicture*}(-4,-4)(4,4) 13 \psframe(-4,-4)(4,4)13 %\psframe(-4,-4)(4,4) 14 14 \psSolid[object=cube, 15 15 fillcolor=red, … … 20 20 \end{center} 21 21 22 The option \ verb+affinage+ allows to hollow a solid's faces either globally or23 individually. This option uses the key \ verb+affinagecoeff+22 The option \Lkeyword{affinage} allows us to hollow a solid's faces either globally or 23 individually. This option uses the key \Lkeyword{affinagecoeff} 24 24 (value $0.8$ by default) which indicates the ratio $k$ used for the 25 25 hollow ($0<k<1$). 26 26 % 27 27 \begin{itemize} 28 \item \ verb+[affinage=all]+hollows all the faces;29 \item \ verb+[affinage=0 1 2 3]+ hollows the faces \texttt{[0,1,2 and 3]};28 \item \texttt{\Lkeyword{affinage}=\Lkeyval{all}} hollows all the faces; 29 \item \texttt{\Lkeyword{affinage}=0 1 2 3} hollows the faces 0, 1, 2 and 3; 30 30 \end{itemize} 31 31 32 When a face is hollowed out, the default behaviour suppresses the resulting central 33 face. However, the option \ verb+affinagerm+allows us to conserve that central face.32 When a face is hollowed out, the default behaviour suppresses the resulting central 33 face. However, the option \Lkeyword{affinagerm} allows us to conserve that central face. 34 34 35 When we conserve the centre face, it is---by default---drawn with the same colour 36 as the original. The option \ verb+fcolor+permits to specify another colour.35 When we conserve the centre face, it is---by default---drawn with the same colour 36 as the original. The option \Lkeyword{fcolor} permits to specify another colour. 37 37 38 38 %\newpage … … 62 62 affinage=all] 63 63 \end{pspicture*} 64 \end{LTXexample} 64 \end{LTXexample} 65 65 66 66 \endinput trunk/doc-en/par-anneaux-en.tex
r112 r113 2 2 \section{Solid rings} 3 3 4 This paragraph discusses the cylindric rings. Within the macro5 \ bs{psSolid}, this object is passed with the option:6 \ verb+[object=anneau]+, that comes with 3 parameters:4 This paragraph discusses the cylindric \Index{rings}. Within the macro 5 \Lcs{psSolid}, this object is passed with the option: 6 \texttt{\Lkeyword{object}=\Lkeyval{anneau}}, that comes with 3 parameters: 7 7 \begin{itemize} 8 \item the inner radius \ verb+[r=1.5]+(value by default);9 \item the outer radius \ verb+[R=4]+(value by default);10 \item the height \ verb+[h=6]+(value by default).8 \item the inner radius \texttt{\Lkeyword{r}=1.5} (value by default); 9 \item the outer radius \texttt{\Lkeyword{R}=4} (value by default); 10 \item the height \texttt{\Lkeyword{h}=6} (value by default). 11 11 \end{itemize} 12 12 13 The argument \ verb+ngrid+defines the number of sections used to make a complete13 The argument \Lkeyword{ngrid} defines the number of sections used to make a complete 14 14 rotation of $360$~degrees. Its default value is $24$. 15 15 … … 22 22 This section is defined in the plane $Oyz$, it is parameterized with the 23 23 triple $(r, R, h)$. The values of the outer radius $R$, inner radius $r$ and the 24 height $h$ are passed in the macro \ bs{psSolid}. By default, one has a ring with24 height $h$ are passed in the macro \Lcs{psSolid}. By default, one has a ring with 25 25 a variable rectangular section, and the definition takes place at the time 26 of the transmission of the values $(r, R, h)$ into the options of \ bs{psSolid}.26 of the transmission of the values $(r, R, h)$ into the options of \Lcs{psSolid}. 27 27 28 28 If the user redefines the \TeX {} macro \verb+\Section+ with some numeric values 29 29 instead of the parameters $r$, $R$ and $h$, then 30 30 the ring won't be variable anymore and it is not necessary to transmit the 31 values $r$, $R$, and $h$ into the options of \ bs{psSolid}.31 values $r$, $R$, and $h$ into the options of \Lcs{psSolid}. 32 32 33 33 \begin{minipage}{0.45\linewidth} … … 92 92 Below is a very simple ring with a fixed triangular section. 93 93 The section is defined by $3$~points $(6, -2)$, $(10, 0)$ 94 and $(6, 2)$ within the option \ verb+section+ of \bs{psSolid}.94 and $(6, 2)$ within the option \Lkeyword{section} of \Lcs{psSolid}. 95 95 96 96 \begin{LTXexample}[width=6cm] trunk/doc-en/par-annoterschema-en.tex
r112 r113 1 1 \section{Adding dimensions to the scenery} 2 2 3 It is very interesting to add dimensions to the scenery. We take the example3 It is very interesting to add \Index{dimensions} to the scenery. We take the example 4 4 of the methane molecule, where we want to insert the distances and angles. 5 5 6 The first step consists of representing the molecule with its bonds and 6 The first step consists of representing the molecule with its bonds and 7 7 characteristic dimensions, and then draw it in a good looking way. 8 8 … … 94 94 \end{center} 95 95 96 The construction of the molecule is detailed in the document 96 The construction of the molecule is detailed in the document 97 97 \texttt{molecules.tex}. To add a dimensioning you only need to find 98 98 the vertices of the tetrahedron: trunk/doc-en/par-axes3D-en.tex
r112 r113 1 \section{The axesin 3d}1 \section{The \Index{axes} in 3d} 2 2 3 3 The command \verb+\axesIIID[options](x1,y1,z1)(x2,y2,z2)+ draws the axes $Ox$, … … 9 9 \begin{itemize} 10 10 \item all colour options, line width as well as all types of arrows. 11 \item \ verb+labelsep=length+ which allows you to position the label in a self defined distance away from the extremity of the arrow of the axis, the default value is \verb+labelsep=5pt+---this is a real distance in three dimensions and not on screen.11 \item \texttt{\Lkeyword{labelsep}=length} which allows you to position the \Index{label} in a self defined distance away from the extremity of the arrow of the axis, the default value is \texttt{\Lkeyword{labelsep}=5pt}---this is a real distance in three dimensions and not on screen. 12 12 \item the choice of the labels on each of the axes with the option: \\ 13 \ verb+axisnames={a,b,c}+, the default values are \verb+axisnames={x,y,z}+.13 \texttt{\Lkeyword{axisnames}={a,b,c}}, the default values are \texttt{\Lkeyword{axisnames}={x,y,z}}. 14 14 \item the potential to specify the style of the labels with the option: \\ 15 \ verb+axisemph={\boldmath\Large\color{red}}+. By default there is no style predefined, which means, if no style is chosen one will get \verb+$x$,$y$,$z$+.16 \item \ verb+showOrigin+ is a Boolean, \texttt{true}---by default. If it is set to \verb+showOrigin=false+the dashed lines aren't drawn to the origin anymore.17 \item \ verb+mathLabel+ is a Boolean, \texttt{true}---by default, in which case the math mode is activated. Set to \verb+mathLabel=false+the labels are set in text mode.15 \texttt{\Lkeyword{axisemph}=}\verb+\boldmath\Large\color{red}+. By default there is no style predefined, which means, if no style is chosen one will get \verb+$x$,$y$,$z$+. 16 \item \Lkeyword{showOrigin} is a Boolean, \texttt{true}---by default. If it is set to \texttt{\Lkeyword{showOrigin}=false} the dashed lines aren't drawn to the origin anymore. 17 \item \Lkeyword{mathLabel} is a Boolean, \texttt{true}---by default, in which case the math mode is activated. Set to \texttt{\Lkeyword{mathLabel}=false} the labels are set in text mode. 18 18 \end{itemize} 19 \encadre{The labelsare placed at the extemities of the axes.}19 \encadre{The \Index{labels} are placed at the extemities of the axes.} 20 20 21 21 \begin{LTXexample}[width=5cm] trunk/doc-en/par-chanfrein-en.tex
r112 r113 1 \section{ Chamferinga solid}1 \section{\Index{Chamfering} a solid} 2 2 3 3 \psset{lightsrc=10 0 10,viewpoint=50 -20 30 rtp2xyz,Decran=50} … … 23 23 \end{LTXexample} 24 24 25 The option \ verb+chanfrein+ allows us to chamfera solid. This option26 uses the key \ verb+chanfreincoeff+(value $0.8$ by default) which indicates the25 The option \Lkeyword{chanfrein} allows us to \Index{chamfer} a solid. This option 26 uses the key \Lkeyword{chanfreincoeff} (value $0.8$ by default) which indicates the 27 27 ratio $k$ with ($0<k<1$). This ratio is the one of a centre dilation with 28 28 the centre in the middle of the chosen face. trunk/doc-en/par-codejps-en.tex
r112 r113 1 \section{The code jps}1 \section{The \Index{jps code}} 2 2 3 3 \textit{jps code} contains all the PostScript code that is used by the library … … 24 24 25 25 In all of the $3$~examples below, the number of points is declared by the global 26 variable \ verb+resolution+.26 variable \Lkeyword{resolution}. 27 27 28 In other words, with the function$F$ named above and a fixed resolution of 36, the \textit{jps code}28 In other words, with the \Index{function} $F$ named above and a fixed resolution of 36, the \textit{jps code} 29 29 \begin{verbatim} 30 30 0 360 {F} CourbeR2+ trunk/doc-en/par-colorierfacettes-en.tex
r112 r113 1 \section{ Colouringsome single faces}1 \section{\Index{Colouring} some single faces} 2 2 3 The key value \texttt{[fcol=}% 4 $i_0$~\verb+(+$c_0$\verb+)+~% 5 $i_1$~\verb+(+$c_1$\verb+)+~% 6 \dots 7 $i_n$~\verb+(+$c_n$\verb+)+~% 8 \texttt{]}, 9 where $i_k$ are integers and $c_k$ the names of the colours, permits to 10 specify a colour for special faces. 11 To the face with the index $i_k$ corresponds the colour $c_k$. The 3 The key value \texttt{\Lkeyword{fcol}=$i_0$~($c_0$) $i_1$~($c_1$) \dots $i_n$~($c_n$)}, 4 where $i_k$ are integers and $c_k$ the names of the colours, permits to 5 specify a \Index{colour} for special \Index{faces}. 6 To the face with the index $i_k$ corresponds the colour $c_k$. The 12 7 integer $n$ must be lower than the maximum of the number of faces of the chosen solid. 13 8 … … 98 93 must be lower than 68! 99 94 100 However users can define their own colours. There are two methods:95 However users can define their own \Index{colours}. There are two methods: 101 96 102 97 \begin{itemize} 103 \item They can use one of the $4$~optional arguments \texttt{ [color1]},104 \texttt{ [color2]}, \texttt{[color3]}, \texttt{[color4]} from105 \ verb+\psSolid+, then transmit to \verb+fcol+a pair of the type98 \item They can use one of the $4$~optional arguments \texttt{color1}, 99 \texttt{color2}, \texttt{color3}, \texttt{color4} from 100 \Lcs{psSolid}, then transmit to \Lkeyword{fcol} a pair of the type 106 101 $i$~\verb+(color1)+, where $i$ is the index of the chosen face. The 107 arguments \texttt{ [color1]}, etc. are used in the same way as the108 arguments from \ texttt{color} and \texttt{incolor}.\hfill \break102 arguments \texttt{color1}, etc. are used in the same way as the 103 arguments from \Lkeyword{color} and \Lkeyword{incolor}.\hfill \break 109 104 A possible command could be the following: 110 105 \begin{verbatim} … … 113 108 \item They define their own colour names with the command 114 109 \verb+\pstVerb+, and then use these names with the argument 115 \ verb+[fcol]+. For example:110 \Lkeyword{fcol}. For example: 116 111 \begin{verbatim} 117 112 \pstVerb{/hetre {0.764 0.6 0.204 setrgbcolor} def … … 176 171 \pstVerb{/iface 0 store}% 177 172 \psSolid[ 178 fcol=48 {iface (Black) 179 iface 1 add (LimeGreen) 180 iface 2 add (Yellow) /iface 173 fcol=48 {iface (Black) 174 iface 1 add (LimeGreen) 175 iface 2 add (Yellow) /iface 181 176 iface 3 add store} repeat, 182 177 r1=4,r0=1, … … 188 183 \end{center} 189 184 190 When the option \ verb+hue+is activated, the faces of the solid are coloured with the nuance of the rainbow colours.185 When the option \Lkeyword{hue} is activated, the faces of the solid are coloured with the nuance of the rainbow colours. 191 186 192 187 \begin{LTXexample}[width=5.9cm] trunk/doc-en/par-commandestrace-en.tex
r112 r113 1 1 \section{Commands for drawing} 2 2 3 The parameter for drawing comes with the key value \verb+action=+within the command4 \ bs{psSolid}.3 The parameter for \Index{drawing} comes with the key value \Lkeyword{action} within the command 4 \Lcs{psSolid}. 5 5 6 6 Four values are possible: 7 7 \begin{itemize} 8 \item \ verb+none+: nothing is drawn.9 \item \verb+draw+: draws the solid as a framework and sets up dashed lines for the hidden edges.10 \item \verb+draw*+: draws the solid with dashed lines for the hidden edges and colours the visible faces.11 \item \verb+draw**+: draws the solid with a painting algorithm, without the12 hidden edges and with colo ration of the visible faces.8 \item \Lkeyval{none}: nothing is drawn. 9 \item \Lkeyval{draw}: draws the solid as a framework and sets up dashed lines for the hidden edges. 10 \item \Lkeyval{draw*}: draws the solid with dashed lines for the hidden edges and colours the visible faces. 11 \item \Lkeyword{draw**}: draws the solid with a painting algorithm, without the 12 hidden edges and with colouration of the visible faces. 13 13 \end{itemize} 14 \encadre{The key values \ texttt{draw} and \texttt{draw*} only make sense for convex solids.}14 \encadre{The key values \Lkeyval{draw} and \Lkeyword{draw*} only make sense for convex solids.} 15 15 16 16 \begin{center} trunk/doc-en/par-couleurs-en.tex
r112 r113 1 1 \section{Colours and the nuances of a colour} 2 2 3 The key value \verb+[fillcolor=name]+allows us to specify the wanted colour for the outer faces of a solid.4 The key value \verb+[incolor=name]+allows us to specify the wanted colour for the inner faces of a solid.3 The key word \texttt{\Lkeyword{fillcolor}=colourname} allows us to specify the wanted colour for the outer faces of a solid. 4 The key word \texttt{\texttt{\Lkeyword{incolor}=colourname}} allows us to specify the wanted colour for the inner faces of a solid. 5 5 6 6 The possible values for \textit{name} are those known to PSTricks (and particularly those of the package \texttt{xcolor}). 7 7 8 8 We can directly use the colour nuances in the color schemes of 9 HSB, RGB or CMYK. In that case we use the key values \ verb+[hue]+,10 \ verb+[inhue]+ or \verb+[inouthue]+for the outer faces, the inner faces, or for all the faces.11 The number of arguments \ verb+hue+determines nuances.12 13 \subsection{Predefined colours by the option [\texttt{dvipsnames}]}14 15 There are $68$~predefined colours, which are identified by9 HSB, RGB or CMYK. In that case we use the key values \Lkeyval{hue}, 10 \Lkeyval{inhue} or \Lkeyval{inouthue} for the outer faces, the inner faces, or for all the faces. 11 The number of arguments \Lkeyval{hue} determines nuances. 12 13 \subsection{Predefined \Index{colours} by the option \texttt{dvipsnames}} 14 15 There are $68$~predefined \Index{colours}, which are identified by 16 16 \texttt{solides.pro}: \texttt{Black}, \texttt{White}, and the 17 17 $66$~colours below. … … 113 113 \egroup 114 114 115 \subsection {Predefined colours by the option [\texttt{svgnames}]}116 117 The following colours are known by PSTricks, when the option [\texttt{svgnames}]is given.118 These ones are not identified by the file \texttt{solides.pro}: we can use them directly with the option \ texttt{[fcol]}.115 \subsection{Predefined \Index{colours} by the option \texttt{svgnames}} 116 117 The following colours are known by PSTricks, when the option \texttt{svgnames} is given. 118 These ones are not identified by the file \texttt{solides.pro}: we can use them directly with the option \Lkeyword{fcol}. 119 119 120 120 \bgroup … … 317 317 \egroup 318 318 319 \subsection{Nuances in the colour scheme of HSB, saturation and maximum brilliance}320 321 There are 2 key values: \ verb+[hue=+$h_0$ $h_1$\verb+]+where319 \subsection{Nuances in the \Index{colour scheme} of \Index{HSB}, \Index{saturation} and maximum \Index{brilliance}} 320 321 There are 2 key values: \texttt{\Lkeyword{hue}=$h_0$ $h_1$} where 322 322 the numbers $h_0$ and $h_1$ with $0\leq h_0 < h_1 \leq 1$ 323 323 respect the limits of the colour scheme of HSB. … … 363 363 364 364 365 \subsection{Nuances in the colour scheme of HSB, saturation and fixed brilliance}366 367 There are 4 key values: \ verb+[hue=+$h_0$ $h_1$ $s$ $b$\verb+]+or365 \subsection{Nuances in the \Index{colour scheme} of \Index{HSB}, \Index{saturation} and fixed \Index{brilliance}} 366 367 There are 4 key values: \texttt{\Lkeyword{hue}=$h_0$ $h_1$ $s$ $b$} or 368 368 the numbers $h_0$ and $h_1$ with $0\leq h_0 < h_1 \leq 1$ 369 369 respect the limits of the colour scheme HSB and $s$ … … 395 395 \end{LTXexample} 396 396 397 \subsection{Nuances in the colour scheme of HSB, gneral case}398 399 There are 7 key values: \ verb+[hue=+$h_0$ $s_0$ $b_0$ $h_1$ $s_1$400 $b_1$ \verb+ (hsb)]+or the numbers $h_i$, $s_i$ and $b_i$ respecting the limits of the parameters of HSB.397 \subsection{Nuances in the \Index{colour scheme} of \Index{HSB}, gneral case} 398 399 There are 7 key values: \texttt{\Lkeyword{hue}=$h_0$ $s_0$ $b_0$ $h_1$ $s_1$ 400 $b_1$ (hsb)} or the numbers $h_i$, $s_i$ and $b_i$ respecting the limits of the parameters of HSB. 401 401 402 402 … … 413 413 \end{LTXexample} 414 414 415 \subsection{Nuances in the colour scheme of RGB}416 417 There are 6 key values: \ verb+[hue=+$r_0$ $g_0$ $b_0$ $r_1$ $g_1$418 $b_1$ \verb+]+or the numbers $r_i$, $g_i$ and $b_i$ respecting the limits of the $3$ parameters of RGB.415 \subsection{Nuances in the \Index{colour scheme} of \Index{RGB}} 416 417 There are 6 key values: \texttt{\Lkeyword{hue}=$r_0$ $g_0$ $b_0$ $r_1$ $g_1$ 418 $b_1$} or the numbers $r_i$, $g_i$ and $b_i$ respecting the limits of the $3$ parameters of RGB. 419 419 420 420 … … 432 432 433 433 434 \subsection{Nuances in the colour scheme of CMYK}435 436 There are 8 key values: \ verb+[hue=+$c_0$ $m_0$ $y_0$ $k_0$ $c_1$ $m_1$437 $y_1$ $k_1$ \verb+]+or the numbers $c_i$, $m_i$, $y_i$ and $k_i$ respecting the limits of the $4$ parameters of CMYK.434 \subsection{Nuances in the \Index{colour scheme} of \Index{CMYK}} 435 436 There are 8 key values: \texttt{\Lkeyword{hue}=$c_0$ $m_0$ $y_0$ $k_0$ $c_1$ $m_1$ 437 $y_1$ $k_1$} or the numbers $c_i$, $m_i$, $y_i$ and $k_i$ respecting the limits of the $4$ parameters of CMYK. 438 438 439 439 … … 453 453 454 454 There are 2 key values 455 \ verb+[hue=(color1) (color2)]+where455 \texttt{\Lkeyword{hue}=(color1) (color2)} where 456 456 \texttt{color1} and \texttt{color2} are the names of colours known by \verb+solides.pro+. 457 457 … … 470 470 471 471 If we like to use some defined colours of \texttt{xcolor}, we use the 472 key values \texttt{color1}, \texttt{color2}, etc. from \ bs{psSolid}.472 key values \texttt{color1}, \texttt{color2}, etc. from \Lcs{psSolid}. 473 473 474 474 \psset{viewpoint=50 50 20 rtp2xyz,Decran=30} … … 493 493 494 494 To deactivate the colour application we use the option 495 \ verb+[deactivatecolor]+.495 \Lkeyword{deactivatecolor}. 496 496 497 497 \endinput trunk/doc-en/par-courbeR3-en.tex
r112 r113 1 \section[ Lines of functions from R in R\textsuperscript{3}]%2 { Lines of functions from $\mathbb{R}$ in $\mathbb{R}^3$} %$1 \section[Curves of functions from R in R\textsuperscript{3}]% 2 {Curves of functions from $\mathbb{R}$ in $\mathbb{R}^3$} %$ 3 3 4 4 %% \section{Fonctions R --> R\textsuperscript{3}} 5 5 6 The line of a defined function calls the object \verb+courbe+ and the option \verb+function+.6 The line of a defined \Index{function} calls the object \Lkeyval{courbe} and the option \Lkeyword{function}. 7 7 We can realize a helix in algebraic notation with the function: 8 8 trunk/doc-en/par-cylindres-cones-en.tex
r112 r113 1 1 \section{Generalization of the notion of a cylinder and a cone} 2 2 3 \subsection{Cylinder or cylindric area}4 5 This paragraph generalizes the notion of a cylinder, or a cylindric 3 \subsection{Cylinder or \Index{cylindric area}} 4 5 This paragraph generalizes the notion of a cylinder, or a cylindric 6 6 area\footnote{This was written by 7 Maxime \textsc{Chupin}, as a result of a question on the list 8 \url{http://melusine.eu.org/cgi-bin/mailman/listinfo/syracuse}}. 9 A \textit{routing} curve has to be defined by a function and the 10 direction of the \textit{cylinder} axis needs to be arranged. In 7 Maxime \textsc{Chupin}, as a result of a question on the list 8 \url{http://melusine.eu.org/cgi-bin/mailman/listinfo/syracuse}}. 9 A \textit{routing} curve has to be defined by a function and the 10 direction of the \textit{cylinder} axis needs to be arranged. In 11 11 the example below the routing curve is sinusoidal, situated in the plane $z=-2$: 12 12 \begin{verbatim} 13 13 \defFunction[algebraic]{G1}(t){t}{2*sin(t)}{-2} 14 14 \end{verbatim} 15 The direction of the cylinder is defined by the components of a vector 16 \ verb+[axe=0 1 1]+. The drawing calls \verb+[object=cylindre]+ which17 in addition to the usual parameters---which is the height \ verb+[h=4]+---18 is about the \textbf{length of the generator} and not of the distance 19 between the two base planes, and needs to define the routing curve 20 \ verb+[function=G1]+ and the interval of the variable $t$ \verb+[range=-3 3]+.15 The direction of the cylinder is defined by the components of a vector 16 \texttt{\Lkeyword{axe}=0 1 1}. The drawing calls \texttt{\Lkeyword{object}=\Lkeyval{cylindre}} which 17 in addition to the usual parameters---which is the height \texttt{\Lkeyword{h}=4}--- 18 is about the \textbf{length of the generator} and not of the distance 19 between the two base planes, and needs to define the routing curve 20 \texttt{\Lkeyword{function}=G1} and the interval of the variable $t$ \texttt{\Lkeyword{range}=-3 3}. 21 21 22 22 \begin{verbatim} … … 73 73 \end{center} 74 74 75 In the following example, before drawing the horizontal planes, we calculate the 75 In the following example, before drawing the horizontal planes, we calculate the 76 76 distance between these two planes. 77 77 … … 181 181 \end{LTXexample} 182 182 183 \subsection{Cone or conic area}184 This paragraph generalizes the notion of a cone, or a conic 183 \subsection{Cone or \Index{conic area}} 184 This paragraph generalizes the notion of a cone, or a conic 185 185 area\footnote{This was written by 186 Maxime \textsc{Chupin}, as the result of a question on the list 187 \url{http://melusine.eu.org/cgi-bin/mailman/listinfo/syracuse}}. 188 A \textit{routing} curve needs to be defined by a function which 189 defines the base of the cone, and the vertex of the \textit{cone} 190 which is by default \ verb+[origine=0 0 0]+. The parts above and191 below the cone are symmetric concerning the vertice. In the example 186 Maxime \textsc{Chupin}, as the result of a question on the list 187 \url{http://melusine.eu.org/cgi-bin/mailman/listinfo/syracuse}}. 188 A \textit{routing} curve needs to be defined by a function which 189 defines the base of the cone, and the vertex of the \textit{cone} 190 which is by default \texttt{\Lkeyword{origine}=0 0 0}. The parts above and 191 below the cone are symmetric concerning the vertice. In the example 192 192 below, the routing curve is a parabolic arc, situated in the plane $z=-2$. 193 193 … … 268 268 \end{LTXexample} 269 269 270 \encadre{For the cones as well, the routing curve can be any curve and need not necessarily 271 be a plane horizontal curve, as the following example, written by Maxime 270 \encadre{For the cones as well, the routing curve can be any curve and need not necessarily 271 be a plane horizontal curve, as the following example, written by Maxime 272 272 \textsc{Chupin}, will show.} 273 273 trunk/doc-en/par-datfile-en.tex
r112 r113 36 36 37 37 38 \subsection{\texttt{ .dat} files (specific to \texttt{pst-solides3d})}38 \subsection{\texttt{\Index{.dat}} files (specific to \texttt{pst-solides3d})} 39 39 40 40 In \texttt{pst-solides3d}, the data structure used for a solid has 4 fields. … … 45 45 \subsubsection{Writing \texttt{.dat} files} 46 46 47 One uses the action \ verb+writesolid+ within \bs{psSolid}, and one48 uses the option \ verb+file+to specify the name of the file.47 One uses the action \Lkeyword{writesolid} within \Lcs{psSolid}, and one 48 uses the option \Lkeyword{file} to specify the name of the file. 49 49 50 50 For example, let's look at the code below: … … 72 72 \subsubsection{Reading \texttt{.dat} files} 73 73 74 We use the object \ verb+datfile+ of \bs{psSolid}, with the argument75 \ verb+file+to specify the name.74 We use the object \Lkeyword{datfile} of \Lcs{psSolid}, with the argument 75 \Lkeyword{file} to specify the name. 76 76 Now the code 77 77 \begin{verbatim} 78 78 \psSolid[object=datfile, file=montore] 79 79 \end{verbatim} 80 will allow to use the object---now saved in the \texttt{.dat} files generated---80 will allow us to use the object---now saved in the \texttt{.dat} files generated--- 81 81 as described in the previous paragraph. 82 82 … … 90 90 the vertices and the faces. 91 91 92 \subsubsection{Writing \texttt{ .obj} files}92 \subsubsection{Writing \texttt{\Index{.obj}} files} 93 93 94 One uses the action \ verb+writeobj+ in \bs{psSolid}, and one uses95 the option \ verb+file+to specify the name of the file.94 One uses the action \Lkeyword{writeobj} in \Lcs{psSolid}, and one uses 95 the option \Lkeyword{file} to specify the name of the file. 96 96 97 97 For example, the code below: … … 106 106 \subsubsection{Reading \texttt{.obj} files} 107 107 108 One uses the option \ verb+objfile+ of \bs{psSolid}, with the argument109 \ verb+file+to specify the name of the file.108 One uses the option \Lkeyword{objfile} of \Lcs{psSolid}, with the argument 109 \Lkeyword{file} to specify the name of the file. 110 110 Now the following code 111 111 \begin{verbatim} … … 135 135 vertices and the faces. 136 136 137 \subsubsection{Writing \texttt{ .off} files}137 \subsubsection{Writing \texttt{\Index{.off}} files} 138 138 139 We use the action \ verb+writeobj+ in \bs{psSolid}, and we use the option140 \ verb+file+to specify the name of the file.139 We use the action \Lkeyword{writeobj} in \Lcs{psSolid}, and we use the option 140 \Lkeyword{file} to specify the name of the file. 141 141 142 142 For example the code below: … … 151 151 \subsubsection{Reading.off files} 152 152 153 We use the option \ verb+offfile+ of \bs{psSolid}, with the argument154 \ verb+file+to specify the name of the file.153 We use the option \Lkeyword{offfile} of \Lcs{psSolid}, with the argument 154 \Lkeyword{file} to specify the name of the file. 155 155 Now the following code 156 156 \begin{verbatim} trunk/doc-en/par-definirfonction-en.tex
r112 r113 1 1 \section{Defining a function} 2 2 3 It is possible to define functionsusable in a PostScript environment.3 It is possible to define \Index{functions} usable in a PostScript environment. 4 4 5 5 The domain can be $\mathbb{R}$, $\mathbb{R}^2$ trunk/doc-en/par-definirplanquelconque-en.tex
r112 r113 1 \section{Defining a projection plane}2 3 The planeof projection is defined with the option4 \texttt{ [plan=plantype]} which expects an argument \textit{type of1 \section{Defining a \Index{projection plane}} 2 3 The \Index{plane} of projection is defined with the option 4 \texttt{\Lkeyword{plan}=plantype} which expects an argument \textit{type of 5 5 plane}. The creation of such an argument invariably happens 6 6 through the command \verb+\psSolid[object=plan]+ (see the relevant … … 13 13 To define a plane of projection, we assume that the drawing to be 14 14 projected resides on the plane $Oxy$, and the user has to specify 15 the images of the origin $O$ and the basis $\overrightarrow{\imath}$, 15 the images of the origin $O$ and the basis $\overrightarrow{\imath}$, 16 16 $\overrightarrow{\jmath}$, and $\overrightarrow{k}$. 17 17 If they wish to abbreviate the syntax, users are required at most … … 51 51 There are four ways to define a normal to a plane, two of which 52 52 have an option to rotate the coordinate system of the plane around 53 that normal: \ texttt{|normal=...]}53 that normal: \Lkeyword{normal} 54 54 55 55 \subsubsection{Method 1: giving the components of the normal vector} 56 56 57 57 58 In this case \texttt{ [normal=nx ny nz]}, the argument consists of58 In this case \texttt{\Lkeyword{normal}=nx ny nz}, the argument consists of 59 59 3 values: the components of the normal vector. For example 60 \texttt{ [normal=0 0 1]} for the plane $Oxy$.60 \texttt{\Lkeyword{normal}=0 0 1} for the plane $Oxy$. 61 61 62 62 \newpage … … 326 326 of rotation} 327 327 328 In this case \texttt{ [normal=nx ny nz A]}, the argument takes four328 In this case \texttt{\Lkeyword{normal}=nx ny nz A}, the argument takes four 329 329 values: the components of the normal vector and the angle of 330 330 rotation (in degrees) around that axis. … … 429 429 and \textit{k}} 430 430 431 In this case \texttt{ [normal=ix iy iz kx ky kz]}, the argument431 In this case \texttt{\Lkeyword{normal}=ix iy iz kx ky kz}, the argument 432 432 takes six values: the components of the images of 433 433 $\overrightarrow{i}$ and $\overrightarrow{k}$, with: … … 533 533 \textit{i}, \textit{k} and an angle of rotation} 534 534 535 In this case \texttt{ [normal=ix iy iz kx ky kz phi]}, the argument535 In this case \texttt{\Lkeyword{normal}=ix iy iz kx ky kz phi}, the argument 536 536 takes seven values: the components of the images of 537 537 $\overrightarrow{i}$, $\overrightarrow{k}$ and the angle of trunk/doc-en/par-definitionmaillage-en.tex
r112 r113 1 1 \section{Definition of grating} 2 2 3 The user can specify the gratingof the solid with the option4 \Lkeyword{ngrid} within the command \ Cadre{\Lcs{psSolid}}.3 The user can specify the \Index{grating} of the solid with the option 4 \Lkeyword{ngrid} within the command \Lcs{psSolid}. 5 5 6 6 For the objects … … 8 8 \Lkeyval{prisme}, 9 9 \Lkeyval{prismecreux}, 10 the syntax is \Lkeyword{ngrid}=$n_1$ where $n_1$ represents the number of vertical gridlines.10 the syntax is \Lkeyword{ngrid}=$n_1$ where $n_1$ represents the number of vertical \Index{gridlines}. 11 11 12 12 For the objects … … 18 18 \Lkeyval{troncconecreux}, 19 19 %%\verb+tore+, 20 the syntax is \ Lkeyword{ngrid}=$n_1$~$n_2$where $n_1$ is an integer greater or equal20 the syntax is \texttt{\Lkeyword{ngrid}=$n_1$~$n_2$} where $n_1$ is an integer greater or equal 21 21 to 1 ($2$ for \Lkeyval{tore}) representing the number of the vertical gridlines, and $n_2$ is an integer 22 22 representing the number of divisions on the circle. 23 23 24 24 For the object 25 \ verb+sphere+,26 the syntax is \texttt{ [ngrid=}$n_1$~$n_2$\texttt{]} where $n_1$ is an integer, representing the number of divisions on the vertical axis, and25 \Lkeyval{sphere}, 26 the syntax is \texttt{\Lkeyword{ngrid}=$n_1$~$n_2$} where $n_1$ is an integer, representing the number of divisions on the vertical axis, and 27 27 $n_2$ is an integer representing the number of divisions on the circle 28 28 horizontally. 29 29 30 30 For the object 31 \ verb+tore+,32 the syntax is \texttt{ [ngrid=}$n_1$~$n_2$\texttt{]} where $n_1$ and $n_2$31 \Lkeyval{tore}, 32 the syntax is \texttt{\Lkeyword{ngrid}=$n_1$~$n_2$} where $n_1$ and $n_2$ 33 33 are integers. 34 34 &hellip
