Re: [Catalyst] Use Undo on A List Apart

2007-07-28 Thread Matthieu Codron
Hi, Le 26 juil. 07 à 08:55, Bill Moseley a écrit : There's a recent article titled Never Use a Warning When you Mean Undo at http://alistapart.com/articles/neveruseawarning. I'm wondering about the implementation. I read that too. Interesting, but from what I see undo is not so easy to

Re: [Catalyst] Use Undo on A List Apart

2007-07-28 Thread Matt S Trout
On Sat, Jul 28, 2007 at 01:00:14PM +0200, Matthieu Codron wrote: Hi, Le 26 juil. 07 à 08:55, Bill Moseley a écrit : There's a recent article titled Never Use a Warning When you Mean Undo at http://alistapart.com/articles/neveruseawarning. I'm wondering about the implementation. I

Re: [Catalyst] Use Undo on A List Apart

2007-07-28 Thread Matthieu Codron
Le 28 juil. 07 à 14:05, Matt S Trout a écrit : I like more the idea of a generic undo request. This could be part of a plugin providing this action and the necessary infrastructure to implement the un-doing of the action. I fail entirely to see why this should be a plugin rather than part

Re: [Catalyst] Use Undo on A List Apart

2007-07-28 Thread Wade . Stuart
Matthieu Codron [EMAIL PROTECTED] wrote on 07/28/2007 11:22:36 AM: Le 28 juil. 07 à 14:05, Matt S Trout a écrit : I like more the idea of a generic undo request. This could be part of a plugin providing this action and the necessary infrastructure to implement the un-doing of the

Re: [Catalyst] Use Undo on A List Apart

2007-07-28 Thread Matthieu Codron
I do not know how this could be generalized for all apps. In the simple cases -- maybe. Consider the following scenarios that you would need to handle: * Change happens, the updated data affects the next 5 actions (via the current user or another user(s)) and then the user requests

[Catalyst] Use Undo on A List Apart

2007-07-26 Thread Bill Moseley
There's a recent article titled Never Use a Warning When you Mean Undo at http://alistapart.com/articles/neveruseawarning. I'm wondering about the implementation. One option is to create actions for every possible undo operation. That would mean that each undo operation would generate a specific