5,705
edits
Changes
Jump to navigation
Jump to search
Line 45:
Line 45: − − === 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. − − [[Image:-3.png|200px]] − − ==== Additional types of filters ==== − − For example Library [http://wiki.sugarlabs.org/go/File:-1.png 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). − − [[Image:-7.png|200px]] − − ==== 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). − − [[Image:-4.png|200px]]
→In additional
==== #4 ====
==== #4 ====
[[Image:journal_mockup_gary_list_palette.png|thumb|centre|640px|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.]]
[[Image:journal_mockup_gary_list_palette.png|thumb|centre|640px|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.]]
<noinclude>
<noinclude>