On Friday 15 November 2002 1:25 am, John Levon wrote:
> On Fri, Nov 15, 2002 at 11:11:26AM +1000, Allan Rae wrote:
> > Can't you just make controller.OKButton() call save() for you since
> > "Save" is really just a relabelled OK button? (overloading maybe?)
>
> good idea. Let's see...
>
> > I have
On Fri, Nov 15, 2002 at 11:11:26AM +1000, Allan Rae wrote:
> Can't you just make controller.OKButton() call save() for you since
> "Save" is really just a relabelled OK button? (overloading maybe?)
good idea. Let's see...
> I haven't managed to find time to understand how MVC works yet...
Me n
On Fri, 15 Nov 2002, John Levon wrote:
> On Thu, Nov 14, 2002 at 11:29:04PM +, John Levon wrote:
>
> > Angus, how on earth are we supposed to cope with "Save" ? Must we really
> > add another type to the state machine ? (if there is workaround, we can
> > remove unused PreferencesPolicy)
>
> A
On Thu, Nov 14, 2002 at 11:29:04PM +, John Levon wrote:
> Angus, how on earth are we supposed to cope with "Save" ? Must we really
> add another type to the state machine ? (if there is workaround, we can
> remove unused PreferencesPolicy)
Ah, we can send it to input() and call controller().O
The attached is the beginning of moving xforms prefs dialog to
MVC.
Angus, how on earth are we supposed to cope with "Save" ? Must we really
add another type to the state machine ? (if there is workaround, we can
remove unused PreferencesPolicy)
There's probably more than can be moved to the con