Opened 10 years ago

Last modified 6 years ago

#652 new enhancement

Potential Journal Detail View improvements (Mock-up)

Reported by: garycmartin Owned by: eben
Priority: Unspecified by Maintainer Milestone:
Component: design Version: Unspecified
Severity: Unspecified Keywords: GPA
Cc: eben, cms Distribution/OS: Unspecified
Bug Status: New

Description

I've tried to come up with some small evolutionary, iterative design changes to the detail view to improve usage and usability. The main goal is to increase it's usefulness when looking back over Journal entries. Attached are 2 mock-up images, the first just shows the current main Journal view before the user has clicked on the entry titled "Screenshot"; the second image shows the new design for the Detail View. It includes:

1) The correct v shaped back icon, to match the one found on the right of the main Journal view.

2) Move of the back button to the far right edge, so than when clicking a detail button in the main Journal view you mouse is already over the button to get you back out again (behaviour is the same as current Back button). It also provides an easier mouse target as it's flush against the screen edge (Fitts Law).

3) The next Journal entry shown at the top of the view, just as it looks from the main Journal view (except for a grey background). It has no function other than to act as a Next button to move the Detail view to that entry.

4) The previous Journal entry shown at the bottom of the view, just as it looks from the main Journal view (except for a grey background). It has no function other than to act as a Previous button to move the Detail view to that entry.

5) Minor alignment of the thumbnail image with the other boxes, and addition of the work "Preview".

Clicking the Next/Previous areas allows navigation through the Journal entries in Detail view rather than having to hunt and peck, increasing the chance you can find what you're after and the likelihood of a user adding Description and Tag data.

FWIW: I'd rather this entry view ability was just part of the main Journal view, like an in-place fold-out, (and not another 'view' at all), but this at least seems a smaller step with less technical issues.

Attachments (2)

journal view.png (143.1 KB) - added by garycmartin 10 years ago.
Journal view prior to clicking on "Screenshot" entry
new details view.png (118.4 KB) - added by garycmartin 10 years ago.
New details view mock-up allowing entry navigation

Download all attachments as: .zip

Change History (7)

Changed 10 years ago by garycmartin

Journal view prior to clicking on "Screenshot" entry

Changed 10 years ago by garycmartin

New details view mock-up allowing entry navigation

comment:1 Changed 10 years ago by erikos

  • Bug Status changed from Unconfirmed to New
  • Component changed from sugar to design
  • Milestone changed from Unspecified by Release Team to 0.86
  • Owner changed from tomeu to eben

Here are some previous mockups from Eben - that are going into that direction: http://wiki.sugarlabs.org/go/Design_Team/Designs/Journal#02

comment:2 Changed 10 years ago by garycmartin

  • Cc cms added
  • Milestone changed from 0.86 to 0.88

Pushing to 0.88. This may be an approach to increase usage of the Journal detail view (as per discussions at yesterdays design meeting)

comment:3 Changed 10 years ago by gregorio

  • Keywords GPA added

Hi Guys,

I like it and I think this is an important area. I suggest that you look at refining the regular (aka not details) view as well.

Kids had trouble downloading an image fro Wikipedia via right click in Browse then finding that image again. I suggested we get a couple of images (states) at once then move them in to Memorize via journal, but it was hard to tell one download from another.

See: http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg06470.html

comment: - Weren't sure which item in journal was the state image they just downloaded.

Try that wikipedia download workflow as your design test case. If the details view makes it easy to tell one download from another, that's a step in the right direction, albeit an extra click.

Let me know if you need more input on why this was hard for kids.

Thanks,

Greg S

comment:4 Changed 9 years ago by walter

  • Milestone changed from 0.88 to 0.90

Seems we have consensus on this... just need to get the coding done. Maybe for 0.90

comment:5 Changed 6 years ago by dnarvaez

  • Milestone 0.90 deleted

Milestone 0.90 deleted

Note: See TracTickets for help on using tickets.