Difference between revisions of "Command/fillinfield"
< Command
Jump to navigation
Jump to search
DecebalICT (talk | contribs) |
(Format code with <texcode>) |
||
Line 18: | Line 18: | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | |||
== Example == | == Example == | ||
− | + | <texcode> | |
− | \usemodule[fields, abr-pseudocaps] | + | \usemodule[fields,abr-pseudocaps] |
\setupinteraction[state=start] | \setupinteraction[state=start] | ||
\starttext | \starttext | ||
− | + | A few years back, \TEX\ could only produce \fillinfield [dvi]{\DVI} | |
− | A few years back, \TEX\ could only produce | + | output, but nowadays, thanks to \fillinfield {Han The Thanh}, |
− | + | we can also directly produce \fillinfield [pdf] {\PDF}! Nice eh? | |
− | \fillinfield [dvi]{\DVI} output, | + | Actually, while the first field module was prototyped in \ACROBAT, |
− | + | the current implementation was debugged in \fillinfield [pdfTeX] {\PDFTEX}. | |
− | but nowadays, thanks to \fillinfield {Han The Thanh}, | + | Field support in \fillinfield [ConTeXt] {\CONTEXT} is rather advanced |
− | + | and complete and all kind of fields are supported. One can hook | |
− | we can also directly produce \fillinfield [pdf] {\PDF}! | + | in appearances, and validation \fillinfield [JavaScripts] {\JAVASCRIPT}'s. |
− | + | Fields can be cloned and copied, where the latter saves some space. | |
− | Nice eh? Actually, while the first field module was prototyped | + | By using \fillinfield {objects} when suited, this module saves space anyway. |
− | |||
− | in \ACROBAT, the current implementation was debugged in | ||
− | |||
− | \fillinfield [pdfTeX] {\PDFTEX}. Field support in \fillinfield | ||
− | |||
− | [ConTeXt] {\CONTEXT} is rather advanced and complete and all | ||
− | |||
− | kind of fields are supported. One can hook in appearances, and | ||
− | |||
− | validation \fillinfield [JavaScripts] {\JAVASCRIPT} | ||
− | |||
− | can be cloned and copied, where the latter saves some space. By | ||
− | |||
− | using \fillinfield {objects} when suited, this module saves | ||
− | |||
− | space anyway. | ||
− | |||
\stoptext | \stoptext | ||
+ | </texcode> | ||
== See also == | == See also == |
Revision as of 17:56, 5 April 2011
\fillinfield
Syntax
\fillinfield[...]{...} | |
[...] | text |
{...} | text |
Example
\usemodule[fields,abr-pseudocaps] \setupinteraction[state=start] \starttext A few years back, \TEX\ could only produce \fillinfield [dvi]{\DVI} output, but nowadays, thanks to \fillinfield {Han The Thanh}, we can also directly produce \fillinfield [pdf] {\PDF}! Nice eh? Actually, while the first field module was prototyped in \ACROBAT, the current implementation was debugged in \fillinfield [pdfTeX] {\PDFTEX}. Field support in \fillinfield [ConTeXt] {\CONTEXT} is rather advanced and complete and all kind of fields are supported. One can hook in appearances, and validation \fillinfield [JavaScripts] {\JAVASCRIPT}'s. Fields can be cloned and copied, where the latter saves some space. By using \fillinfield {objects} when suited, this module saves space anyway. \stoptext