On 08/24/2007 10:41 AM, Matt Rosin wrote:
> 2b. This reduces templates to a list of assets (snippets) called by > name interspersed with HTML tags and TT directives. Text snippets > would reside in a database and could be edited in a CMS, at least like > the utility of 1a/b above. Image pathnames or a single DIV's HTML > could also all be stored in the db. The template would just pull the > snippets out with a simple $c method like loc in the above I18N > modules. A standard facility for editing these things (a module and TT > templates) would also be useful. > I'm working on such an app right now, except that snippets are kept in SVN instead of a database. The idea is to allow .tt files to be edited via web UI, storing metadata in each .tt file in a special reserved hash. Still deciding on which JS UI toolkit to use. Leaning toward TinyMCE. Hardest part (right now) is figuring out how to provide real-time re-use of other .tt files (via PROCESS) within the .tt file being edited. So a user could (e.g.) pick a snippet from a dropdown list and insert it, and then see the rendered text immediately. But on save, only the [% PROCESS foo %] gets written. Oh, and images. :) -- Peter Karman . [EMAIL PROTECTED] . http://peknet.com/ _______________________________________________ List: Catalyst@lists.rawmode.org Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.rawmode.org/ Dev site: http://dev.catalyst.perl.org/