Bugzilla – Full Text Bug Listing
| Summary: | [client] page layout and visual styling for 0.4 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Susan McCourt <susan> | ||||
| Component: | Client | Assignee: | Susan McCourt <susan> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | antonm, john.arthorne, johnjbarton, lindawat, Silenio_Quarti, simon_kaegi | ||||
| Version: | 0.2 | ||||||
| Target Milestone: | 0.4 M2 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Susan McCourt
need to revisit this list during 0.4 work generalizing this title. We are looking for a "fresh coat of paint" for 0.4, so we want to take a step back and freshen up the common page elements (banner, etc.) first before drilling in on these details. other points to consider: - visual affordance for toggling the banner out of view (or should we design a reduced banner that would still have the breadcrumb, etc.) - mobile friendliness In bug 363740 we talked about making the search box wider, to show scoping information. Consider this when we redo layouts. general discussion of new styling for 0.4: http://wiki.eclipse.org/Orion/Page_Layout (In reply to comment #4) > general discussion of new styling for 0.4: > > http://wiki.eclipse.org/Orion/Page_Layout The ken missing item for me might be called "Context sensitive navigation". On the edit page for foo.js I want the git status link for the project foo.js lives in; on the git status page I want the navigation link for the project. The multi-file copy/move UI is obscure. First you have to know the click the box on a file, then notice a new menu, mouse to it, then it almost never has the dest folder list, you have to use the tedious dialog version. (In reply to comment #5) > (In reply to comment #4) > > general discussion of new styling for 0.4: > > > > http://wiki.eclipse.org/Orion/Page_Layout > > The ken missing item for me might be called "Context sensitive navigation". On > the edit page for foo.js I want the git status link for the project foo.js > lives in; on the git status page I want the navigation link for the project. Thanks, John. I agree this is very important, but I feel like we covered this (mentioning those examples and bugs) in "Links to related pages" and "Related task Links". (In reply to comment #6) > The multi-file copy/move UI is obscure. First you have to know the click the > box on a file, then notice a new menu, mouse to it, then it almost never has > the dest folder list, you have to use the tedious dialog version. Agree. making move/copy locally available (next to the item) used to perform too badly, but I've since fixed that problem. Opened bug 365463 to look at it again. There's also drag/drop (bug 339144) but no one is working on it. (In reply to comment #7) > Thanks, John. I agree this is very important, but I feel like we covered this > (mentioning those examples and bugs) in "Links to related pages" and "Related > task Links". Yes, sorry I read the top of the page as "plan" not realizing it was "old" and "plan" was further down. (In reply to comment #8) > (In reply to comment #7) > > > Thanks, John. I agree this is very important, but I feel like we covered this > > (mentioning those examples and bugs) in "Links to related pages" and "Related > > task Links". > > Yes, sorry I read the top of the page as "plan" not realizing it was "old" and > "plan" was further down. I moved the historical stuff to its own document. The wiki now focuses on what we plan to do. Also blogged about it http://adventuresinthoughtlessness.blogspot.com/2012/01/anatomy-of-orion-page.html I believe I am running I20120108-2230 I still think that Navigate-this-project is a top level operation on a Git repo, more so than Git Log (which should be a toolbar option from Git Status IMO). I like the less gray UI (thanks!) but now I feel that the visuals are dominated by the rectangular menu icons. Created attachment 210135 [details]
mockup from 1/25/2012
per the Orion call, here is the latest screenshot of designer mockups. I'm trying to get closer to this for M2 (darker banner, flatter toolbar and slideout, etc.).
This will continue to change, and we have not yet drilled down on command rendering inside pages (icon vs. button vs. links).
Another disclaimer is that this mockup makes no sense from a content point of view, it's attempting to show the visuals for everything in one page.
pushed the first set of changes that go with the mockup. Still work to do on section headings, etc. But this gets the basics working with respect to dark top, toolbars matching their interior panes, etc. Marking fixed. I've committed the last of the structural changes for the mockup, moving the progress, status, and notification messages out of the footer and into a sliding area under the tools. There will still be visual tweaks on colors, spacing, etc. but I'll track these in other bugs. The biggest piece not done is surrounding headers, commands, etc. and that is covered in bug 360986 |