Design Team/Proposals/Journal

<Your proposal's pithy name here>

Rationale:

<Your rationale here>

Features:

1. <1st feature here>
2. <2nd feature here>

Implementation Details:

<Details here>

Reviewer Comments:

comments here

Tags under titles

Example mock-up based on current Journal (0.84) using two lines for title and tags per each entry. Notes: Entries with no tags have their title vertically centred to keep visual balance; entries with more tags than can be displayed end with an ellipsis, this could just be indicative that there are more tags, or have hover hint function showing the remaining un-displayed tags. Clicking a tag should add it to the search field to allow drilling down into results.

Tollbar and palettes

TODO:

• Mock-up of tag palette (before alstoot starts throwing heavy objects at me).
• Add and mock-up an anytime/when palette.
• Add and mock-up an anyone/who palette.
• Try and find better design for the anything/what filter/funnel icon.
• Show multi entry selection and applying actions to them
  • shift key modifier and click to multi select (toggle, or could be block range)
  • modified pop-up palette when interacting with multi selected items

#1

Toolbar rework using standard button icons instead of text menus (the Activity filter icon is a temporary design placeholder, suggestions welcome!)

#2

Example using a palette with a grid layout to show many items on screen at once and reduce scrolling (Activity filter icon is a temporary design placeholder, suggestions welcome!) Clicking on an item will highlight it (as shown on the default 'Anything' icon) and place it's icon in the toolbar.

#3

Grid palette, not much here to see, other than to note that Grid view has been placed as a top level toolbar button as it's likely a frequent view to be switched to and from (grid view is inherently an object-view).

#4

List palette, Journal Grid view and List view are (I think) the primary views users will switch between, so I've swapped around the design priority from Eben so that (potential future) action-view and object-view are secondary items for the List view. Once/if action-view is implemented/proven it would likely be the default List view.

In additional

Compact list view

The purpose is, if user has lots of objects it could be useful idea to show as much as possible objects on one screen.

Having several column/grid layouts for example its very useful for books to have columns for author, genre, date; so, user can see the whole valuable info at once and sort objects by these columns; and so separate layouts for video audio etc. files.

Additional types of filters

For example Library has several types to filter objects

• user tags
• object traits(additional columns from previous section) like author, genre, date for books
• activity creators(grouping by activity_id field)
• types of objects(like top section in filter palette)[3]
• filter by participants
• filter by sources(if we are in shared mode)

Its not clear that all of these modes are useful, but something could be(or another types).

Several levels of chosen filters

In some cases it could be useful. For example user can filter all text/plane files and separate from them only objects that were made by Terminal activity. In that case there should UI element to show currently chosen filters(see bottom panel on below page).

Subpages

• Design Team/Proposals/Journal/Toolbar and palettes