Mercurial > p > roundup > code
comparison doc/templating.txt @ 956:846f2a79807d
tweak
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Tue, 20 Aug 2002 04:41:56 +0000 |
| parents | 84281f7f2900 |
| children | e8aa903cbaa5 |
comparison
equal
deleted
inserted
replaced
| 955:84281f7f2900 | 956:846f2a79807d |
|---|---|
| 1 ========================== | 1 ========================== |
| 2 HTML Templating Mechanisms | 2 HTML Templating Mechanisms |
| 3 ========================== | 3 ========================== |
| 4 | 4 |
| 5 :Version: $Revision: 1.1 $ | 5 :Version: $Revision: 1.3 $ |
| 6 | 6 |
| 7 Current Situation and Issues | 7 Current Situation and Issues |
| 8 ============================ | 8 ============================ |
| 9 | 9 |
| 10 Syntax | 10 Syntax |
| 26 don't parse as we'd hope. It would be almost impossible to modify the sgmllib | 26 don't parse as we'd hope. It would be almost impossible to modify the sgmllib |
| 27 parser to parse the above "correctly", so a wholly new parser would be | 27 parser to parse the above "correctly", so a wholly new parser would be |
| 28 required. That is a large undertaking, and doesn't address another couple of | 28 required. That is a large undertaking, and doesn't address another couple of |
| 29 issues that have arisen: | 29 issues that have arisen: |
| 30 | 30 |
| 31 1. the template syntax is neither HTML-editor friendly, not a well-formed | 31 1. the template syntax is not well-formed, and therefore is a pain to parse |
| 32 syntax for other tools to work with, and | 32 and doesn't play well with other tools, and |
| 33 2. user requirements generally have to be anticipated and accounted for in | 33 2. user requirements generally have to be anticipated and accounted for in |
| 34 templating functions (like ``plain()`` and ``checklist()`` above), and | 34 templating functions (like ``plain()`` and ``checklist()`` above), and |
| 35 we are therefore artificially restrictive. | 35 we are therefore artificially restrictive. |
| 36 | 36 |
| 37 Arguments for switching templating systems: | 37 Arguments for switching templating systems: |
| 38 | 38 |
| 39 *Pros* | 39 *Pros* |
| 40 | 40 |
| 41 - we can be editor-friendly | |
| 42 - more flexibility in templating control and content | 41 - more flexibility in templating control and content |
| 42 - we can be well-formed | |
| 43 | 43 |
| 44 *Cons* | 44 *Cons* |
| 45 | 45 |
| 46 - installed user base (though they'd have to edit their templates with the | 46 - installed user base (though they'd have to edit their templates with the |
| 47 next release anyway) | 47 next release anyway) |