[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Suggestions for usability improvements
From:       Thomas Pfeiffer <colomar () autistici ! org>
Date:       2009-12-16 20:14:03
Message-ID: 200912162114.03756.colomar () autistici ! org
[Download RAW message or body]

> On Tuesday 15. December 2009 23.54.09 Thomas Pfeiffer wrote:
> > Yes, exactly. Thanks for clarifying the point. The goal should be to
> > unify the  interface throughout the suite as much as possible while still
> > straying from the unified interface in a particular app as much as
> > necessary to ensure it's appropriateness for the task.
> 
> I like this.
> 
> I recently had an interaction designer student ask me about KOffice, and I
>  had several long discussions (some hours each) about the design, the tools
>  system and the philosophy koffice follows.
> 
> The fact that it took so much time is basically because its an approach
>  that is straying out of the normal ways of working.
> 
As I wrote before, I really like the fact that you are trying new things. 
After all, that's one of the big advantages of community projects: You can try 
things out without having to fear losses in sales. And I'm glad you took that 
opportunity. 

> I mirror what I read into Boudewijns words of caution that this stuff is
>  pretty weird and that its essential to understand where we (the KOffice
>  guys) want to go in order to steer us through the usability minefield
>  while not straying too far back into known territory.
> 
I especially like that last sentence. "Steering you through the usability 
minefield" in the unknown territory sounds like a pretty interesting task ;) I 
don't think "known territory" is generally a bad thing, though. There are 
concepts that just work well and you shouldn't turn your backs on them just 
because they are known. But returning to known things just because of fear of 
the unknown isn't good, either, of course.
I think freeing oneself from the usual ways to focus on what works best no 
matter if it's know or old would be the most promising way.
I'm confident that we can find ways to improve aspects of KOffice without 
conflicting with the team's vision and philosophy.

Regards,
Thomas
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]