Dear Bruno

Great to hear that there are other ZOPE users among us.

When I work with ZOPE I code with dtml. I only found out about ZPT
when I quiz ZOPE and never got familiar with it afterwords. The first
thing they teach you when working with ZOPE is to combine segment of
web pages with <dtml-var "aSegment.html">. With this I could prepare
some page with other tags or javascript/css and it will all render
normally.

I was kind of disappointed that I didn't find any thing similar here
and page inheritance is still new to me so I didn't consider
it first.

I want to create a application that uses minimal html files. At the
present stage of development, coded everything into one html and save
all the static data into the database.

I want to know about re-rendering a django tag/javascript/css is
because I want to allow my users to use a web interface to create
their own contents and with custom tag that I created and save it back
to the
database.

If everything work accordingly, the custom tag will activate and put
javascript/googleMap api onto the page and display a google map. But
sadly it didn't gone according to plan and the page only
displayed the tag as if it was just text.

So.. does anyone have any idea how I could solve this problem?

Allen



On Nov 27, 6:06 pm, bruno desthuilliers
<[email protected]> wrote:
> On 27 nov, 09:35, Allen <[email protected]> wrote:
>
> > Dear Andy McKay
> > Thanks for the input and you're right, I shouldn't do it this way.
>
> > I use to use ZOPE for a couple of years and it has to abilities to
> > integrate multiple static webpages just by write a tag with the static
> > webpage filename similar to the filter tag.
>
> ZPT or dtml ? I've done my share of Zope / ZPT (and still do when
> someone points a gun at me), and from memory I don't see what you're
> talking about...
>
> > But I just started django
> > a month ago and I didn't see function of this sort except for page
> > inheritance.
>
> Well, there's an include tag, but if that's not what you're after, you
> can write your own cutom tag.
>
> > I have consider using page inheritance but I just not use to it.
>
> You should, definitly. Page inheritance work mostly like the "page
> macro" pattern in ZPT - except it's way cleaner.
>
> > That's why I place it in the database. This is just my temporary fix
> > for the time being and I know eventually I find a problem with this
> > way soon of later.
>
> Well, putting template code in the DB is not necessarily totally dumb
> - but you need to explicitely render it, which is not supported OOTB,
> so you either have to do it in the view or write some custom tag /
> filters to take care of the rendering.
>
> You'll find relevant doc here:
>
> http://docs.djangoproject.com/en/dev/ref/templates/api/#ref-templates...http://docs.djangoproject.com/en/dev/howto/custom-template-tags/#howt...

--

You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected].
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