[Digikam-devel] "Apply" button in right side bar

[Marcel Wiesweg]

Hi,

there were some complaints about the Apply button in the Comments/Tags
sidebar. These included:
- users assume that the changes are applied only if the button is pressed, and
not as well when moving to the next image
- when editing multiple pictures, inadvertent changes can easily affect many
pictures. So here it is even more important to make clear when changes are
applied.

I would like to add that implementing an undo feature is not trivial.

My suggestions:

1) Single selection
Changes are applied immediately, visible after each keystroke in main view.
(Only database, DMetadata is slow, update still only on selection change)
The Apply button is not needed.

2) Multiple selection
At the very first change, the user is asked if he wants to auto-apply changes
in multiple selection. This option can be changed from the menu on the "More"
button.
        a) Auto-apply
                Changes are applied on selection change
        b) No auto-apply
                The "Apply" button is shown. Changes are applied
                only if the button is pressed.
                On selection change with changes, a message box
                asks if changes shall be applied.

Please tell me if this is an improvement to the current situation:
usability-wise, for "educating" new users, and acceptable for power users.
Or if the current situtation is all right.
Or give other suggestions.

Marcel
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-2]

Le Samedi 20 Janvier 2007 21:15, Marcel Wiesweg a écrit :

> Hi,
>
> there were some complaints about the Apply button in the Comments/Tags
> sidebar. These included:
> - users assume that the changes are applied only if the button is pressed,
> and not as well when moving to the next image
> - when editing multiple pictures, inadvertent changes can easily affect
> many pictures. So here it is even more important to make clear when changes
> are applied.
>
> I would like to add that implementing an undo feature is not trivial.

agree.

>
> My suggestions:
>
> 1) Single selection
> Changes are applied immediately, visible after each keystroke in main view.
> (Only database, DMetadata is slow, update still only on selection change)
> The Apply button is not needed.

Warning, i have add the Apply button because some user have ping me because
the behaviours is obscur with Comments & Tags.

Of course, for me, without Apply button is fine, but i'm programmer (:=)))...
User viewpoint can be different.

>
> 2) Multiple selection
> At the very first change, the user is asked if he wants to auto-apply
> changes in multiple selection. This option can be changed from the menu on
> the "More" button.
> a) Auto-apply
> Changes are applied on selection change
> b) No auto-apply
> The "Apply" button is shown. Changes are applied
> only if the button is pressed.
> On selection change with changes, a message box
> asks if changes shall be applied.

b) This is fine for me .The message box can have a 'Do not ask this warning to
the future..." checkbox.

The Usability is stuff can be difficult to judge. I recomend you to have more
feedback using user mailing list if there is more message in this thread.

Other tip is to wait the first beta1 when a first feedback will come.

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

> > My suggestions:
> >
> > 1) Single selection
> > Changes are applied immediately, visible after each keystroke in main
> > view. (Only database, DMetadata is slow, update still only on selection
> > change) The Apply button is not needed.
>
> Warning, i have add the Apply button because some user have ping me because
> the behaviours is obscur with Comments & Tags.
>
> Of course, for me, without Apply button is fine, but i'm programmer
> (:=)))... User viewpoint can be different.

Yes, I'm not sure what users expect.

>
> > 2) Multiple selection
> > At the very first change, the user is asked if he wants to auto-apply
> > changes in multiple selection. This option can be changed from the menu
> > on the "More" button.
> > a) Auto-apply
> > Changes are applied on selection change
> > b) No auto-apply
> > The "Apply" button is shown. Changes are applied
> > only if the button is pressed.
> > On selection change with changes, a message box
> > asks if changes shall be applied.
>
> b) This is fine for me .The message box can have a 'Do not ask this warning
> to the future..." checkbox.
>
> The Usability is stuff can be difficult to judge.

Yes. That's why I prefer to ask the list before ;-)

> I recomend you to have
> more feedback using user mailing list if there is more message in this
> thread.

I have sent the mail to digikam-user as well.

>
> Other tip is to wait the first beta1 when a first feedback will come.
>
> Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gerhard Kulzer]

Am Sonntag, 21. Januar 2007 22:20 schrieb Marcel Wiesweg:

> > > My suggestions:
> > >
> > > 1) Single selection
> > > Changes are applied immediately, visible after each keystroke in main
> > > view. (Only database, DMetadata is slow, update still only on selection
> > > change) The Apply button is not needed.
> >
> > Warning, i have add the Apply button because some user have ping me
> > because the behaviours is obscur with Comments & Tags.
> >
> > Of course, for me, without Apply button is fine, but i'm programmer
> > (:=)))... User viewpoint can be different.
>
> Yes, I'm not sure what users expect.

I just read an article about useability; it seems that 5 user opinions are
enough to get sufficiently precise feedback.

Ok I try to be a normal user:
The 'apply' button is disturbing if you haven't followed the historical
development. I think the best solution is to apply changes straight away as
Marcel suggest. Maybe after each keystroke is a bit busy but update every
second should be fine.

> > > 2) Multiple selection
> > > At the very first change, the user is asked if he wants to auto-apply
> > > changes in multiple selection. This option can be changed from the menu
> > > on the "More" button.
> > > a) Auto-apply
> > > Changes are applied on selection change
> > > b) No auto-apply
> > > The "Apply" button is shown. Changes are applied
> > > only if the button is pressed.
> > > On selection change with changes, a message box
> > > asks if changes shall be applied.
> >
> > b) This is fine for me .The message box can have a 'Do not ask this
> > warning to the future..." checkbox.
> >
> > The Usability is stuff can be difficult to judge.
>
> Yes. That's why I prefer to ask the list before ;-)
>
> > I recomend you to have
> > more feedback using user mailing list if there is more message in this
> > thread.
>
> I have sent the mail to digikam-user as well.
>
> > Other tip is to wait the first beta1 when a first feedback will come.
> >
> > Gilles
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

--
http://www.gerhard.fr
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[krienke]

Am Montag, 22. Januar 2007 09:40 schrieb Gerhard Kulzer:

>
> I just read an article about useability; it seems that 5 user opinions are
> enough to get sufficiently precise feedback.
>
> Ok I try to be a normal user:
> The 'apply' button is disturbing if you haven't followed the historical
> development. I think the best solution is to apply changes straight away as
> Marcel suggest. Maybe after each keystroke is a bit busy but update every
> second should be fine.
>

Ok, perhaps I am number 5 :-)  
I think an apply button makes sense especially because useability. Not having
an apply button I always asked myself when are the changes really applied.
What if I add another tag to an photo and then immedeately close digikam.
Will the changes be applied? I was unsure.

Not having an apply button simlpy leaves the user in the dark not knowing what
will happen when.  Thats why I would vote for an apply button like solution
b) in the last posting suggested. Next I would offer the user an option so he
can switch over to auto apply telling the user when exactly changes are
applied. In this case the user knows what happens since he himself made the
decision.

Perhaps one could add a checkbox near the apply button to
enable/disable  "autoapply" graying out the apply button when checked.
Tooltips could inform the user what exactly this means.  The checkbox could
of course also be put into the option setup dialog instead of the tag dialog.

Have a nice day
Rainer
--
---------------------------------------------------------------------------
Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022
Universitaetsstrasse 1, 56070 Koblenz, Tel: [phone], Fax: -1001312
Mail: [hidden email], Web: http://www.uni-koblenz.de/~krienke
Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html
---------------------------------------------------------------------------

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel