| Thanks for writing these up Priss, there are a bunch of good issues in here that we need to tackle in the Beta timeframe... On Sep 11, 2006, at 10:10 AM, Priscilla Chung wrote: This is collection of random notes from July till early September 2006. Please note I tried to put some of the more recent activity at the top of my notes. I started with comments from a more recent build. The most recent build I have now is dated on 9/10/06 0.7 Alpha 4. It should be Triage status. But there are a couple of other issues. e.g. + Should we preserve sort order as you navigate across App Areas? That depends... - When you go from All to Tasks, are you filtering down All to just look at Tasks? in which case you'd want to preserve Sort order. - Or are you switching modes? e.g. I was Processing new stuff that was coming in (Sort by Triage Status). Now I'm going to Review my tasks (Sort by Tickler Date). + We should probably preserve sort order on a per collection basis. - It's consistent with how Folders work in Email clients - I think you are more likely to be switching modes when you switch collections, because you are completely changing the data set that you are looking at. Whereas when you switch App areas, you are working within the same pool of data, but just expanding and narrowing what you see. - Of course, this changes if we have Overlays in the Summary Table View. I think if you have overlays, you don't want Sort Order to change as you switch collections, because the 'data that you see' doesn't change. - However when you switch between the user-defined area and the Out of the Box area, you are essentially swapping data sets (since overlays get temporarily de-activated), so sort order should probably change to be whatever it was the last time your were in the IN collection or the DASHBOARD collection or the TRASH collection. So the general rule is: If you're working within the same set of data, then sort order should stay the same. However, if 1 data set is essentially being swapped out for another, then sort order can change. This is something we should probably just implement 1 way and see how it feels. I will log these as bugs.
Yeah, I've played around with the idea that when you select an item, something appears to show you that there's a widget in that column. Or having a widget appear when you mouseover the row, rather than just the cell, the way we do it in the sidebar with the collection overlay icon. It's a hard balancing act between making the widget discoverable and creating a lot of repetitive visual noise in the table. I will log a bug with a couple of these suggestions.
Yeah I think that's not a convention non-technical people will understand. What if we had: osaf.us/your_username instead? It's hard for us to grey out the text. So we need to make it clear that the field hasn't been filled out for you already.
I believe that is part of the Keyboard support wiki write-up: http://wiki.osafoundation.org/bin/view/Journal/AEBehavior3320
|
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
