Next: Introduction, Previous: (dir), Up: (dir) [Contents][Index]
This is the ten Reference Manual, version 0.0.1, generated automatically by Declt version 3.0 "Montgomery Scott" on Mon Apr 19 17:59:59 2021 GMT+0.
| • Introduction | What ten is all about | |
| • Systems | The systems documentation | |
| • Files | The files documentation | |
| • Packages | The packages documentation | |
| • Definitions | The symbols documentation | |
| • Indexes | Concepts, functions, variables and data types |
Yet another template system for Common Lisp.
TEN is a fork of ECO template system by Fernando Borretti.
Like ECO, TEN compiles templates to Lisp code, but has some differences:
My reasons for writing yet another template system for Common Lisp is to combine the simplicity and usability of ECO (the whole Lisp language at your disposal for writing the templates), with features available in more complex template systems like Djula that makes things easier for web development (inheritance, dot syntax, etc.).
A TEN template looks like this:
{% template ex1 () (user enabled &key items) %}
<html>
<head>
</head>
<body>
{{ user.name | string-capitalize }}
{% if enabled %}
Enabled
{% else %}
Disabled
{% end %}
{% when items %}
<ul>
{% loop for item in items do %}
<li>{{ item }}</li>
{% end %}
</ul>
{% end %}
{% when (not items) %}
There are no items
{% end %}
</body>
</html>
{% end %}
There are two types of tags:
{{ <var> }}, becomes <var>, and {{ <fn> &rest args }}, that becomes (fn arg1 arg2 .. argn).{% <expr> %} body {% end %}, becomes (<expr> body).Control tags control which parts of the tamplate are rendered; their return value is ignored.
The value returned by output tags are interpolated into the template. The function called can be any Lisp function, or another template (because templates are compiled to functions).
For example:
{{ user }} => user{{ name user }} => (name user){% when (name user) %} ... {% end %} => (when (name user) ...)The if tag is a special case: it supports using an else tag to separate the true and
false branches. For example:
{% if posts %}
<h1>Recent Posts</h1>
... loop over posts ...
{% else %}
No recent posts.
{% end %}
Also, more advanced control expressions are possible, like let, case, cond, etc.
Templates are defined with the following syntax:
{% template name (&rest options) (&rest args) %}
... body ...
{% end %}
Template options are:
:extends : The template to extend from.:dot-syntax: If T, templates are compiled with dot syntax enabled. Dot syntax is implemented via the Lisp library access. Default is T.:package: The package in which to compile and export the template. By default, templates are compiled and exported in TEN-TEMPLATES package.:export: When T, export the generated template function. Otherwise, the template is not exported. Default is T.:escape-html: Whether to escape html in output tags. Default is T.:output-whitespace. Default is T. When NIL, expressions that just spit whitespace are discarded.For manually compiling templates, use ten:compile-template function.
But more useful is to include them in the ASDF system definition of your project.
First, add :ten as ASDF system definition dependency:
:defsystem-depends-on (:ten)
Then, use :ten-template in to include the template files:
(:ten-template "filename")
The default file extension is "ten", but another can be specified via the :file-extension option; and the template package can be specified with the :package option. Look at ten.examples ASDF system for an example.
You can also compile all the templates in some directory using this ASDF recipe:
:perform (asdf:compile-op :after (o c)
(dolist (template (uiop:directory-files (asdf:system-relative-pathname :my-app "templates/*.ten")))
(uiop:symbol-call :ten 'compile-template template)))
Templates are compiled into functions and exported in the indicated package. The default package is ten-templates, but that can be changed from either the ASDF system definition, the ten:compile-template parameters, or the {% template %} options.
When developing your project it is useful to be able to compile templates in an interactive way.
If you are using Emacs + SLIME, load ten.el file.
Then use M-X ten-compile-template when on the template buffer to compile templates. Note that you may want to have :package option specified in the template so that it gets compiled into the correct package.
For debugging, you can inspect the expanded template using ten:expand-template function. In Emacs, go to template buffer an do M-x ten-expand-template.
If you enable ten minor mode, template compilation gets conveniently bound to C-c C-c, and template expansion to C-c RET. Best is to automatically enable the minor mode for template files adding something like (add-hook 'web-mode-hook 'ten-mode) to your .emacs initialization file.
To make a template inherit from anohter, use the :extends option in template definition.
Templates are organized in sections. sections are the parts of the templates that are inherited.
Use {{super}} inside a section to render the parent section.
TEN leverages CLOS for implementing template inheritance. Templates are compiled to classes and generic functions render-template and render-section.
Have a look at some examples of template inheritance.
To include other templates, just use the output tag with the name of the included template. Remember that templates are compiled to functions; just call those functions from the template to include them.
Have a look at an example.
When dot syntax is enabled (it is, by default), it is possible to conveniently access objects with dot syntax in templates:
{{ object.key1.key2 }}
that gets translated by access library to:
(access:accesses obj 'key1 'key2)
Have a look at an example.
TEN implements some convenient syntax for filters.
{{ value | func1 arg1 .. argN| func2 arg1 .. argN| .. | funcN arg1 .. argN}}
Filters are just normal functions that get applied to the value.
Filters are translated to functions application like this:
(funcN (.. (func2 (func1 value arg1 .. argN) arg1 .. argN))) arg1 .. argN)
In general, filter functions are expected to receive the value to be filtered as first parameter.
But, for several Lisp functions that's not the case. In those cases, it is possible to use _ to indicate where the filter function should receive the value.
For example, string-trim receives the string to trim as second value, so, to apply it as filter we do:
{{str | string-trim '(#\%) _}}
Filters syntax is completly optional, you can disregard it and just apply functions instead:
{{ string-trim '(#\%) (string-capitalize str) }}
Have a look at some examples of filters.
Load and have a look at the examples.
(require :ten.examples)
ten-templates, if the package specified doesn't :use ten or ten-template packages, then you may run into problems trying to compile your templates. That may be because the template and section macros are not found in the specified package. In that case, make sure to prefix your template and section declarations with ten:, like:{% ten:template my-template (:package my-package) %}
{% ten:section my-section %}
{% end %}
{% end %}
cond and case, require that you turn :output-whitespace to NIL. Otherwise, template compilation puts write-string expressions right in the middle of the case and cond bodies. Have a look at this template.MIT
Next: Files, Previous: Introduction, Up: Top [Contents][Index]
The main system appears first, followed by any subsystem dependency.
| • The ten system |
Mariano Montone <marianomontone@gmail.com>
MIT
Template System for Common Lisp
# TEN
[](https://travis-ci.org/mmontone/ten)
[](http://quickdocs.org/ten/)
[](./LICENSE)
Yet another template system for Common Lisp.
TEN is a fork of [ECO template system](https://github.com/eudoxia0/eco) by Fernando Borretti.
Like ECO, TEN compiles templates to Lisp code, but has some differences:
- Two types of tags only. Control and output.
- Support for templates inheritance.
- Dot syntax for accessing template data.
- Convenient syntax for applying filters.
- Configurable syntax delimiters (planned, not done yet).
My reasons for writing yet another template system for Common Lisp is to combine the simplicity and usability of ECO (the whole Lisp language at your disposal for writing the templates), with features available in more complex template systems like [Djula](https://mmontone.github.io/djula/) that makes things easier for web development (inheritance, dot syntax, etc.).
## Usage
A TEN template looks like this:
“‘jinja
{% template ex1 () (user enabled &key items) %}
<html>
<head>
</head>
<body>
{{ user.name | string-capitalize }}
{% if enabled %}
Enabled
{% else %}
Disabled
{% end %}
{% when items %}
<ul>
{% loop for item in items do %}
<li>{{ item }}</li>
{% end %}
</ul>
{% end %}
{% when (not items) %}
There are no items
{% end %}
</body>
</html>
{% end %}
“‘
There are two types of tags:
- *Output tags*: ‘{{ <var> }}‘, becomes ‘<var>‘, and ‘{{ <fn> &rest args }}‘, that becomes ‘(fn arg1 arg2 .. argn)‘.
- *Control tags*: ‘{% <expr> %} body {% end %}‘, becomes ‘(<expr> body)‘.
Control tags control which parts of the tamplate are rendered; their return value is ignored.
The value returned by output tags are interpolated into the template. The function called can be any
Lisp function, or another template (because templates are compiled to functions).
For example:
* ‘{{ user }}‘ => ‘user‘
* ‘{{ name user }}‘ => ‘(name user)‘
* ‘{% when (name user) %} ... {% end %}‘ => ‘(when (name user) ...)‘
The ‘if‘ tag is a special case: it supports using an ‘else‘ tag to separate the true and
false branches. For example:
“‘lisp
{% if posts %}
<h1>Recent Posts</h1>
... loop over posts ...
{% else %}
No recent posts.
{% end %}
“‘
Also, more [advanced control expressions](https://github.com/mmontone/ten/blob/master/examples/control.html) are possible, like ‘let‘, ‘case‘, ‘cond‘, etc.
## Template definition
Templates are defined with the following syntax:
“‘
{% template name (&rest options) (&rest args) %}
... body ...
{% end %}
“‘
Template options are:
- ‘:extends‘ : The template to extend from.
- ‘:dot-syntax‘: If T, templates are compiled with dot syntax enabled. Dot syntax is implemented via the Lisp library ‘access‘. Default is T.
- ‘:package‘: The package in which to compile and export the template. By default, templates are compiled and exported in ‘TEN-TEMPLATES‘ package.
- ‘:export‘: When T, export the generated template function. Otherwise, the template is not exported. Default is T.
- ‘:escape-html‘: Whether to escape html in output tags. Default is T.
- ‘:output-whitespace‘. Default is T. When NIL, expressions that just spit whitespace are discarded.
## Template compilation
For manually compiling templates, use ‘ten:compile-template‘ function.
But more useful is to include them in the ASDF system definition of your project.
First, add ‘:ten‘ as ASDF system definition dependency:
‘:defsystem-depends-on (:ten)‘
Then, use ‘:ten-template‘ in to include the template files:
“‘lisp
(:ten-template "filename")
“‘
The default file extension is "ten", but another can be specified via the ‘:file-extension‘ option; and the template package can be specified with the ‘:package‘ option. Look at [ten.examples ASDF system](https://github.com/mmontone/ten/blob/master/ten.examples.asd) for an example.
You can also compile all the templates in some directory using this ASDF recipe:
“‘lisp
:perform (asdf:compile-op :after (o c)
(dolist (template (uiop:directory-files (asdf:system-relative-pathname :my-app "templates/*.ten")))
(uiop:symbol-call :ten ’compile-template template)))
“‘
Templates are compiled into functions and exported in the indicated package. The default package is ‘ten-templates‘, but that can be changed from either the ASDF system definition, the ‘ten:compile-template‘ parameters, or the ‘{% template %}‘ options.
When developing your project it is useful to be able to compile templates in an interactive way.
If you are using Emacs + SLIME, load ‘ten.el‘ file.
Then use ‘M-X ten-compile-template‘ when on the template buffer to compile templates. Note that you may want to have ‘:package‘ option specified in the template so that it gets compiled into the correct package.
For debugging, you can inspect the expanded template using ‘ten:expand-template‘ function. In Emacs, go to template buffer an do ‘M-x ten-expand-template‘.
If you enable ‘ten‘ minor mode, template compilation gets conveniently bound to ‘C-c C-c‘, and template expansion to ‘C-c RET‘. Best is to automatically enable the minor mode for template files adding something like ‘(add-hook ’web-mode-hook ’ten-mode)‘ to your ‘.emacs‘ initialization file.
## Inheritance
To make a template inherit from anohter, use the ‘:extends‘ option in template definition.
Templates are organized in ‘sections‘. ‘sections‘ are the parts of the templates that are inherited.
Use ‘{{super}}‘ inside a ‘section‘ to render the parent ‘section‘.
TEN leverages CLOS for implementing template inheritance. Templates are compiled to classes and generic functions ‘render-template‘ and ‘render-section‘.
Have a look at some [examples of template inheritance](https://github.com/mmontone/ten/blob/master/examples/inheritance.html).
## Includes
To include other templates, just use the output tag with the name of the included template. Remember that templates are compiled to functions; just call those functions from the template to include them.
Have a look at [an example](https://github.com/mmontone/ten/blob/master/examples/include.html).
## Dot syntax
When dot syntax is enabled (it is, by default), it is possible to conveniently access objects with dot syntax in templates:
‘{{ object.key1.key2 }}‘
that gets translated by [access](https://github.com/AccelerationNet/access) library to:
‘(access:accesses obj ’key1 ’key2)‘
Have a look at [an example](https://github.com/mmontone/ten/blob/master/examples/dot-syntax.html).
## Filters
TEN implements some convenient syntax for filters.
‘{{ value | func1 arg1 .. argN| func2 arg1 .. argN| .. | funcN arg1 .. argN}}‘
Filters are just normal functions that get applied to the value.
Filters are translated to functions application like this:
‘(funcN (.. (func2 (func1 value arg1 .. argN) arg1 .. argN))) arg1 .. argN)‘
In general, filter functions are expected to receive the value to be filtered as first parameter.
But, for several Lisp functions that’s not the case. In those cases, it is possible to use ‘_‘ to indicate where the filter function should receive the value.
For example, ‘string-trim‘ receives the string to trim as second value, so, to apply it as filter we do:
‘{{str | string-trim ’(#\%) _}}‘
Filters syntax is completly optional, you can disregard it and just apply functions instead:
‘{{ string-trim ’(#\%) (string-capitalize str) }}‘
Have a look at some [examples of filters](https://github.com/mmontone/ten/tree/master/examples/filters.html).
## Examples
Load and have a look at the [examples](https://github.com/mmontone/ten/tree/master/examples).
“‘lisp
(require :ten.examples)
“‘
## Troubleshooting
1) When specifying a template package other than ‘ten-templates‘, if the package specified doesn’t ‘:use‘ ‘ten‘ or ‘ten-template‘ packages, then you may run into problems trying to compile your templates. That may be because the ‘template‘ and ‘section‘ macros are not found in the specified package. In that case, make sure to prefix your ‘template‘ and ‘section‘ declarations with ‘ten:‘, like:
“‘django
{% ten:template my-template (:package my-package) %}
{% ten:section my-section %}
{% end %}
{% end %}
“‘
2) Some "complex" expressions, like ‘cond‘ and ‘case‘, require that you turn ‘:output-whitespace‘ to ‘NIL‘. Otherwise, template compilation puts ‘write-string‘ expressions right in the middle of the ‘case‘ and ‘cond‘ bodies. Have a look at [this template](https://github.com/mmontone/ten/blob/master/examples/control.html).
## License
MIT
0.0.1
ten.asd (file)
Files are sorted by type and then listed depth-first from the systems components trees.
| • Lisp files |
Next: The ten/package․lisp file, Previous: Lisp files, Up: Lisp files [Contents][Index]
ten.asd
ten (system)
Next: The ten/parser․lisp file, Previous: The ten․asd file, Up: Lisp files [Contents][Index]
ten (system)
package.lisp
Next: The ten/template․lisp file, Previous: The ten/package․lisp file, Up: Lisp files [Contents][Index]
package.lisp (file)
ten (system)
parser.lisp
Next: The ten/compiler․lisp file, Previous: The ten/parser․lisp file, Up: Lisp files [Contents][Index]
parser.lisp (file)
ten (system)
template.lisp
Next: The ten/asdf․lisp file, Previous: The ten/template․lisp file, Up: Lisp files [Contents][Index]
template.lisp (file)
ten (system)
compiler.lisp
Next: The ten/i18n․lisp file, Previous: The ten/compiler․lisp file, Up: Lisp files [Contents][Index]
compiler.lisp (file)
ten (system)
asdf.lisp
Next: The ten/ten․lisp file, Previous: The ten/asdf․lisp file, Up: Lisp files [Contents][Index]
asdf.lisp (file)
ten (system)
i18n.lisp
_ (function)
Previous: The ten/i18n․lisp file, Up: Lisp files [Contents][Index]
i18n.lisp (file)
ten (system)
ten.lisp
Next: Definitions, Previous: Files, Up: Top [Contents][Index]
Packages are listed by definition order.
| • The ten/template package | ||
| • The ten/parser package | ||
| • The ten/compiler package | ||
| • The ten package | ||
| • The ten-templates package |
Next: The ten/parser package, Previous: Packages, Up: Packages [Contents][Index]
package.lisp (file)
common-lisp
Next: The ten/compiler package, Previous: The ten/template package, Up: Packages [Contents][Index]
package.lisp (file)
Next: The ten package, Previous: The ten/parser package, Up: Packages [Contents][Index]
package.lisp (file)
Next: The ten-templates package, Previous: The ten/compiler package, Up: Packages [Contents][Index]
package.lisp (file)
common-lisp
Previous: The ten package, Up: Packages [Contents][Index]
package.lisp (file)
Definitions are sorted by export status, category, package, and then by lexicographic order.
| • Exported definitions | ||
| • Internal definitions |
Next: Internal definitions, Previous: Definitions, Up: Definitions [Contents][Index]
| • Exported special variables | ||
| • Exported symbol macros | ||
| • Exported macros | ||
| • Exported functions | ||
| • Exported generic functions | ||
| • Exported classes |
Next: Exported symbol macros, Previous: Exported definitions, Up: Exported definitions [Contents][Index]
template.lisp (file)
template.lisp (file)
template.lisp (file)
template.lisp (file)
template.lisp (file)
The package where template expressions are evaluated and the template function is exported
compiler.lisp (file)
Next: Exported macros, Previous: Exported special variables, Up: Exported definitions [Contents][Index]
template.lisp (file)
(progn (call-next-method) "")
Next: Exported functions, Previous: Exported symbol macros, Up: Exported definitions [Contents][Index]
template.lisp (file)
template.lisp (file)
template.lisp (file)
template.lisp (file)
The main template creation macro.
Arguments:
- EXTENDS: the name of the template to extend from.
- PACKAGE: the package within which the compiled template is to be defined.
- EXPORT: when T, the generated template function is exported.
- ESCAPE-HTML: whether to escape HTML or not. Default is controlled by *ESCAPE-HTML*, which is true by default.
- OUTPUT-WHITESPACE: whether to output whitespaces or not. Default is controlled by *OUTPUT-WHITESPACE*, which is true by default.
- CREATE-STRING-WRITING-FUNCTION: controls whether a function that writes the template to a string should be created. Default is T.
- CREATE-STREAM-WRITING-FUNCTION: controls whether a function that writes the template to *TEMPLATE-OUTPUT* stream should be created. Default is false.
IMPORTANT: some of this macro arguments are processed by CALL-WITH-TEMPLATE-HEADER-OPTIONS, not here. That’s why we declare some of them as ignored.
template.lisp (file)
Next: Exported generic functions, Previous: Exported macros, Up: Exported definitions [Contents][Index]
i18n.lisp (file)
compiler.lisp (file)
Compile a template. If a pathname is given, compiles the file content. Otherwise, compiles the given string.
Escape a string.
template.lisp (file)
Expand a template to Lisp code. Useful for debugging.
parser.lisp (file)
template.lisp (file)
template.lisp (file)
template.lisp (file)
Next: Exported classes, Previous: Exported functions, Up: Exported definitions [Contents][Index]
automatically generated reader method
parser.lisp (file)
automatically generated reader method
parser.lisp (file)
automatically generated reader method
parser.lisp (file)
Previous: Exported generic functions, Up: Exported definitions [Contents][Index]
parser.lisp (file)
<tag> (class)
:code
code (generic function)
:body
body (generic function)
parser.lisp (file)
<tag> (class)
parser.lisp (file)
<tag> (class)
:code
code (generic function)
template.lisp (file)
standard-object (class)
Previous: Exported definitions, Up: Definitions [Contents][Index]
| • Internal special variables | ||
| • Internal functions | ||
| • Internal generic functions | ||
| • Internal classes |
Next: Internal functions, Previous: Internal definitions, Up: Internal definitions [Contents][Index]
template.lisp (file)
compiler.lisp (file)
i18n.lisp (file)
i18n.lisp (file)
Export the templates by default
template.lisp (file)
template.lisp (file)
compiler.lisp (file)
compiler.lisp (file)
The translation backend.
i18n.lisp (file)
i18n.lisp (file)
i18n.lisp (file)
parser.lisp (file)
parser.lisp (file)
parser.lisp (file)
parser.lisp (file)
parser.lisp (file)
Next: Internal generic functions, Previous: Internal special variables, Up: Internal definitions [Contents][Index]
compiler.lisp (file)
compiler.lisp (file)
compiler.lisp (file)
parser.lisp (file)
compiler.lisp (file)
compiler.lisp (file)
compiler.lisp (file)
i18n.lisp (file)
template.lisp (file)
parser.lisp (file)
compiler.lisp (file)
compiler.lisp (file)
template.lisp (file)
template.lisp (file)
parser.lisp (file)
i18n.lisp (file)
parser.lisp (file)
parser.lisp (file)
Next: Internal classes, Previous: Internal functions, Up: Internal definitions [Contents][Index]
i18n.lisp (file)
compiler.lisp (file)
compiler.lisp (file)
compiler.lisp (file)
compiler.lisp (file)
compiler.lisp (file)
template.lisp (file)
Previous: Internal generic functions, Up: Internal definitions [Contents][Index]
parser.lisp (file)
<tag> (class)
parser.lisp (file)
<output-tag> (class)
parser.lisp (file)
standard-object (class)
parser.lisp (file)
<output-tag> (class)
Previous: Definitions, Up: Top [Contents][Index]
| • Concept index | ||
| • Function index | ||
| • Variable index | ||
| • Data type index |
Next: Function index, Previous: Indexes, Up: Indexes [Contents][Index]
| Jump to: | F L T |
|---|
| Jump to: | F L T |
|---|
Next: Variable index, Previous: Concept index, Up: Indexes [Contents][Index]
| Jump to: | _
A B C D E F G L M P R S T V W |
|---|
| Jump to: | _
A B C D E F G L M P R S T V W |
|---|
Next: Data type index, Previous: Function index, Up: Indexes [Contents][Index]
| Jump to: | *
+
B C S |
|---|
| Jump to: | *
+
B C S |
|---|
Previous: Variable index, Up: Indexes [Contents][Index]
| Jump to: | <
C P S T |
|---|
| Jump to: | <
C P S T |
|---|