Am 11.03.2015 15:40:16, schrieb Adolfo Jayme Barrientos:
(You should know GDocs as you’re using it know makes me feel excluded.
Hopefully somebody will care)
How would you feel included? Of course your input is very appreciated.
About the mockups: It makes sense to start UI discussions from scratch. That means to figure out
what is the scope and which requirements are needed for the users. If you or someone else start
with a more or less final solution it not only hinders creativity (sorry for being a psychologist
;-) ) but we would discuss the proposal and miss features.
Some examples for the recent topic (all in terms of yes/no decisions based on good reasoning):
* Load and save from ftp, ssh, webdav, shared folders etc.* Integration of CMS into file dialog
* Live synchonization (at least we need to check on save if the original document was changed
meanwhile)
Just some brainstorming from my naiv view.
PS: (Phone call let Sophie slip in) We discussed whether or not to use Google and decided pro since
it is the most comfortable option. I'm fine with Etherpad too, for instance.
--
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.