html-template-users Mailing List for HTML::Template (Page 105)
Brought to you by:
samtregar
You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(42) |
Jul
(80) |
Aug
(77) |
Sep
(97) |
Oct
(65) |
Nov
(80) |
Dec
(39) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(63) |
Feb
(47) |
Mar
(45) |
Apr
(63) |
May
(67) |
Jun
(51) |
Jul
(78) |
Aug
(37) |
Sep
(45) |
Oct
(59) |
Nov
(50) |
Dec
(70) |
2004 |
Jan
(23) |
Feb
(90) |
Mar
(37) |
Apr
(53) |
May
(111) |
Jun
(71) |
Jul
(35) |
Aug
(58) |
Sep
(35) |
Oct
(35) |
Nov
(35) |
Dec
(20) |
2005 |
Jan
(51) |
Feb
(19) |
Mar
(20) |
Apr
(8) |
May
(26) |
Jun
(14) |
Jul
(49) |
Aug
(24) |
Sep
(20) |
Oct
(49) |
Nov
(17) |
Dec
(53) |
2006 |
Jan
(12) |
Feb
(26) |
Mar
(45) |
Apr
(19) |
May
(19) |
Jun
(13) |
Jul
(11) |
Aug
(9) |
Sep
(10) |
Oct
(16) |
Nov
(17) |
Dec
(13) |
2007 |
Jan
(9) |
Feb
(12) |
Mar
(28) |
Apr
(33) |
May
(12) |
Jun
(12) |
Jul
(19) |
Aug
(4) |
Sep
(4) |
Oct
(5) |
Nov
(5) |
Dec
(13) |
2008 |
Jan
(6) |
Feb
(7) |
Mar
(14) |
Apr
(16) |
May
(3) |
Jun
(1) |
Jul
(12) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(9) |
2009 |
Jan
(9) |
Feb
|
Mar
(10) |
Apr
(1) |
May
|
Jun
(6) |
Jul
(5) |
Aug
(3) |
Sep
(7) |
Oct
(1) |
Nov
(15) |
Dec
(1) |
2010 |
Jan
|
Feb
|
Mar
|
Apr
(9) |
May
|
Jun
|
Jul
(5) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
(3) |
Mar
|
Apr
(28) |
May
|
Jun
|
Jul
(3) |
Aug
(4) |
Sep
(3) |
Oct
|
Nov
(8) |
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2016 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
From: Kenny S. <ke...@jo...> - 2002-07-03 06:54:18
|
> why not do this: > > my $t = new HTML::Template(filehandle => *DATA); > > then, you just put your template in the source file itself, either after > __DATA__ or after __END__ But... that goes against everything that HTML::Template stands for, imo. The separation of program from display.. the ability to change the look without editing the source, etc. Kenny Smith JournalScape.com |
From: Sam T. <sa...@tr...> - 2002-07-03 06:38:28
|
On Wed, 3 Jul 2002, Philip S Tellis wrote: > On Tue, 2 Jul 2002, Sam Tregar wrote: > > > filter => { > > sub => sub { $language_filter->(shift, > > scalar $query->param("language")) }, > > format => 'scalar', > > }, > > heh. try doing that in java. Perl is a good deal closer to reimplementing Lisp with a reasonable syntax than Java is. The ability to dynamicly create closures is definitely a benefit of that! Hopefully Perl 6 will get us even closer. Can you tell I've been reading way too much Paul Graham lately? -sam |
From: Philip S T. <phi...@gm...> - 2002-07-03 05:34:48
|
On Tue, 2 Jul 2002, Roy Rubin wrote: > > my $t = new HTML::Template(filehandle => *DATA); > > > > then, you just put your template in the source file itself, either after > > __DATA__ or after __END__ > > > > Can you provide a more detailed example well, I've never tried it myself, but it would look something like this: #!/usr/bin/perl -w use strict; use HTML::Template; my $t = new HTML::Template(filehandle => *DATA); # do normal template processing here __DATA__ <html> <head><title><tmpl_var title></title></head> <body> <h1><tmpl_var title></h1> <p> Hello <tmpl_var name>. </p> </body> </html> |
From: Roy R. <ro...@ir...> - 2002-07-03 05:13:08
|
> On Tue, 2 Jul 2002, Douglas Kirkland wrote: > > > Ok I am curious, Can I do the following. This way I can have the > > template name that is assocated with the script and at the same level > > as the script directory. All the while not having to modify the > > following line. I would like it to be a cut and paste into each > > script. > > > > > > my $t = HTML::Template->new(filename => $0.'.tmpl', > > path => '../templates'); > > > > why not do this: > > my $t = new HTML::Template(filehandle => *DATA); > > then, you just put your template in the source file itself, either after > __DATA__ or after __END__ > > > Can you provide a more detailed example Thanks. Roy |
From: Philip S T. <phi...@gm...> - 2002-07-03 05:05:13
|
On Tue, 2 Jul 2002, Sam Tregar wrote: > filter => { > sub => sub { $language_filter->(shift, > scalar $query->param("language")) }, > format => 'scalar', > }, heh. try doing that in java. |
From: Philip S T. <phi...@gm...> - 2002-07-03 04:47:25
|
On Tue, 2 Jul 2002, Douglas Kirkland wrote: > Ok I am curious, Can I do the following. This way I can have the > template name that is assocated with the script and at the same level > as the script directory. All the while not having to modify the > following line. I would like it to be a cut and paste into each > script. > > > my $t = HTML::Template->new(filename => $0.'.tmpl', > path => '../templates'); > why not do this: my $t = new HTML::Template(filehandle => *DATA); then, you just put your template in the source file itself, either after __DATA__ or after __END__ |
From: Cory T. <ct...@on...> - 2002-07-02 22:03:06
|
> -----Original Message----- > From: htm...@li... > [mailto:htm...@li...]On Behalf Of > Keith Jackson > Sent: Tuesday, July 02, 2002 5:24 PM > To: Will > Cc: HTML Template > Subject: Re: [htmltmpl] placing .tmpl files in a subdirectory? > Just to add my method : > > What we do is to place them in a directory at the same level as docroot > and cgi-bin in a directory called templates. We store them outside of 'cgi-bin' and in fact, outside of the server_root altogether. We use a five-level deep structure of directories to store our templates : user's role templates, component (single-cgiapp), application (group-of-cgiapp), overall system templates, overall component templates. The bottom three levels ( role, component, application ) could contain a very flexible interface for a single application. The same application could exist solely using the top two levels ( system, component .) We also load all of our templates via an Abstract Factory pattern ( implemented as 'load_tmpl( )' in CGI::Application. ) This way the arguments passed to 'HTML::Template->new( )' are consistent and we can generate a new hierarchy from the configuration of the environment when a template is requested. Our structure is this way because we are deploying many copies of the same component with different interfaces (HTML::Templates,) and thus, we need a way to put custom HTML::Template files where needed but always be able to reuse the templates that were not changed. If a group of cgi::applications all use a template with the same name / functionality (a function of cgi::app design I guess) then a single template at application (group of cgi::app) can update multiple cgi::app interfaces (assuming the cgi::app in question did not further override the template.) Overriding 'load_tmpl( )' for cgi::application and using that to create html::template objects helped our design remain flexible MANY times. Even if I was not using CGI::application I would still strongly suggest an Adapter function of some type to ensure that updating your method for creating html::templates never becomes a chore. Just our method, Cory > > During development, we have a secondary docroot set up point to that > directory so the designers can see the templates in a browswer. When we > go to production, the secondary docroot is dropped. > > We also duplicate the directory structure under the templates directory > to match as closely as we can the directory structuce of the cgi-bin > directory to make maintenance easier. This doesn't always work out, but > for the most part it does. > > We also place the name of the template in a comment at the top of each > template so the template can be identified from a browser. Otherwise we > would have to trace back through perl code to know which template is > being used. Again, it makes maintenace much easier. > > Hope this helps. > > Keith Jackson > > On Tue, 2002-07-02 at 15:39, Will wrote: > > Greets Folks, > > > > Does anyone here place their .tmpl files in a special > > directory assigned just for templates, like maybe: > > > > /cgi-bin/templates > > > > I was thinking of doing this for organizational > > purposes, but I wasn't sure of what problems I might > > run into, or what path I would have to use in the CGI > > programs, etc... > > > > Any advice appreciated. > > > > Thanks, > > > > Will |
From: Roy R. <ro...@ir...> - 2002-07-02 21:47:20
|
> Greets Folks, > > Does anyone here place their .tmpl files in a special > directory assigned just for templates, like maybe: > > /cgi-bin/templates > > I was thinking of doing this for organizational > purposes, but I wasn't sure of what problems I might > run into, or what path I would have to use in the CGI > programs, etc... > > Any advice appreciated. > > Thanks, > > Will We usually separate the template names and location to a configuration file, which the designers can update on their own. It look something like this: TemplateConfig.pm ================== package TemplateConfig; use vars '$AUTOLOAD'; sub new { my $class = shift; bless { _base_template_path => '/path/to/files/templates', _add_rec => 'emp_add.html', _delete_rec => 'emp_delete.html', _edit_rec => 'emp_edit.html' }, $class; } sub AUTOLOAD { my ($self) = @_; $AUTOLOAD =~ /.*::get(_\w+)/; exists $self->{$1}; return $self->{$1}; } 1; In the cgi script, the package is instantiated and the file names are used in the following format: use TemplateConfig; $config = TemplateConfig->new(); $filename = $config->get_base_template_path . $config->get_add_rec Roy ro...@ir... |
From: Keith J. <kja...@ey...> - 2002-07-02 21:23:48
|
What we do is to place them in a directory at the same level as docroot and cgi-bin in a directory called templates. During development, we have a secondary docroot set up point to that directory so the designers can see the templates in a browswer. When we go to production, the secondary docroot is dropped. We also duplicate the directory structure under the templates directory to match as closely as we can the directory structuce of the cgi-bin directory to make maintenance easier. This doesn't always work out, but for the most part it does. We also place the name of the template in a comment at the top of each template so the template can be identified from a browser. Otherwise we would have to trace back through perl code to know which template is being used. Again, it makes maintenace much easier. Hope this helps. Keith Jackson On Tue, 2002-07-02 at 15:39, Will wrote: > Greets Folks, > > Does anyone here place their .tmpl files in a special > directory assigned just for templates, like maybe: > > /cgi-bin/templates > > I was thinking of doing this for organizational > purposes, but I wasn't sure of what problems I might > run into, or what path I would have to use in the CGI > programs, etc... > > Any advice appreciated. > > Thanks, > > Will > > > > __________________________________________________ > Do You Yahoo!? > Sign up for SBC Yahoo! Dial - First Month Free > http://sbc.yahoo.com > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Html-template-users mailing list > Htm...@li... > https://lists.sourceforge.net/lists/listinfo/html-template-users > |
From: Roger B. W. <ro...@fi...> - 2002-07-02 21:21:34
|
On Tue, Jul 02, 2002 at 02:10:58PM -0700, Douglas Kirkland wrote: >Ok I am curious, Can I do the following. This way I can have the template >name that is assocated with the script and at the same level as the script >directory. All the while not having to modify the following line. I would >like it to be a cut and paste into each script. Yes, though what I do is: my $fn=$0; $fn =~ /\/([^\/]*?)\.cgi$/; $fn="$1.tmpl"; &set_env; my $tmpl=HTML::Template->new(filename => $fn, die_on_bad_params => 0); where &set_env sets the HTML_TEMPLATE_ROOT. The directory structure is: cgi-bin/ a.cgi b.cgi etc. templates/ a.tmpl b.tmpl etc. Roger |
From: Douglas K. <dlk...@rh...> - 2002-07-02 21:11:54
|
On Tuesday 02 July 2002 10:51 am, Sam Tregar wrote: > On Tue, 2 Jul 2002, Will wrote: > > Does anyone here place their .tmpl files in a special > > directory assigned just for templates, like maybe: > > > > /cgi-bin/templates > > > > I was thinking of doing this for organizational > > purposes, but I wasn't sure of what problems I might > > run into, or what path I would have to use in the CGI > > programs, etc... > > Yes. If you do that, just use the path option to specify the path to the > templates: > > my $t = HTML::Template->new(filename => 'foo.tmpl', > path => 'templates'); > Ok I am curious, Can I do the following. This way I can have the template name that is assocated with the script and at the same level as the script directory. All the while not having to modify the following line. I would like it to be a cut and paste into each script. my $t = HTML::Template->new(filename => $0.'.tmpl', path => '../templates'); -- Douglas Kirkland Technical Support Department Rhyton Corporation te...@rh... http://www.rhyton.com |
From: Kenny S. <ke...@jo...> - 2002-07-02 19:57:28
|
Hi Will, Yes, I put all of my templates in a subdirectory. You can set $ENV{'HTML_TEMPLATE_ROOT'} to the name of the subdirectory, and then just do $template = HTML::Template->new( filename => 'filename.tmpl' ) ; and H::T will look for $ENV{'HTML_TEMPLATE_ROOT'}/filename.tmpl Hope this helps, Kenny Smith JournalScape.com > Greets Folks, > > Does anyone here place their .tmpl files in a special > directory assigned just for templates, like maybe: > > /cgi-bin/templates > > I was thinking of doing this for organizational > purposes, but I wasn't sure of what problems I might > run into, or what path I would have to use in the CGI > programs, etc... > > Any advice appreciated. > > Thanks, > > Will |
From: Roy R. <ro...@ir...> - 2002-07-02 19:57:12
|
> > Greets Folks, > > Does anyone here place their .tmpl files in a special > directory assigned just for templates, like maybe: > > /cgi-bin/templates > > I was thinking of doing this for organizational > purposes, but I wasn't sure of what problems I might > run into, or what path I would have to use in the CGI > programs, etc... > > Any advice appreciated. > > Thanks, > > Will > I usually place the files under the HTML main directory under a templates folder. There are no problems at all, and the files could be placed anywhere. Roy ro...@ir... |
From: Sam T. <sa...@tr...> - 2002-07-02 19:51:49
|
On Tue, 2 Jul 2002, Will wrote: > Does anyone here place their .tmpl files in a special > directory assigned just for templates, like maybe: > > /cgi-bin/templates > > I was thinking of doing this for organizational > purposes, but I wasn't sure of what problems I might > run into, or what path I would have to use in the CGI > programs, etc... Yes. If you do that, just use the path option to specify the path to the templates: my $t = HTML::Template->new(filename => 'foo.tmpl', path => 'templates'); -sam |
From: Will <sel...@ya...> - 2002-07-02 19:39:57
|
Greets Folks, Does anyone here place their .tmpl files in a special directory assigned just for templates, like maybe: /cgi-bin/templates I was thinking of doing this for organizational purposes, but I wasn't sure of what problems I might run into, or what path I would have to use in the CGI programs, etc... Any advice appreciated. Thanks, Will __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com |
From: Philip S T. <phi...@gm...> - 2002-07-02 05:51:53
|
On Mon, 1 Jul 2002, Will wrote: > Supposing a script using both CGI.pm and > HTML::Template... would the following be a functional > assignment (such that the WHATEVER could be used in > the .tmpl file)? > > $template->param(WHATEVER=>$CGI->param("blah")); yes, this is correct, but not what is normally done. you'd be better off doing an associate: my $template = new HTML::Template( filename => 'template.tmpl', associate => $CGI ); which will do the above for all cgi variables. Use your method only if you want just one or two cgi vars sent to the template. |
From: Will <sel...@ya...> - 2002-07-02 05:33:17
|
Greets Folks, One more question on CGI.pm please... Supposing a script using both CGI.pm and HTML::Template... would the following be a functional assignment (such that the WHATEVER could be used in the .tmpl file)? $template->param(WHATEVER=>$CGI->param("blah")); My system is down, or I would try it myself, but please let me know. Thanks, will __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com |
From: Philip S T. <phi...@gm...> - 2002-07-01 07:04:27
|
On Mon, 1 Jul 2002, Philip S Tellis wrote: > Well, version 0.0.9 is out, which fixes the case bug, and also adds some > features. Ok, some confusion, since this announcement was primarily for the html-tmpl-java list. It's the new version of html-tmpl-java that's out. Philip |
From: Philip S T. <phi...@gm...> - 2002-07-01 06:13:15
|
Well, version 0.0.9 is out, which fixes the case bug, and also adds some features. Changelog: 1 Jul 2002 ver 0.0.9 - supports reading from file handle - no longer adds newline character to items passed in arrayref - added escape=quote parameter for tmpl_vars - still waiting for sam to put it into HTML::Template. This may change. - fixed bug that caused NullPointerAssignment if closing tags were not in lowercase I need help finding bugs in the docs, and also suggestions to improve the howto on the site. Any suggestions? Philip |
From: Sam T. <sa...@tr...> - 2002-06-30 17:39:20
|
On Sun, 30 Jun 2002, Will wrote: > I am just learning both CGI.pm and HTML::Template. > Before I get too deep into my reading, I wanted to > ask: are there any possible conflicts I should watch > out for between CGI.pm and HTML::Template? None at all. In fact, HTML::Template has a feature that was made to work with CGI.pm: associate. Also, CGI::Application uses CGI.pm and has built-in support for HTML::Template. -sam |
From: Will <sel...@ya...> - 2002-06-30 16:55:27
|
Greets Folks, I am just learning both CGI.pm and HTML::Template. Before I get too deep into my reading, I wanted to ask: are there any possible conflicts I should watch out for between CGI.pm and HTML::Template? Thanks, Will __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
From: Cory T. <ct...@on...> - 2002-06-30 14:58:21
|
> -----Original Message----- > From: htm...@li... > [mailto:htm...@li...]On Behalf Of > Ralf Ullrich > > > Hi Philip, > > thanks for your help. > > ----- Original Message ----- > > 2.: a servlet class that reads it template via getPathTranslated(). The > template is parsed correctly and outputs exactly what i expect, > except if I > put a <TMPL_INCLUDE NAME="inc.tmpl"> in my template. > I guess the servlet doesn't know where the inc.tmpl isnt located. So I put > "path", "c:/templates" in template_init, but that doesn't work either. > Did I get the use of path wrong? Maybe you should look at the 'search_path_on_include' argument? You can turn off, in PERL H:T at least, the behavior to look in the list of paths specified by PATH. By default, new search the folder of the parent template (I think.) -- Cory |
From: Ralf U. <rul...@we...> - 2002-06-30 10:54:32
|
Hi Philip, thanks for your help. ----- Original Message ----- From: "Philip S Tellis" <phi...@gm...> To: "ralf ullrich" <rul...@we...> Sent: Friday, June 28, 2002 4:33 PM Subject: Re: [htmltmpl] html-template-java > open HTML/Tmpl/Parsers/Parser.java > function: > private String getTagType(String tag) > > > change (line 249): > tag_type = tag; > > to: > tag_type = tag.toLowerCase(); > This did the trick, tags do their job in uppercase now. But if I may ask another (probably stupid) question: where does the <TMPL_INCLUDE> tag search for the includes? I tried two classes in different contexts: 1.: a class for the command-line. the templates are located in the same directrory. when i run that class it finds it includes and parses them. no problem in this scenario. 2.: a servlet class that reads it template via getPathTranslated(). The template is parsed correctly and outputs exactly what i expect, except if I put a <TMPL_INCLUDE NAME="inc.tmpl"> in my template. I guess the servlet doesn't know where the inc.tmpl isnt located. So I put "path", "c:/templates" in template_init, but that doesn't work either. Did I get the use of path wrong? Yours, ralf |
From: Philip S T. <phi...@gm...> - 2002-06-28 18:25:58
|
Sometime Today, Charles Martin assembled some asciibets to say: > I had the exact same problem yesterday with html-tmpl-java. It > took me a while to figure out what exactly was wrong because, > instead of not returnning any output, my servlet just crashed when I > used </TMPL_LOOP> in caps ! I'm in the process of porting a system > just to see how things are 'doable' with a java servlet instead of a > perl-scripted site so the 'compatibility' site of html-tmpl is quite > interesting in my point of view... well, this is fixed in CVS if anyone else is interested, and will be in 0.0.9 when it comes out sometime next week. I've also included the escape=quote param for tmpl_var, but whether it stays in or not depends on whether sam's going to put it into HTML::Template or not. Philip -- When the wind is great, bow before it; when the wind is heavy, yield to it. |
From: Philip S T. <phi...@gm...> - 2002-06-28 14:27:53
|
On Fri, 28 Jun 2002, ralf ullrich wrote: > I hope this isn't off-topic in this list, but I have a question > concerning the use of html-template-java. The background is that I'm Hi, Philip here. Well, as long as the discussion is HTML-Template related, Sam says that it's okay to carry it on here. > planning to write an article about the use of htmltemplate as a > cross-language-templating-systems (as Sam Tregar said), mostly about > the perl , python and java-version. The motivation is to make > html-template a little bit more known outside the perl universe. I > started to write code for perl and python, and everything works like > one would expect. My only problem is the java version, which works > great if I use lower-case tags. But if I use upper-case <TMPL_LOOP > NAME="loop"> and close it accordingly my java servlet does not > generate any output. The strange thing is that it works if TMPL_LOOP > is in upper, but /tmpl_loop in lowercase; the same is true for the > conditionals. Does anybody have a glue? I asked this on the > htmltemplate-java list, but got no answer, so I turned to this list, I'll look into it. unfortunately I've been having trouble with sourceforge over the last few days, and was away from mail for a few weeks before that. Philip |