Re: [libreoffice-design] Re: LibreOffice Tablet Suite

Andrew,

2011/10/28 Charles-H. Schulz <charles.schulz@documentfoundation.org>

> Hello Andrew,
>
> 2011/10/28 Andrew Pullins <android2772@gmail.com>
>
> > HI,
> >
> > - We already explained that we cannot change the UI of LibreOffice all
> > >  of a sudden or as a whole, but that incremental improvements will be
> > >  the way to work. However, when it comes to a tablet interface, things
> > >  are different, as we do not expect to use the "LibreOffice
> > >  interface". The work that's currently being done by developers is to
> > >  port the system, the platform, the featureset if you will, but the
> > >  interface as it stands today would of course not be desirable. This
> > >  means that a new UI for tablets will be necessary, starting more or
> > >  less from scratch (I'm sure there will be constraints, etc.)
> >
> > we are starting from scratch here. yes the UI that Mirek has come up with
> > looks very much the same as his "Citrus UI" but that is the way it should
> > be(or at least if we decide to go with Citrus[which we should.])
> > of cores the interface that we have today would not be good on a tablet. I
> > have talked to a few people that USE pages on the ipad a lot at my church
> > to
> > make their sermons, and they have said that you can do too little in
> > pages.
> > they want more tools with the tablet suite. they also say that because of
> > this they make there documents on the computer with M$ word. so some of
> > the
> > curent UI should be put into the tablet suite.
>
> I think it would be very interesting to collect even more granular feedback
> on what they dislike with Pages from these people, do you think you could do
> that some time?
>
>
>
> > > - Designing an interface won't be everything. You can draw a beautiful
> > >  mock-up, but if the design/UX team does not translate it into
> > >  specification(s) it will remain a nice mock-up. Developers do not
> > >  know what to do with a mock-up, it can only be an illustration that
> > >  gives a general impression.
> >
> > what kind of specifications, from what Mirek and I have done so far what
> > do
> > the developers need to make it work? from what I have done it it I can see
> > only one or two things that would need more explaining, which would be
> > that
> > when typing the document the contextbar and maybe the top bar would hide
> > and
> > when press the bar that remains it would reaper.
>
>
> Oh... We are very, very far from even 20% of the job of a specification
> here. Here's a link that I found on a blog, it does not give you the precise
> manual to write a specification, but it gives you at least an idea of what a
> specification should contain:
>
> http://boadweelaw.com/blog/2007/02/15/how-to-draft-a-specification-or-requirements-document-for-a-contract/
>
> As you can see it's a full document that's needed, it describes very
> precisely each interaction of the UI. By the way, since what is needed is
> -at least for LibreOffice on the desktop- only one or two UX feature at a
> time, the document does not need to be overly complex and long, but you
> still need to have a specification describing everything, the layout,
> aspect, behaviour, intended goal of the feature, dependency,etc.
>
> Christoph, do you happen to have a specification template?

As it happened, Christoph just wrote one!

http://wiki.documentfoundation.org/Design/Whiteboard/Writer_SpecialIndicators#Document_Margin_Design


Hope this helps,

Charles.

-- 
Unsubscribe instructions: E-mail to design+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/design/
All messages sent to this list will be publicly archived and cannot be deleted