Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


2014/1/19 Regina Henschel <rb.henschel@t-online.de>

Hi Mirek,

Mirek M. schrieb:

Hi Regina,


2014/1/19 Regina Henschel <rb.henschel@t-online.de>

 Hi Mirek,

Mirek M. schrieb:

 Hi Regina,

2014/1/19 Regina Henschel <rb.henschel@t-online.de>

  Hi Mirek,


Mirek M. schrieb:

   Hi guys,

 In order to be able to effectively design and shape the future of
LibreOffice modules, it is imperative that we define what these
modules
are
for. Knowing the purpose of each module will help us focus on doing
one
thing well and avoid counterproductive feature creep.

Since, out of all the modules, Impress's purpose might be one of the
clearest, let's start with it.

My rough draft:
The purpose of Impress is "to make it simple and quick to craft a
slide
show to perfectly complement a speech."
Please comment on this.

   "complement a speech" is not all. There exists other popular
usages of

 impress. For example:
(1) Self-repeating (product-) information, for example in shop window,
waiting room, or station.
(2) Interactive learning arrangement
(3) Present pictures from travel or festivals to friends or
parishioners
(4) Background for memorial or meditation
(5) Lecture notes for revision


 Yes, but it's important design practice to focus on doing one thing
excellently, not on doing several things in a mediocre way.
That doesn't mean Impress can't or shouldn't be used for other things,
but
that it should be optimized to do one thing well. Alternative use-cases
can
be covered unintentionally, by extensions, or by splitting the module
into
two.


I disagree here. Look at the questions about impress in mailing lists and
forums. For example, why do you think users ask about a sound continuing
over the whole slide show? Surely not for "complement a speech", but
likely
for purpose (3).


Again, I'm not asking what the software is being used for. I'm asking what
use-cases it should be designed for.
For example, if we say that the purpose of Impress is creating photo
slideshows, then maybe we should show the Photo Album dialog at launch.
If, on the other hand, we say that creating photo slideshows is not at all
relevant to the purpose, we should think about spinning the Photo Album
dialog into an extension.


I would not keep the question on design-list, but bring it to
discuss-list
too.


Real-life examples of each of these:
LibreOffice Writer wasn't designed for editing code. You may use it for
that purpose, though. (You definitely shouldn't, there are much, much
better tools for the job, but it is possible.) The same goes for using
Impress for a picture slideshow -- there are better tools for the job,
and
that's because those tools were designed specifically for that job.


I think, that many users do not install special applications, but use the
tools they know. LO is not only used in enterprises and large
administration, but in non-profit organizations like religious
communities
and friendly societies, small business, and in education.


The huge popularity of single-purpose mobile apps proves otherwise. These
are popular because they're simple and tailored to a single use case.


But "single-purpose" is a radical change of paradigm. Therefore the focus
on design mailing list is too small.


It's another guideline to go by when designing. Not unlike the guidelines
at https://wiki.documentfoundation.org/Design/Guidelines or the principles
at https://wiki.documentfoundation.org/Design/Principles.

Also, it shouldn't be a radical change of paradigm. Impress has generally
been tailored toward complementing presentations and features like the
Photo Album came as an afterthought. That's why the Photo Album dialog
doesn't appear at launch, that's why the slide sorter is linear rather than
spatial, as it should be if Impress was tailored for interactive
presentations, that's why slide advancement isn't automatic by default and
why slide advancement options aren't emphasized, as they would be if
Impress was tailored for autoplaying presentations.

Kind regards
Regina


--
To unsubscribe e-mail to: design+unsubscribe@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


-- 
To unsubscribe e-mail to: design+unsubscribe@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

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.