HTML::Template

thanks for the reply.

i think i started down the right path (and resolved my initial confusion)after
sending out this message, but am i able to pass the "gui" template a filename
to then be parsed as part of the tmpl_include (which, then in turn, will be
parsed)?

ideally, i'd like to reference one gui template for all the pages and simply
supply H-T a name of that page-specific .tmpl to parse into the area "x".

i was thinking i'd have to parse the entire x.tmpl into a string and supply
that as a tmpl_var when i parse through the gui.tmpl.

the separate two calls don't necessarily bother me at this point, but didn't
understand if H-T was able to do such a thing.

thanks.



--- Karen Cravens <silver@...> wrote:
> On 5 Sep 2002 at 11:28, csajl wrote:
> 
> > the tmpl_include function works but only as far as vertical layout blocks
> are
> > concerned (or am i missing something?).
> 
> You're missing something.  But it's more of an HTML issue than an H-T issue.
>  
> > i searched the mailing list archives as well as google and haven't found a
> > solution.  any pointers would be greatly appreciated.
> 
> You want a table, most likely.  That's the layout I use at the Phoenyx.  In 
> fact, if you look at <URL: http://www.phoenyx.net/index.tmpl >, you can see 
> the raw template file for the index.html main page (static, regenerated 
> nightly).  You'll have to look at the subtemplates, since I actually do a
> sort of 
> reverse template, but the basic structure of the HTML looks something like 
> this:
> 
> === Sample pseudocode ===
> <TABLE width=100%>
> <TR><TD width=(either an explicit pixel width or a percentage, depending on 
> what you're putting in the "sidebar") valign="top">
> 
> (Your sidebar stuff)
> 
> </td></tr><TR><TD valign="top">
> 
> (Your main content stuff... the "x", or a TMPL_INCLUDE in your case)
> 
> </td></tr>
> </table>
> === end pseudocode ===
> 
> You can get clever with your table layout and cause the main content to 
> appear above the sidebar for Lynx users (two rows, two columns, of which 
> the first cell is 1 pixel high, and the second column is a rowspan of two,
> and 
> the sidebar lives in the first column, *second* row), but you have to be
> careful 
> because Netscape and IE don't always agree on how that should be 
> displayed.  I think mine still does that, so don't let it confuse you.
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Html-template-users mailing list
> Html-template-users@...
> https://lists.sourceforge.net/lists/listinfo/html-template-users




__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com

On 5 Sep 2002 at 13:58, csajl wrote:

> i was thinking i'd have to parse the entire x.tmpl into a string and supply
> that as a tmpl_var when i parse through the gui.tmpl.
> the separate two calls don't necessarily bother me at this point, but didn't
> understand if H-T was able to do such a thing.

I'm not quite sure where you're going with this, but couldn't you go the other 
way 'round, the way I do, and TMPL_INCLUDE the "skin" parts into the 
individual pages?  I actually have four different prefab sections, with three 
different "openings" for custom stuff:

Prefab header
  Menu
Prefab separator (which currently opens the table tags)
  Main content
Prefab separator (which closes that cell and opens another)
  Sidebar content
Prefab footer (which closes out the table, and adds all the various bottom-of-
the-page meeble)

This setup lets me change the look of the site quite a bit without changing 
anything but the prefab files.  Here's a piece of an older site-look:

<URL: http://www.phoenyx.net/gamers/2002/index.html >

compared to the new one on the main page.  (The older stuff is MhonArc-
generated, and I haven't gotten around to reconfiguring the mhonarc.rc file 
and regenerating the vast quantities of archives we've got.  If anyone wants to 
earn my undying gratitude, convince Earl Hood to switch MhonArc to H::T.)

On Thu, 5 Sep 2002, csajl wrote:

> i was thinking i'd have to parse the entire x.tmpl into a string and
> supply that as a tmpl_var when i parse through the gui.tmpl.

use a filter.  something like this:

<tmpl_include "%%include_file%%">

and in the perl filter:

s/<tmpl_include "%%include_file%%">/<tmpl_include "$include_file">/g;

although i'm not quite sure if this works as I think it should.  ie, 
does H::T pass a <tmpl_include> to a filter and then do the including or 
does it just do the including?

-- 
Life is the urge to ecstasy.

Quoting Philip S Tellis <philip.tellis@...>:

> On Thu, 5 Sep 2002, csajl wrote:
> 
> > i was thinking i'd have to parse the entire x.tmpl into a string and
> > supply that as a tmpl_var when i parse through the gui.tmpl.
> 
> use a filter.  something like this:
> 
> <tmpl_include "%%include_file%%">
> 
> and in the perl filter:
> 
> s/<tmpl_include "%%include_file%%">/<tmpl_include "$include_file">/g;
> 
> although i'm not quite sure if this works as I think it should.  ie, 
> does H::T pass a <tmpl_include> to a filter and then do the including or 
> does it just do the including?

This would break if you are using caching, since H::T doesn't consider filters 
when doing its cache lookups.  Sam said he was planning to add support for  
generating your own cache keys which would solve this problem, but I guess he's 
been quite busy lately.

However, with caching turned off, your method should work.  From what I 
remember of the code, filters are applied first, then the template is parsed. 
When an include file is found, it is sent through the filter first, then parsed 
and included, etc...  So if you have many includes in your template, the filter 
will be called many times.

Cees

thanks much.
this is exactly what i was trying to do.


--- Philip S Tellis <philip.tellis@...> wrote:
> On Thu, 5 Sep 2002, csajl wrote:
> 
> > i was thinking i'd have to parse the entire x.tmpl into a string and
> > supply that as a tmpl_var when i parse through the gui.tmpl.
> 
> use a filter.  something like this:
> 
> <tmpl_include "%%include_file%%">
> 
> and in the perl filter:
> 
> s/<tmpl_include "%%include_file%%">/<tmpl_include "$include_file">/g;
>

__________________________________________________
Yahoo! - We Remember
9-11: A tribute to the more than 3,000 lives lost
http://dir.remember.yahoo.com/tribute