[Zope3-dev] RFC: preCreation view, postCreation view use cases

[Chris Withers]

Guido van Rossum wrote:
> 
> > * we ought to be able to specify pre-creation views (plural!) of an
> > object, that will let us provide TTW the values needed to
> > instantiate an object (including a file upload).  This seems
> > particularly important to me to be able to use non-Zope specific
> > classes.
> 
> Very interesting.  That need came up in the jobboard example too!  It
> has two pre-creation views: one is a form that lets you enter the
> content fields, one is a preview page that lets you see how the object
> would be shown after creation.  IMO this is a pretty useful pattern; I
> used it in the Python FAQ wizard.  I'm curious how you can provide a
> general framework for this feature -- maybe a look at the jobboard
> example (checked in as Packages/JobBoardEx on cvs.zope.org) would help
> you.

Well, Zope 2 has this although I don't particularly like the way it's done, I can't think
of a better alternative.

BTW, the pre-creation view is often the normal edit view + an id field. IS this a pattern
we can enhance for? The CMF does a pretty good job, but it doebns't let you edit objects
before you create them, which kinds sucks for simple apps like Squishdot/Swishdot...

> > * we ought to be able to specify a default post-creation view of an
> > object, to which the creation process will automatically direct the
> > user after object creation.
> 
> Also very interesting.  The jobboard example has the need of a default
> view (also for the whole jobboard itself).  We discussed this with Jim
> over lunch yesterday, and he agreed that a default view was a good
> idea.  But then he hopped on a plane to Europe where he'll stay for
> three weeks, so it may be a while.

...the CMF way of tackling this was pretty cool. I really like the Types Tool. Whats'
gonna be the Zoep 3 equivalent?

cheers,

Chris