<div class="gmail_extra">2012/4/26 Tor Lillqvist <span dir="ltr"><<a href="mailto:tml@iki.fi" target="_blank">tml@iki.fi</a>></span><br><div class="gmail_quote"><div class="gmail_extra"><div class="gmail_quote"><div class="im"> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div>> Should there be a separate view mode, then, or would the viewing UI<br> > gradually develop into an editing UI?<br> <br> </div>I think there would be a separate viewer app (or apps) first, the<br> editing-capable ones would then be developed when the viewer<br> functionality starts getting good enough.<br></blockquote><div><br></div></div><div>Oh, a completely separate application, then.</div><div>If you opt for having a single LibreOffice application that would contain all modules (which is what I'd prefer personally, as I tend to group my ODF files by project, not by file type, and I'm a Google Docs user, which is also suited for that), would the first version of the editing-capable application contain only the modules that can edit files, or contain a mix of editing-capable and view-only modules?</div> <div>(I'd prefer the latter.)</div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div><br> >> We don't know for<br> >> instance whether it will make sense to combine handling of all three<br> >> document types (text, spreadsheet, presentation) into one app, or have<br> >> a separate one for each.<br> <br> > Will your decision depend largely on the technical difficulties posed by<br> > each option, or is this more of a UX problem?<br> <br> </div>Both. It might be, for instance, that an app to cover all three kinds<br> of documents brings in so much code that some real or apparent app<br> size limit is exceeded.</blockquote><div><br></div></div><div>I've seen some shots of LibreOffice running under Android (with the desktop UI and a colorful margin) -- was that the whole of LibreOffice running under Android, or just a small portion of the code?</div> <div>Also, how much code do the modules share? Will they share more code over time?</div><div>(I know Calligra Suite is very modular, LibreOffice apparently not so much.)</div><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> And, there are some very real technical<br> differences in how a viewer app can get the services it needs from the<br> lower layers of the code for the different kinds of documents.<br> <br> And then there is a question whether we have enough UX resources to do<br> a good design for all three document kinds, or should we concentrate<br> on one at a time?</blockquote><div><br></div></div><div>In my view, the UI for each module doesn't need to be so different as to require having a separate module for each.</div><div><br></div><div>I've done some brainstorming on how the current UI might be tweaked to get a tablet UI at <a href="http://wiki.documentfoundation.org/Design/Whiteboards/Tablet_Writer" target="_blank">http://wiki.documentfoundation.org/Design/Whiteboards/Tablet_Writer</a> and <a href="http://clickortap.wordpress.com/frivl/" target="_blank">http://clickortap.wordpress.com/frivl/</a>.</div> <div class="im"> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div><br> > Take a look at<br> > <a href="https://wiki.documentfoundation.org/Design/Whiteboards/File_Manager" target="_blank">https://wiki.documentfoundation.org/Design/Whiteboards/File_Manager</a> to get a<br> > better idea.<br> <br> </div>Thanks, I will.<br> <br> --tml<br> </blockquote></div></div></div> </div></div>