<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Sans Serif'; font-size:10pt; font-weight:400; font-style:normal;">Let's make this a mockups thread :)))<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Yesterday I proposed another design (attached).<br>
Some notes about mockup:<br>
1. When deck has both front and back suites, both icons are available<br>
2. Decks which are "backside-only" are marked with some special (yet undecided) markup and have only "use as the backside" icon.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Parker had some nice ideas too - about having two GHNS-like listviews one next to another.<br>
(Parker, would you post them here, so others can review?)<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Yesterday we had some discussion on #kde-games.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I argued that showing two separate lists views for fronts and backs looks like an overkill to me - too complex interface, dialog gets too big.<br>
While Parker had a point that having both fronts and backs shown together would make it easier to compare them.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>it-s and Half-Left came up with their own ideas which were also presented in this thread.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Some more thoughts I have:<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>1. First of all i'd personally remove this "separate backs" feature as it really complicates not only UI, but user workflow too. Too much options to choose from IMO.<br>
2. If we leave this feature, I'd consider it a "power-user"-like feature and having it not necessarily available right from the start sound good. One more idea here is to have a dialog with tabs named "Frontsides" and "Backsides" each of which shows respective listview. This would allow to keep dialog compact and clean.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>On Tuesday 21 April 2009 02:28:31 Eugene Trounev wrote:<br>
> I would do it like this:<br>
> [attached]<br>
> Screen one - default view, screen two - once the deck is chosen.<br>
> If possible reuse the existing Dolphin views (that's what I used to produce<br>
> the mockup anyhow)<br>
> *Sorry about distorted images in selector, Dolphin squashes the images to<br>
> 64x64 for some reason :P<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p></body></html>