[Zope3-dev] standalone Zope3 ZPT

[Corey]

Hello!

I'm about to dust off an old project written in perl w/ xml, and completely
rewrite it using python w/ page templates.

I'd like to use Zope3's zope.pagetemplates, but I don't want to use or
package up the rest of Zope3.  So what I did was grab the latest cvs,
and I began going through the dependencies ( DEPENDENCIES.cfg was
obviously a huge help here ). What I found, is it looks like it should be
fairly easy for me to completely decouple ZPT from Zope, but I have a
couple questions.

Obviously, I'll need the following:

zope.pagetemplates
zope.tal
zope.tales

I don't want to use the testing or i18n frameworks, so I would very
much like to get rid of the following dependencies:

zope.testing
zope.i18n
zope.i18nmessageid

... as well as zope.schema and zope.component - which both rely on
zope.i18n.  

I haven't yet looked into exactly how difficult it would be to decouple the
i18n stuff from zope.tal - I'm hoping it'll be fairly simple. Am I right? Or
will it be very difficult?

Also, I'm wondering about zope.interface - will it be possible to get rid
of that dependency as well, or will it be too much work?


My goal here is to keep things down to the bare minimal... which is why
I would ideally only want the zope.pagetemplates, zope.tal and zope.tales
libs, though I wouldn't mind keeping the zope.exceptions framework because
it is very small. 

So, assuming I can get rid of i18n, my last question is concerning the
zope.interface framework.  The problem here is that it is rather large and
that none of my code will be using the interface specification to python
that Zope3 introduces. I can only imagine though that it will be unrealistic
to decouple pagetemplates, tal and tales from interface though - is this
true?


Thanks!

Corey


-- 

"To a mind that is still, the whole universe surrenders."
  - Chuang Tzu