[Zope-PTK] PTK II
Fri, 28 Jul 2000 18:07:21 -0600
Shane Hathaway wrote:
> What do you think of the following direction for the development of
> I envision PTK as not a framework but a toolkit. A framework is a
> thing which is mostly built but needs customization. It's like leasing
> office space. A toolkit is less restrictive but more flexible. It's
> like having the tools and materials to build your own office space.
> So PTKBase should be a toolkit while PTKDemo is a framework built from
> that toolkit.
That sounds good to me. Especially if it means I can build a portal site at the root of my
ZODB, rather than needing to have a sub-folder for it.
> So I came up with an idea. What we want to be able to do is have a set
> of "tools" at the base of the portal. These tools would include:
> - Membership database
> - Workflow attribute access
> - Discussion access
> The default membership database would be a thin layer on top of the
> acl_users object. It could be replaced with a ZPatterns specialist
> that looks up users from any number of sources.
> The default workflow attribute access tool would query documents about
> their workflow status, as is done now. But it should be possible to
> retrieve and store workflow status in another way, such as from context
> or using a specialist. This could be achieved by replacing the default
Sounds good to me. Of course, I've been doing quite a bit of playing with ZPatterns, so I
may be biased. :)
> The discussion access tool would enable us to solve a problem we have
> right now: every view of any portal content generates a catalog query.
> That's not necessarily a good thing. The discussion access tool could
> govern the storage of discussion information.
Agreed. Th ecurrent discussable thing is downright aggravatign, IME. IMO, it would be nice
if discussable was changeable. Perhaps like a switch, settable at instantiation,, and in
the config. Then you could do things like have a discussionable item only open for
discussion for a limited, for example.
Do not meddle in the affairs of sysadmins, for they are easy to annoy,
and have the root password.