Webpy templetor or home rolled template is quirky requires tabs and 4 spaces
like regular pythona new line breaks the templates
it is very unusable
Tyler: I'm genuinely curious for the usecases for dynamically compiled
templates in this fashion since we don't use anything like this at
Slide.
Our usage of cheetah was from the webpy example
http://webpy.org/cookbook/template_cheetah
So we didnt know you could compile templates till you showed me...
Can you also show how you setup Cheetah and your templates and deploy them
at slide as opposed to dynamically compiled templates in webpy
thanks
On Tue, May 5, 2009 at 1:31 PM, R. Tyler Ballance <[email protected]> wrote:
> On Tue, May 05, 2009 at 09:01:10PM +0100, Jeremy James wrote:
> > [email protected] wrote:
> > > Hey tavis and Tyler
> > > If you really *must* avoid first compiling foo.tmpl, then for now the
> > > #include would be what you'd want. See:
> > >
> > >
> http://www.cheetahtemplate.org/docs/users_guide_html/users_guide.html#SECTION000860000000000000000
> > >
> > > *We cant compile templates in webpy and include is what we need*
> > > *So please DONT PHASE OUT #includes*
> > > *all our code base uses #include
> >
> > On the contrary - unless you've re-written webpy's cheetah.py [1], then
> > it does its own hacky #include, and dropping support from Cheetah will
> > make no difference to you.
> >
> > For what it's worth, I support removing #include and using more
> > intelligent on-demand compiling of parent templates required by #extends
> > if a user doesn't want to compile to .py first.
>
> That sounds like a good middle-ground to me, but I'm curious as to why
> users (read: you's guys ;)) aren't compiling templates? From your point
> of view what are the benefits to this approach that is gained over
> compiling .tmpl->.py via `cheetah compile`?
>
> I'm genuinely curious for the usecases for dynamically compiled
> templates in this fashion since we don't use anything like this at
> Slide.
>
> > [1] web.py has deprecated cheetah support for its home-rolled templating
> > language (which continues to look more like Cheetah every day). However,
> > for the old support that the OP is referring to, see the
> > __compiletemplate function at the top of
> >
> http://github.com/webpy/webpy/blob/a5a1ab1cb10106ea678e9741790668063c3cfdd1/web/cheetah.py
>
> Why they decided to roll their own template language is still beyond me,
> my only guess is Django-envy.
>
> Cheers
>
> --
> -R. Tyler Ballance
> Slide, Inc.
>
--
Bidegg worlds best auction site
http://bidegg.com
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Cheetahtemplate-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cheetahtemplate-discuss
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.