Why - "Unsaved changes do you wish to retain them" vs. "Save them"?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Why - "Unsaved changes do you wish to retain them" vs. "Save them"?

TimM-3
I wonder if its me - but when I change a method and then just click on new
method, why does it not prompt to let me simply save my changes and then
select the method I clicked on?

The "do you wish to retain them" seems like a non-obvious question - as yes
take me back to the code where I have to press Ctrl-S and then click on my
method again. Which seems very long winded.

I wonder if its a bit of implementation history (it wasn't easy to save and
continue?). Or maybe a "Save changes" Yes/No/Cancel messagebox would be
better?

Tim


Reply | Threaded
Open this post in threaded view
|

Re: Why - "Unsaved changes do you wish to retain them" vs. "Save them"?

Blair McGlashan
"TimM" <[hidden email]> wrote in message
news:[hidden email]...

>I wonder if its me - but when I change a method and then just click on new
>method, why does it not prompt to let me simply save my changes and then
>select the method I clicked on?
>
> The "do you wish to retain them" seems like a non-obvious question - as
> yes take me back to the code where I have to press Ctrl-S and then click
> on my method again. Which seems very long winded.
>
> I wonder if its a bit of implementation history (it wasn't easy to save
> and continue?). Or maybe a "Save changes" Yes/No/Cancel messagebox would
> be better?

Yup, could be better. Its historical. When we originally implemented it, we
couldn't get the "save now" option to work reliably with reasonable effort -
the issue being that it may cause knock on changes in other browsers that
might require further prompts. This causes problematic interactions with
some of the Windows controls in terms of selection management that we hadn't
quite sorted out at the time. Its probable that there would be no issue
today (or that it would be manageable), but I'm afraid its not been a high
priority item to change because we've got use to it as it is. Yes I know
that familiarity is not a good reason to address a usability issue...

Regards

Blair


Reply | Threaded
Open this post in threaded view
|

Re: Why - "Unsaved changes do you wish to retain them" vs. "Save them"?

TimM-3
I wondered if that was the case. Have put it in as an enhancement request.

I do think you guys are getting quite close on the usability side - the way
the Idea space and code completion hang together - Smalltalk is definitely
looking less embarrasing on the IDE usability front. I am finally able to
point my Java and .net colleagues to your "Whats new flash demo" and not
wince. Actually a few people have commented that they quite fancy learning
ST - so that BitWise offer comes at a good time.

Thanks,

Tim

"Blair McGlashan" <[hidden email]> wrote in message
news:[hidden email]...

> "TimM" <[hidden email]> wrote in message
> news:[hidden email]...
>>I wonder if its me - but when I change a method and then just click on new
>>method, why does it not prompt to let me simply save my changes and then
>>select the method I clicked on?
>>
>> The "do you wish to retain them" seems like a non-obvious question - as
>> yes take me back to the code where I have to press Ctrl-S and then click
>> on my method again. Which seems very long winded.
>>
>> I wonder if its a bit of implementation history (it wasn't easy to save
>> and continue?). Or maybe a "Save changes" Yes/No/Cancel messagebox would
>> be better?
>
> Yup, could be better. Its historical. When we originally implemented it,
> we couldn't get the "save now" option to work reliably with reasonable
> effort - the issue being that it may cause knock on changes in other
> browsers that might require further prompts. This causes problematic
> interactions with some of the Windows controls in terms of selection
> management that we hadn't quite sorted out at the time. Its probable that
> there would be no issue today (or that it would be manageable), but I'm
> afraid its not been a high priority item to change because we've got use
> to it as it is. Yes I know that familiarity is not a good reason to
> address a usability issue...
>
> Regards
>
> Blair
>