Harold Fuchs wrote:

I think there are several problems here:

1. The "prototype" was poorly done and, apparently, premature. This is a
shame and, unfortunately has coloured peoples' judgment - including mine. I
don't have any feelings about "ribbons". To be honest I'm not even sure what
the term means. But I certainly didn't like what I saw.

2. I don't think the "explanation" was particularly helpful. MS office's
"paper clip" helper  was supposed to be context sensitive ("You appear to be
writing a letter ..."). Philosophising about context sensitivity is not
productive. I don't believe Microsoft implemented the paper clip, presumably
after a lot of talking, deliberately to annoy millions of users. A UI can
really only be described by a significant [set of] prototype[s] or by
extensive use-case documentation which most of the interviewees you
mentioned and most of the people in this list won't read.

3. Change for change's sake is not a good maxim. IMHO the extensive changes
proposed are probably not a good idea. In my experience, major re-writes
cause more problems than they cure because they introduce new "bugs" and,
very frequently, re-introduce old ones. I'd much rather see evolution than
revolution. Fix the outstanding UI bugs and shortcomings; there are plenty
of them. If the UX team strongly feels it want to implement a completely new
style of UI then let that be an option. Microsoft got it right (yes, really)
when they introduced a whole new style to its Explorer/Control Panel/Start
Menu view but offered "classic view" as an alternative right there on the
"front page", not hidden or obfuscated.

Major changes, particularly to UIs, are very prone to cause major annoyance
and confusion among experienced users who are really not that interested in
the aesthetics but simply want to get the job done. They knew how to do the
job - warts and all - but now, suddenly, they don't. Having the new
interface as an option at least lets people learn the new things at their
own pace rather than having it forced upon them when they have a deadline to
meet. Who knows, they may even warm to the new interface if they can explore
it at leisure.

4. If there is to be a new UI then the developers need to be **a lot** more
responsive to bug-reports than they appear to be today. A new UI that
doesn't work in some major way or that removes/spoils existing functionality
could easily just kill OOo. Of course the death won't be sudden; it'll be a
wasting disease with users quietly disappearing.

I'm not anti change. I am anti trauma.



Hello Harold,

Well, there isn't much in there I can quibble with - there is a risk and I am sure everyone knows it.

But let me put it to you this way
- This same development team, pretty much, created the current package that you like, yes?

Actually by way of a small quibble - My experience has been that there can come a point in a code line's life cycle that the effort and risks involved in augmenting its functionality can match the risk posed by a whole hearted tear down and rebuild. Now I'm not a developer on this project and can't say if that is the case here or not, but I can say that the folks making these decisions are hardly armatures, and this is their code line. So, I don't know if that point is before them or not but I can say that it is often not quite as stark a choice as you make it sound.

As to your point about experienced users needing to learn over - it seems to me, and I hope the folks making the decisions give this some serious thought, that what success OpenOffice.org has had to date owes a certain amount "to the folks that would talk to the developers", the community in other words, and that they continue to take advantage of that very real resource.

Drew

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to