[Zope-PTK] PTK features

Rik Hoekstra rik.hoekstra@inghist.nl
Mon, 30 Oct 2000 13:23:18 +0100


I'm building new products for our own site. Many of them actually do
many of the same things as the PTK does, but they are different enough
not to use an out of the box PTK. 

I'm a bit unsure about using the PTK right now, as it seems to be a bit
of a moving target. This is natural as it hasn't stabilized. An example
is the Dublin Core stuff, that seems to be shifting quite a bit lately
(for the best, probably, but that's not the point). 

As I'm still implementing, I'm still flexible and this is not a real
problem right now, but it would be good to know what we can expect as
core features in the PTK once it stabilizes. At the moment there doesn't
seem to be a target API or target feature set. This makes deriving from
the PTKBAse a bit awkward at the moment. What is the best policy for
this; would such a target API be a good idea? Or perhaps a division
between basic PTK functionality and extended functionality in which the
PTK base is most stable?

Rik