Re: [Zope-CMF] Re: Add forms and menus

2008-07-16 Thread Charlie Clark
Am 15.07.2008 um 23:38 schrieb Martin Aspeli: Actually, that's interesting... what purpose does 'initial view' serve in a world with add forms? The same as it ever has - you redirect to the initial view from the add form because the add form is actually registered for the container

Re: [Zope-CMF] Re: Add forms and menus

2008-07-16 Thread Robert Niederreiter
Am Dienstag, den 15.07.2008, 22:34 +0100 schrieb Martin Aspeli: Daniel Nouri wrote: Daniel Nouri writes: Robert Niederreiter writes: yuppie writes: I like pretty URLs, and 'foo/+/MyPortalType' looks much prettier than the URLs needed with my approach:

Re: [Zope-CMF] Re: Add forms and menus

2008-07-16 Thread Robert Niederreiter
Hi, So, let me try to summarise what I think we're saying here: - My type has a form like: class MyAddForm(CMFBaseAddForm): fields = form.Fields(IMyType) portal_type = 'My type' - The base form knows to look at self.factory_name to look up the factory when it does the

[Zope-CMF] CMF Tests: 9 OK

2008-07-16 Thread CMF Tests Summarizer
Summary of messages to the cmf-tests list. Period Tue Jul 15 11:00:00 2008 UTC to Wed Jul 16 11:00:00 2008 UTC. There were 9 messages: 9 from CMF Tests. Tests passed OK --- Subject: OK : CMF-1.6 Zope-2.8 Python-2.3.6 : Linux From: CMF Tests Date: Tue Jul 15 21:41:22 EDT 2008 URL:

[Zope-CMF] Re: Add forms and menus

2008-07-16 Thread Martin Aspeli
yuppie [EMAIL PROTECTED] writes: class MyAddForm(CMFBaseAddForm): fields = form.Fields(IMyType) portal_type = 'My type' Here you are mixing up content type with portal type. We can't hardcode the portal type if we want to use the add form for renamed/derived portal types as

[Zope-CMF] Re: Add forms and menus

2008-07-16 Thread Martin Aspeli
Robert Niederreiter [EMAIL PROTECTED] writes: +/- i would provide a default add form anyway. consider how archetypes works. Not necessarily an example to follow, though, is it. :) you never write an addform (especially because there are none :)). for most of the usecases default sequencial

[Zope-CMF] Re: Add forms and menus

2008-07-16 Thread Daniel Nouri
Martin Aspeli writes: If we want to be true to the tradition of Zope 3 and its simplified content types metaphor, then I think we should assume that a type consists of: - a class - a schema interface - an add form/view - an edit form/view plus the FTI to install it into the CMF site.

Re: [Zope-CMF] Re: Add forms and menus

2008-07-16 Thread Robert Niederreiter
Am Mittwoch, den 16.07.2008, 13:04 + schrieb Martin Aspeli: Robert Niederreiter [EMAIL PROTECTED] writes: +/- i would provide a default add form anyway. consider how archetypes works. Not necessarily an example to follow, though, is it. :) you never write an addform

[Zope-CMF] Re: Add forms and menus

2008-07-16 Thread Daniel Nouri
Robert Niederreiter writes: 2 more properties on the fti (addforminterface, schemainterface), both are optional, but provide then the discussed and requested flexibility for different type implementations. If you copy a FTI, you can probably reuse the add and edit forms available for the type

Re: [Zope-CMF] Re: Add forms and menus

2008-07-16 Thread Daniel Nouri
Robert Niederreiter writes: Am Mittwoch, den 16.07.2008, 16:24 +0200 schrieb Daniel Nouri: Where would we need overrides.zcml? in the case where ICMFAddForm is no longer my interface to look up. then i have to overwrite the traverser. Why would ICMFAddForm no longer be the interface to look

[Zope-CMF] Re: Add forms and menus

2008-07-16 Thread Martin Aspeli
it's not that big architectual change. everything else discussed is possible anyway. i would rather call it a feature than a design change (since the change happens anyway). I think it's a fairly big shift to assume that the FTI has knowledge of the schema of the type. It's not necessarily a

Re: [Zope-CMF] Re: Add forms and menus

2008-07-16 Thread Wichert Akkerman
Previously Martin Aspeli wrote: it's not that big architectual change. everything else discussed is possible anyway. i would rather call it a feature than a design change (since the change happens anyway). I think it's a fairly big shift to assume that the FTI has knowledge of the

[Zope-CMF] Re: Add forms and menus

2008-07-16 Thread Martin Aspeli
Wichert Akkerman [EMAIL PROTECTED] writes: Possibly related: I have often had a desire to be able to annotate or extend the FTI. In Plone (and to a lesser degree CMF) we have lots of settings that change a portal type's behaviour that are stored in various places: versioning settings, markup

[Zope-CMF] Re: Add forms and menus

2008-07-16 Thread Martin Aspeli
Daniel Nouri [EMAIL PROTECTED] writes: Robert Niederreiter writes: Am Mittwoch, den 16.07.2008, 16:24 +0200 schrieb Daniel Nouri: Where would we need overrides.zcml? in the case where ICMFAddForm is no longer my interface to look up. then i have to overwrite the traverser. Why

[Zope-CMF] Re: Add forms and menus

2008-07-16 Thread Daniel Nouri
Martin Aspeli writes: Daniel Nouri [EMAIL PROTECTED] writes: Robert Niederreiter writes: Am Mittwoch, den 16.07.2008, 16:24 +0200 schrieb Daniel Nouri: Where would we need overrides.zcml? in the case where ICMFAddForm is no longer my interface to look up. then i have to overwrite