On Mon, Dec 30, 2002 at 02:30:18PM +0100, Rickard Öberg wrote: > Philipp Meier wrote:
> >My favourite usecase is the show-edit-update-show usecase. Which means > >having the need to pass the primary key of the object updated to the > >action show which is the view of the Update action. Views.proptiers > >whould look like that: > > > >Show.success=show.xslt > >Update.success=Show.action > > I would personally prefer that Update redirects to Show instead, because > otherwise a refresh will do the update again. The browser location > should never point to an action that "does things". Yes, you're right, but the point is that one need to pass some data (the key) to the redirect action. There two ways, doing it automatically or explicitely. > Not straight away. Not quite seeing what is wrong with the current way > of doing views which needs to be fixed. I'd like a higher degree of resuse of the transformation in the different "transports". I will definetly contribute a MailDispatcher soon and I'd like to share code when using XSLT as a transformation engine. But this is no great issue. More a general question of reuse. -billy. -- Meisterbohne Söflinger Straße 100 Tel: +49-731-399 499-0 eLösungen 89077 Ulm Fax: +49-731-399 499-9
msg00879/pgp00000.pgp
Description: PGP signature
