ffu, here is how to use kid in django
http://blogs.translucentcode.org/mick/2005/09/29/using_kid_with_django/

On Jun 3, 9:50 am, Nicola Larosa <[EMAIL PROTECTED]> wrote:
> IttayDror wrote:
> > I was wondering if anyone has thought about makingdjango'stemplating
> > system more in the concepts of wicket (there are other such templating
> > engines, this is the one i've used).
>
> That's not going to happen, as you know by now. However, using any other
> templating system inDjangois very easy (as is usingDjangotemplates
> elsewhere, by the way).
>
> > With wicket, the template is just a regular HTML with attribute that
> > identify snippets of HTML that need to be dynamically created. Then, the
> > backend code can substitute these snippets, usually by reusing them, and
> > injecting dynamic content.
>
> There are a number of Python templating systems that work like that, here
> are the ones I know of:
>
> ZPT - Zope Page Templateshttp://wiki.zope.org/ZPT/FrontPage
>
> Kidhttp://www.kid-templating.org/
>
> Genshihttp://genshi.edgewall.org/
>
> Simple Template Language 
> (STL)http://download.ikaaro.org/doc/itools/Chapter--STL.html
>
> Templesshttp://templess.johnnydebris.net/
>
> Nevow XML 
> templateshttp://divmod.org/trac/browser/trunk/Nevow/doc/txt/nevow-xml-template...
>
> > The cool thing is that wicket templates contain no logic (nor loops or
> > conditions) and are valid HTML. So designers don't need to think in
> > logic and can design (and maintain) the templates in their favorite HTML
> > editor.
>
> I used to see it like you do, but I've come to the conclusion that this is
> a non-use case, basically wishful thinking. I never actually saw anyone
> working like that, never saw any WYSIWYG tool that reads, keeps intact, and
> writes back the needed attributes.
>
> Here's a deep and wide discussion about pros and cons of XML-based templates:
>
> Which Part of "No XML" Don't You 
> Understand?http://www.artima.com/forums/threaded.jsp?forum=106&thread=146647
>
> --
> Nicola Larosa -http://www.tekNico.net/
>
> The big SOAP boys are now admitting they f'd up big time. Let's see how
> they try to make a dime off of HTTP and other really open and already
> proven and relatively simple technologies. Good luck with that. [...]
> Isolating crap like SOAP and ultimately removing it are steps toward
> sanity and successful transition. -- Patrick Logan, January 2007


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to