incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Grignon <kevingrignon...@gmail.com>
Subject Re: [UX] Symphony UI elements for AOO
Date Wed, 13 Jun 2012 05:40:24 GMT
KG02 - See additional comments inline.

On Thu, May 24, 2012 at 10:54 AM, Kevin Grignon
<kevingrignon.oo@gmail.com>wrote:

> KG01 - See comments inline.
>
> On Wed, May 23, 2012 at 8:17 PM, Graham Lauder <yo@apache.org> wrote:
>
>> > As one member of the team, I feel proud that people missed the mail
>> merge
>> > feature ^o*...although the code can't be applied to our code base, the
>> > design does. We can refer to the best from the design, and improve the
>> mail
>> > merge function here.
>>
>> Hi Helen
>>
>> Congratulations and well done, you and your team did an excellent job.
>>
>> There are some bits that it would be nice to work on.  Synching of address
>> labels for instance.  In the old OOo and it seems in Symphony, the address
>> labels were a completely separate document means extra work load for the
>> user.
>> It would be preferable to generate both letter and address label at the
>> same
>> time then at the Print dialog, be able to choose Print documents or Print
>> labels.
>>
>> >
>> > Besides mail merge & MDI, there are a lot of user experience
>> improvements
>> > across three editors in this contribution...for example, the sidebar is
>> in,
>> > which users can access most context properties easily; the clip-art
>> > gallery, has many newly designed pictures; numbering & bullet
>> enhancements,
>> > context menu, look & feel, ...some are bigger ones, but some are very
>> small
>> > items, but were driven by strong user needs or user study, so IMHO still
>> > very valuable for users.
>>
>> KG01 - Indeed, backed by solid user research and testing Symphony does
> have many user experience improvements that we could migrate to the AOO
> codebase. UX has been assessing the opportunities to merge or migrate
> aspects of the Symphony UX into AOO moving forward. Each offering has
> strengths, and each has room for improvement. We are fortunate to be able
> to harvest the best from each to deliver the best user experience for our
> users. UX team is analyzing the UX merge/migration opportunities. We will
> update the UX wiki to include our analysis and recommendations. As always
> we look forward to your input and feedback.
>

KG02 - I have started posting UX migration/merge analysis with specific
actionable recommendations to the AOO UX wiki [1]. All are welcome to
comment and contribute this ongoing analysis.

[1] http://wiki.services.openoffice.org/wiki/AOO_UX_Symphony_Contribution


>
>
>
>> It's too bad about the MDI, ironically the pre-SUN StarOffice had an MDI.
>> Very good it was too.   I do like the sidebar and the whole fresher
>> uncluttered look
>>
>> >
>> > These enhancements are spreading in many places (in code) across three
>> > editors. It would take quite some time to integrate. I would invite all
>> to
>> > have a look at the list, and discuss what you like, what we want to use
>> > here, and how to go forward...Looking forward to your thoughts. :-)
>> >
>>
>> Will do
>>
>
KG02 - See previous comment.


>
>> > Helen
>>
>> Cheers
>> GL
>>
>>
> KG01 - See comments inline.
>
> Regards,
> Kevkin
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message