On Dec 10, 2007 4:33 PM, Mimi Yin <[EMAIL PROTECTED]> wrote: > Hi, > > Just to clarify: There is no design argument against separating > application areas and views. It's more a matter of implementing the > UI elements needed to do this in a way that doesn't visually > overwhelm the interface. (Something we're already struggling with.)
Indeed this is always a struggle. But the number one issue is understanding the data model. I do believe it is possible to fix this issue without overwhelming. Indeed some of the things you have already suggested, like removing all those mail icons, helps enormously. My suggestions help lighten the menu bar - which will be lighter anyway without the utility menus. > The decision to combine app areas + filter functionality boiled down > to prioritization. (In the Chandler Hub UI, we have a different take > on this problem. We *only* have views, no application areas.) We > should revisit this issue in the context of our post 1.0 plans. > I don't have any insight into what the difficulties are in making various changes or your roadmap plans. But in my view, the way that views currently work is so confusing that I think you will loose well more than 50% of your potential users because they do not understand. I say that only because, after spending many hours over the weekend with the software I am still not entirely clear how the views and filtering works. And I figure if that is the case with me, casual users will, for the most part, give up. I therefore suggest that this issue be a priority for 1.0 because, as humbly as I can suggest this, if I am confused, precious few will not be. You are so close to something that really is a friendly piece of software. I'd just love to see you guys make it over the usability finish line. Hank _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
