Wednesday, October 2, 2002, 6:46:38 AM, you wrote:

 Hi Nick,

 I'm not sure what version of the client code you are using... there
 are distinct template systems in place for the default code vs. the
 SF code (HTML::Template and BOTS respectively).  Either way the
 templates will not be parsed by your httpd because the CGI output is
 inherently parsed already and not re-parsed by the server as a .shtml
 file might be.  I suppose it is possible of course but not likely in
 a standard setup AFAIK.

 Are you interested in actually expanding the *Template System* or
 simply the data you can pass around using the template system.  Both
 versions (HTML::Template and BOTS) are pretty extensive as-is and
 simply need massaging at the SRS code level to enable the
 passing/tracking/displaying of additional variables, etc.   Just
 curious. And willing to help if you want to send me some examples
 of what you need to accomplish off-list.

 Regards,
 -tom

 
NP> I am interested in expanding the functionality of the template system in the 
NP> opensrs perl client.

NP> I originally attempted to configure my web server to parse the output of the 
NP> CGI for SSI and that sort of worked..  Although if the SSI portions 
NP> generated the OpenSRS PlaceHolder tags they would not be parsed by the perl 
NP> client.  For example if I had <!--#exec cgi="/cgi-bin/test.cgi"--> generate 
NP> {{CONTENT}} as part of it's output it would just display "{{CONTENT}}".  
NP> Also, if the above test.cgi output additional SSI tags it would not be 
NP> parsed either.

NP> So, I would consider that a failure.  It seems my only hope to do what I am 
NP> looking for, barring writing my own client, would be to add additional 
NP> PlaceHolder tags into the perl client.

NP> Does anyone have any suggestions that might help me get started in this?

NP> Thanks,

NP> Nick Powers

NP> _________________________________________________________________
NP> MSN Photos is the easiest way to share and print your photos: 
NP> http://photos.msn.com/support/worldwide.aspx

Reply via email to