Difference between revisions of "Design Team/Proposals/Journal"

From Sugar Labs
Jump to navigation Jump to search
 
(55 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
<noinclude>{{TOCright}}<!-- START OF BLOCK -- 1. COPY & PASTE this BLOCK to below the END OF BLOCK line.
+
__TOC__
−
                                  2. PASTE it before any pre-existing proposal,
+
== [[Journal NewUI]] ==
−
                                  3. then OVERWRITE the place holders with your information,
+
== [[Design Team/Proposals/Journal#Datastore|Datastore]] ==
−
                                  4. and DELETE the START & END OF BLOCK instruction lines.
+
<noinclude>
−
                                  5. Click [Show preview] to check formatting, and adjust as necessary.
+
* See Sascha Silbe's [http://git.sugarlabs.org/projects/versionsupport-project/repos/mainline version support project] specifically [http://git.sugarlabs.org/projects/versionsupport-project/repos/mainline/blobs/master/datastore-redesign.html datastore-redesign] (click the raw blob data link at the top of the page to see the HTML rendered in your browser), and this [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg06008.html mailing list thread], or this [http://docs.google.com/Doc?docid=0AbFyRSVE0dmOZGQ5emZjOTZfMzBoeG1qMjhqbg&hl=en compilation of the discussion] in context with the proposal document.
−
                                  6. Click [Save page] to complete the edit.
+
</noinclude>
−
                                                                                              -->
+
== [[Design Team/Proposals/Journal#Tags under titles|Tags under titles]] ==
−
===<Your proposal's pithy name here>===  <!-- Leave the === prefix and suffix ===
+
<noinclude>
−
                                                                                              -->
+
[[Image:journal_tag_mockup_frm_gary_v1.png|thumb|centre|640px|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.]]
−
:'''Rationale:'''                    <!-- leave this line -->
+
</noinclude>
−
:: <Your rationale here>
+
CSA: If you incorporate ordered tags, based on filesystem paths, they could look like this:
−
:'''Features:'''                    <!-- leave this line -->
+
[[Image:journal_tag_dir_styles.jpg|center|Tag styles]]
−
:# <1st feature here>
 
−
:# <2nd feature here>
 
−
:'''Implementation Details:'''      <!-- leave this line -->
 
−
:: <Details here>
 
−
:'''Reviewer Comments:'''            <!-- leave this line -->
 
−
:: comments here                <!-- reviewers: leave the :: prefix and overwrite up to this signature code: --~~~~
 
−
END OF BLOCK line --></noinclude>
 
−
<!-- Pre-existing Proposal Block -->
 
−
===Tags under Title===
 
−
====Mockups====
 
  
−
[[Image:journal_tag_mockup_frm_gary_v1.png|thumb|centre|640px|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.]]
+
== [[Design Team/Proposals/Journal/Toolbar and palettes | Toolbar and palettes]] ==
 +
<noinclude>
 +
See Gary Martin's mockups, such as this:
 +
[[Image:journal_mockup_gary_tags_gradient_palette.png|centre|640px|link=Design Team/Proposals/Journal/Toolbar and palettes|Tag fill colour is graduated from white to grey based on the tag frequency. Not sure we want to introduce a new 'colour' language but thought a mock-up would be worth it (though it's certainly the most visually clear indication of frequency given the space). Also works with white text and grey to black fill.]]
 +
</noinclude>
  
 +
== [[Design Team/Proposals/Journal#GMail-style tag view |GMail-style tag view]] ==
 
<noinclude>
 
<noinclude>
 +
Tags drag-and-drop-able from a left-side palette.
 +
[[Image:journal_mockup_cscott.png|thumb|center|640px|GMail-inspired Journal mockup.]]
 +
[[Image:journal_demo_cscott.png|thumb|center|640px|Journal2 demo]]
  
 
==Subpages==
 
==Subpages==
 
{{Special:PrefixIndex/{{PAGENAMEE}}/}}
 
{{Special:PrefixIndex/{{PAGENAMEE}}/}}
 
</noinclude>
 
</noinclude>

Latest revision as of 14:16, 27 October 2011

Journal NewUI

Datastore

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.

CSA: If you incorporate ordered tags, based on filesystem paths, they could look like this:

Tag styles

Toolbar and palettes

See Gary Martin's mockups, such as this:

Tag fill colour is graduated from white to grey based on the tag frequency. Not sure we want to introduce a new 'colour' language but thought a mock-up would be worth it (though it's certainly the most visually clear indication of frequency given the space). Also works with white text and grey to black fill.


GMail-style tag view

Tags drag-and-drop-able from a left-side palette.

GMail-inspired Journal mockup.
Journal2 demo

Subpages

Retrieved from "https://wiki.sugarlabs.org/index.php?title=Design_Team/Proposals/Journal&oldid=70298"