![]() ![]() Template::Toolkit for the template rendering. I hacked an adapter that exposes the HTML::Template API but uses Plugins, but a number of others which have specialized templates of theirĪ modular template system in ikiwiki is unlikely, as template objectsĪre part of the API, notably the pagetemplate hook. ![]() Things that use templates - not just the pagetemplate and template Of special features of different backends. Need to write an IkiWiki template interface that didn't care what theīackend was, and yet is somehow still flexible enough to take advantage Than making the revision-control backend modular, I guess. Think it would be a lot of work to implement, though perhaps no more work System I like better, such as Text::Template or Text::NeatTemplate. It would enable me to use some other template The template system modular, with a choice of which backend to use - I However, I alsoĪgree that HTML::Template has its own problems too. ![]() Others have said above, it's overkill for my needs. I don't wish HTML::Template to be replaced by Template::Toolkit - as Some of this can currently be accomplished with separate templates for each use case and a manual call to the right template in the !inline directive, but this is limited, cumbersome, and makes it difficult to reuse bits of formatting by trapping all of that information in multiple template files. If I could use the slot-based filling and the conditional logic from Template::Toolkit, we could build much more flexible inline and archivepage templates that would look different depending on where in the wiki we use them. I agree that being able to replace the template toolkit would be a great piece of modularity, and one I would use. (Quoting it properly to use from the shell command-line is I used this PERL regexp to convert my own templates: sgi The ability to replace the template engine would be within the spirit of ikiwiki's extensibility. A markup syntax that doesn't confuse editors (such as Template::Toolkit's "") may promote template customization. The editor tries to render the template markup rather than display it verbatim, and large parts of the template become invisible. HTML::Template's HTML-like markup prevents me from editing templates in KompoZer or other WYSIWYG HTML editors. I'd have to agree that Template::Toolkit is overkill and personally I'm not a fan, but it is very popular (there is even a book) and the new version (3) is alleged to be much more nimble than current version. HTML::Template can keep things simple, though. But I think it's somehow overkill for a wiki. I'd prefer not having to touch Perl though. I would be glad to volunteer time to make this switch happen, such as rewrite To fill, I am sure you can see the appeal of that approach. Now look at the approach with slots: MainTemplateĪs soon as you think about more structure pages with various slots It'll be broken in potentially subtle ways. This involves four pages, and if you mistype "footer" on page B, Templating is done with includes: Page A Page B Illustrate, using the HTML::Template syntax for simplicity. With Zope Page Templates and never wanted to miss it again. One major reason for TT is its use of slots, a concept I first encountered I would love to see ikiwiki use the Template Its entirely optional use of capital letters? - Joeyįinally, the software seems unmaintained: the mailing list and searchableĪre broken and the author has not replied to my query in months. Maybe it's just me, I also find HTML::Template cumbersome to use, due in part Note that is no longer true, and I didn't have to do such an intrusive More than one of them contain the tag, which is unnecessary. ![]() If you browse the templates provided in the tarball, you'll notice that HTML::Template is an okay templating kit, but it lacks a lot of powerfulįeatures and thus makes it rather hard to give an ikiwiki site a consistent ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |