Re: [Krang-devel] "current version"

[Noam W. <nwe...@er...>]

Sorry guys! Another message about this after sleeping and realizing my 
thoughts were a bit jumbled last night...

Do you have a preference between these solutions? (For the scenario where a 
user is editing a story at version 9 and wants to revert to 5.)

1) Version 10 is written to disk right away, and the screen now displays 
"Version 10 (Copied from Version 5)"
The next time it is saved, it will be version 11 (And we don't worry about 
the useless version 10 which remains identical to 5)

2) Version 10 is written to disk right away, and the screen now displays 
"Version 10 (Copied from Version 5)".
The next time it is saved, keep_version => 1 is used
(This way we avoid a useless version; whether or not the user makes changes 
the new version will be 10, not 11)

3) Version 10 -- as in the current behavior -- isn't written to disk until 
the user hits Save, but the messages are improved and the screen clarifies 
that the session has been copied from 5 but not yet saved. Perhaps the 
History logic is also changed so the revert message doesn't get logged until 
10 is saved.

??

Noam

----- Original Message ----- 
From: "Noam Weinstein" <nwe...@er...>
To: "Bodo Schulze" <bo...@le...>
Cc: <kra...@li...>
Sent: Friday, March 28, 2008 7:29 AM
Subject: Re: [Krang-devel] On category selector, show OK button only if 
functional


> >A more unobtrusive way would
>> be to just disable those buttons, showing them in a "disabled-color",
>> when no boxes are checked. As far as I see this is the standard way to
>> do things. Thoughts?
>
> I think that's definitely ideal - it also makes clear that those buttons 
> exist and may become active based on the user's choices...