After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 596999 - "Reprise" functionality
"Reprise" functionality
Status: RESOLVED FIXED
Product: hamster-applet
Classification: Deprecated
Component: usability
2.28.x
Other Linux
: Normal enhancement
: ---
Assigned To: hamster-applet-maint
hamster-applet-maint
: 602295 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-10-01 15:08 UTC by Mac Ryan
Modified: 2010-01-18 12:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mac Ryan 2009-10-01 15:08:30 UTC
Very often it happens (at least to me) that in the middle of a development session (development@work,django module for special offer products - backporting to v.1.1) I receive a call from a customer with a urgent need. 

I therefore stop the development session and get a new task (support@work,Jimmy dropped the DB table by mistake).

As soon as the urgent need is done, I am back to the original task I was doing prior to be interrupted, and thus I have to re-insert "django module for special offer products - backporting to v.1.1", which is a bit of annoyance.

I would therefore suggest a button to "reprise" a previously interrupted task (i.e.: to create a new record with the same category, activity and description of a previous one). The more natural place to put such button (IMO) is on the right side of the list of completed tasks for the day, next to the button that allows to edit that record [I am referring to the window opening when you click on the applet]

BTW: After a few days of 2.29.1 I can't really imagine to get back to 2.26. This new version rocks! :)
Comment 1 Mac Ryan 2009-10-11 12:42:41 UTC
Just discovered by accident that this functionality is already there. One has to doubleclick on the task of the day they want to "reprise", and the task will start over a second/third/fourth... time.

I think hamster applet would need some work on the documentation side. How can I help?
Comment 2 Toms Bauģis 2009-10-11 12:44:45 UTC
if you feel strong on the literar side, you could try to write a manual. 

i don't think there is need for documentation though, instead the interface should be maybe hinting better.
Comment 3 Mac Ryan 2009-10-11 14:02:11 UTC
A manual is maybe overshooting, while an interface without the need of additional information would be the perfect one, of course.

I was thinking that maybe having a "tip box" popping up at every start of the applet (of course one could disable it) with some interesting advice, could help users to discover the full power of the critter, thoug! :)

Example: "Did you know you can export your data in CSV? Just go to ... and click..."

Then one would have the button "next tip" "previous tip" "close" and the checkbox "don't show me this window anymore".

Just an idea... :)
Comment 4 Toms Bauģis 2009-10-11 17:18:38 UTC
actually you might be right and we could use some documentation. the startup tips is a bit of overkill, i wonder if we can come up with something more unobtrusive
Comment 5 Mac Ryan 2009-10-11 19:28:45 UTC
If you have an idea of the format and T.O.C. for the documentation just share it. I feel you are kind of the project leader here, so I am totally happy to contribute starting from your input and elaborating together from there [at the end of the day if I really dislike the proposal I can all the time say... no, thanks!] ;)

English is not my first language and most probably my writing will need some kind of review, but I am happy to begin to write some, if you like. (Will take at least a couple of weeks to start, though, as I'm in a middle of a series of project deliveries... :-/
Comment 6 Toms Bauģis 2009-11-18 12:24:51 UTC
*** Bug 602295 has been marked as a duplicate of this bug. ***
Comment 7 Toms Bauģis 2010-01-18 12:00:45 UTC
reprise can now be solved with help of virtual desktops. 
i think this is how far we go.

Mac - as for the documentation - coming up with an outline (thus figuring out what's there to document) is half of the documentation job. Since I don't know your writing style nor your capabilities, i can't guarantee that your contribution will be included in hamster, but i encourage you to give it a try. Results should go in separate bug.