Re: [viewvc-dev] Combining browse and query page

ViewVC's templates aren't really designed to be combined like this.  The EZT
templating system has only the ability to present data provided to it
(more-or-less statically) by ViewVC itself.  We've documented the variables
available to the templates for each ViewVC view (see
http://viewvc.tigris.org/nonav/source/browse/*checkout*/viewvc/trunk/
docs/template-authoring-guide.html).  As you explore that document, note
that it's not the case that a given variable fails to appear for a
particular view because the default templates don't use it -- variables fail
to appear for particular views because the ViewVC Python code fails to make
those variables available to the templates at all.

For various reasons, I'd like to change some of this.  But while doing so
can give ViewVC admins the flexibility to do some fun stuff, it might also
hand them just enough rope to hang themselves due with performance problems.


Kinson Liu wrote:
> Hi Developers,
> 
> I am trying to combine both of the browse and query pages into one page,
> ie. placing the query form on top of the browse table.  Can you please
> advise the following?
> 1. Whether I should include the query_form.ezt into directory.ezt, or
> the other way around, or create a new .ezt including both query_form.ezt
> or directory.ezt?
> 2. For the answer to 1, please advise what code changes needed to be
> made?  I tried including query_form.ezt into directory.ezt but to no
> avail.  Obvioulsy variables or functions for query_form.ezt were missing
> in that case.
> 3. Any other better solutions?
> 
> Thanks,
> 
> Kinson
> 
> -- 
> Kinson Liu


-- 
C. Michael Pilato <[email protected]>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHZvW+okEGqRcG/W4RAr+XAJ9trlmgqDsjp0XMuDqn+it0wf1ciQCgrUAP
/qYLjqvj1YZ/lSDl0yqPLQs=
=dng8
-----END PGP SIGNATURE-----