Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Synergy at OSCON 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • It would be great if Bricolage had a TT burner, with all the TT modules and plugins and my own codebase it would mean that I could build a web app in any of openinteract, openframe or bricolage according to the needs of the project.

    Great news

    I would also love to see some kind of common api or framework between the different templating systems available - in particular something that I would want for my autodocumentation / code generation projects would be some kind of reflection API so that I could run a template through any of TT, H::T or Mason and see what the template would require, its includes, etc - that would provide the ability to provide some sort of lint tool for templates as well as automated documentation and code generation.

    I am already looking at code generation from UML and Database structures (one for design on objects, the other for creating query phrasebooks, get/set methods, etc) and being able to create code stubs that populate a given template would be very useful indeed and greatly reduce variable name copy/paste errors.

    --

    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
    • And the next version of OpenInteract (the 2.x series) will be able to use HTML::Template (or Text::Template, or...) as well. All the TT functionality isn't there (particularly the plugin), but it seems the HTML::Template folks prefer it like that anyway...
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.