Show 33 quoted lines
> On Thu, Sep 25, 2008 at 06:52:22PM +0200, Jakub Narebski wrote:
> >
> > I think that making gitweb use something like Gitweb::Template, where
> > action appearance is governed by templates, be it something like
> > git-for-each-ref --format or StGit *.tmpl files, or XSLT / XSL,
> > could be a good idea. But I think _that_ would require almost writing
> > from scratch, certainly making it long-term gitweb fork, perhaps even
> > with different name (and not residing inside git.git repository).
> >
> > We can discuss this idea here in this subthread. For example: do
> > create Gitweb::Template like HTML::Template or use Template Toolkit;
> > which parts put in template and which in "gitweb" driver, etc.
>
> Actually, my implementation works quite differently - the idea of the
> templates is that you just specify data from which files to show and
> whether to take them right away or tabulate them in some way - so it is
> something very abstract, and agnostic to _presentation_ layer, which is
> still provided by gitweb. An example of made-up template configuration
> file would look something like:
>
> [action "summary"]
> sections = metadata overview README shortlog forks
>
> [section "overview"]
> type = csv
> row = Project Title,(info.txt:title)
> row = Project Authors,(info.txt:authors)
> row = Bussiness Impact,(info.txt:bizimpact)
> row = Base Equation,[formula.png]
>
> [section "README"]
> type = html
> content = (README.html)
Gaaaah. I think this is heavy abuse of _configuration_ mini-language
git uses (extended ini-like syntax); it can be done, but it is IMVHO
on par of writing A.I. (Artificial Intelligence) in COBOL:
http://ars.userfriendly.org/cartoons/?id=20001018
Jakub Narebski <jnareb@gmail.com>