Re: The latest templating system: PSP in DDJ
I think that a "templating system" is the core component of a CMS (content management system). Probably the right direction (for a good TS) is an engine like Axkit. It support other templating system like ASP and Mason too. It need more documentation and more real world examples and more users (IMHO). The link XSP guide / "Real World Example" is still empty. The "quick and dirty" way for a CMS/Template System is not the best. I think we should also look at Java related project, learn the lesson and apply in Perl: Coocoon, Struct, JSP, EJB Take a look at www.caucho.com for a great job. Francesco - Original Message - From: "Ron Savage" <[EMAIL PROTECTED]> To: "mod_perl" <[EMAIL PROTECTED]> Sent: Tuesday, July 10, 2001 2:08 AM Subject: Re: The latest templating system: PSP in DDJ > > FWIW, Greg McCarroll is writing an article for perl.com on a short > > comparison of templating systems, and of course we'll have a talk on > > the subject at TPC by Perrin. > > Ahhh, 'short'. But that's another problem. I realize such articles are hard work, but (especially for those of us struggling to > choose a templating system) is anybody collecting URIs of articles which give practical examples of using such systems? I'm thinking > of one-template-per-article style, so we can actually learn how to use them, rather than a list of features. > > Cheers > Ron Savage > [EMAIL PROTECTED] > http://savage.net.au/index.html > > >
Re: The latest templating system: PSP in DDJ
> FWIW, Greg McCarroll is writing an article for perl.com on a short > comparison of templating systems, and of course we'll have a talk on > the subject at TPC by Perrin. Ahhh, 'short'. But that's another problem. I realize such articles are hard work, but (especially for those of us struggling to choose a templating system) is anybody collecting URIs of articles which give practical examples of using such systems? I'm thinking of one-template-per-article style, so we can actually learn how to use them, rather than a list of features. Cheers Ron Savage [EMAIL PROTECTED] http://savage.net.au/index.html
Re: The latest templating system: PSP in DDJ
> What is needed, IMHO, is a clear > framework,/description/phlogeny/geneology of perl templating systems. I'm writing such a beast for TPC this month, and will publish it when it's ready. I'm not covering every templating module on CPAN though, just the ones that people seem to actually use based on mailing list traffic. (Don't e-mail your "But I use such and such" messages yet. Wait until you see my list.) This is mostly for sanity purposes -- there's just too many to cover all of them in a meaningful way. It won't solve all the world's problems, but it might help some people find a tool that suits them. - Perrin
Re: The latest templating system: PSP in DDJ
Ron Pero sent the following bits through the ether: > Don't give up. What is needed, IMHO, is a clear > framework,/description/phlogeny/geneology of perl templating systems. FWIW, Greg McCarroll is writing an article for perl.com on a short comparison of templating systems, and of course we'll have a talk on the subject at TPC by Perrin. Leon ps we've just had a templating flamewar on the london.pm-list, so please let it die down here too ;-) http://london.pm.org/pipermail/london.pm/2001-June/000681.html -- Leon Brocard.http://www.astray.com/ Iterative Software...http://www.iterative-software.com/ ... You seem a decent fellow, I hate to kill you
Re: The latest templating system: PSP in DDJ
At 01:01 AM 07/08/01 -0400, Perrin Harkins wrote: >> The latter gives you the ability to develop custom tag modules to >> encapsulate complex server-side behaviors and business rules into simple >> XML-like elements that content developers can use. >> PSP shares the same basic elements with JSP..." > >Good grief! This sounds exactly like Apache::ASP with its XMLSubs feature. >I give up. >- Perrin Dear Perrin Don't give up. What is needed, IMHO, is a clear framework,/description/phlogeny/geneology of perl templating systems. Yes, TMTOWTDI is good, and yes, the tendency of open source programmers to write programs that "scratches their itch" is good, but it is also good to do so in the context of an appropriate amount of organization. CPAN is a good example. Lots of modules, ORGANIZED BY CATEGORY. CPAN is incredibly useful. But I believe CPAN would benefit by one more step of organization: a czar of each category. The czar would be see to it that his category has an Overview Document that includes topics like an overview of the topic (think of using encryption when you have never studied it), available modules and what they do and why, when to use which module, links to related materials, etc. He would also help create a framework or architecture for the module space: map out a list of modules that would adequately cover the topic, including levels for major modules of full, middlin, and lite versions. Keep a list of what needs to be done, so people will improve the existing wheels instead of inventing new ones. A framework would help categorize the numerous modules that can accumulate, some major and several minor -- perhaps an "overflow" bin where tiny modules that don't warrant inclusion in the major module space can reside. Templating systems is an excellent candidate for this. Just some thoughts. Ron
Re: The latest templating system: PSP in DDJ
Perrin Harkins wrote: > > on 7/7/01 9:30 PM, Ron Pero at [EMAIL PROTECTED] wrote: > > > Just received my issue of Dr. Dobbs Journal today, and one of the articles > > is "A Tiny Perl Server Pages Engine". Pretty nifty. > > > > Read about it here: > > http://www.ddj.com/articles/2001/0108/0108g/0108g.htm > > > > Here is an excerpt: > > "PSP is modeled after JSP. It is neither an ASP nor a JSP port. PSP > > includes many JSP-like features and, most importantly, custom tag support. > > The latter gives you the ability to develop custom tag modules to > > encapsulate complex server-side behaviors and business rules into simple > > XML-like elements that content developers can use. > > PSP shares the same basic elements with JSP..." > > Good grief! This sounds exactly like Apache::ASP with its XMLSubs feature. > I give up. All Andy Yuen, author of PSP, had to do was ask that Apache::ASP get ported to run under old school CGI... I already have it mostly working, just never had incentive to finish the job. Maybe I'll finish that off now that I've seen lack of ASP's CGI support posted in an article :) --Josh _ Joshua Chamas Chamas Enterprises Inc. NodeWorks <- Web Link Checking Huntington Beach, CA USA http://www.nodeworks.com1-714-625-4051
Re: The latest templating system: PSP in DDJ
On Sunday 08 July 2001 03:30, Ron Pero wrote: > Just received my issue of Dr. Dobbs Journal today, and one of the articles > is "A Tiny Perl Server Pages Engine". Pretty nifty. > > Read about it here: > http://www.ddj.com/articles/2001/0108/0108g/0108g.htm Nifty indeed, if you're interested in such systems, you may wish to check out AxKit's XSP implementation, it's good, and becoming faster every day. -- ___ Robin Berjon <[EMAIL PROTECTED]> -- CTO k n o w s c a p e : // venture knowledge agency www.knowscape.com --- Sleep is no substitute for coffee.
Re: The latest templating system: PSP in DDJ
On Sun, 8 Jul 2001, Perrin Harkins wrote: > Good grief! This sounds exactly like Apache::ASP with > its XMLSubs feature. except with asp you get the whole asp web application environment as well.
Re: The latest templating system: PSP in DDJ
on 7/7/01 9:30 PM, Ron Pero at [EMAIL PROTECTED] wrote: > Just received my issue of Dr. Dobbs Journal today, and one of the articles > is "A Tiny Perl Server Pages Engine". Pretty nifty. > > Read about it here: > http://www.ddj.com/articles/2001/0108/0108g/0108g.htm > > Here is an excerpt: > "PSP is modeled after JSP. It is neither an ASP nor a JSP port. PSP > includes many JSP-like features and, most importantly, custom tag support. > The latter gives you the ability to develop custom tag modules to > encapsulate complex server-side behaviors and business rules into simple > XML-like elements that content developers can use. > PSP shares the same basic elements with JSP..." Good grief! This sounds exactly like Apache::ASP with its XMLSubs feature. I give up. - Perrin