[Sugar-devel] Screenshot feature [GSoC Project]

[Utkarsh Tiwari]

Hi,
     I have all these following listed inconsistencies as suggested ->
1- Esc key handler removed.
2- Enter key hander removed.
3- Now the screenshot can be saved only via save(check) toolbutton.
4- The screenshot alert can be 'not save' or 'cancelled' via cancel(X)
toolbutton.

PR- https://github.com/sugarlabs/sugar/pull/675

Please update me if further modifications are required.

Thank you,
Utkarsh Tiwari

On 4/8/16, Tony Anderson <tony_anderson at usa.net> wrote:
> Hi,
>
> Consistency is very important to our users. Using Esc for this is unusual.
>
>
> I have trouble following the screencast. It looks like you offer a check
> and an x for the user. It also looks like an enter after providing the
> title acts as
> the check. The x appears to save the screenshot without changing the
> title. The user doesn't appear to have an option not to save the
> screenshot. Arguably the workflow would be to complete the task and then
> go to the Journal to erase the unneeded screenshots. I have taken
> screenshots and realized, for example, that the cursor was not on the
> right toolbar item. For these, I would like to be able to have a 'no
> save' option.
>
> Using Esc is not consistent with the way the rest of Sugar works and
> doesn't seem needed since you offer an equivalent one-click option in
> the alert/pop-up.
>
> Tony
>
> On 04/08/2016 02:07 PM, Utkarsh Tiwari wrote:
>> Hi,
>>      Here is the PR to the screenshot feature ->
>> https://github.com/sugarlabs/sugar/pull/675
>>
>> Thank you,
>> Utkarsh Tiwari
>>
>> On 4/4/16, Utkarsh Tiwari <iamutkarshtiwari at gmail.com> wrote:
>>> Hi Dave,
>>>               Thanks for your appreciation. I think this feature isn't
>>> intrusive also because if the user wants to ignore or cancel the save,
>>> he can simply do so by pressing Esc key.
>>>
>>> Golden Rule- Giving the user a choice to do something but not force it.
>>> ;)
>>>
>>> Thanks,
>>> Utkarsh Tiwari
>>>
>>> On 4/4/16, Dave Crossland <dave at lab6.com> wrote:
>>>> I think this is a good change/feature
>>>>
>> .
>>
>
>