Bug 137176 - LibreOffice Online Layout best fit into NC
Summary: LibreOffice Online Layout best fit into NC
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice Online
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-01 09:00 UTC by andreas_k
Modified: 2020-11-12 08:27 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
LibreOffice Online Layout (213.07 KB, image/png)
2020-10-01 09:00 UTC, andreas_k
Details
Markdown Editor Layout in Nextcloud (169.22 KB, image/png)
2020-10-01 09:05 UTC, andreas_k
Details

Note You need to log in before you can comment on or make changes to this bug.
Description andreas_k 2020-10-01 09:00:41 UTC
Created attachment 165995 [details]
LibreOffice Online Layout

Tabbed UI are interested, but didn't fit perfect into Online Storages (like NextCloud).

My idea is to have a similar layout as the inbuild Markdown editor of Nextcloud + the LibreOffice sidebar.

Nextcloud has ordinary the main section and for details stuff an sidebar/panel. The idea is that LOOL follow the same approach (I would like to use this approach also for LibO, that's the reason I work on the sidebar).

LibreOffice layout mockup
- menubar where in the markdown editor the filename is.
- one toolbar where you have commands that are not available with the sidebar (default toolbar stuff from LibO)
- sidebar open by default where you have all the contextual commands for formating, image, ...
Comment 1 andreas_k 2020-10-01 09:05:14 UTC
Created attachment 165996 [details]
Markdown Editor Layout in Nextcloud

if you compare the mardkown editor layout and the proposed LOOL layout you will see that LOOL has a menubar and an aditional sidebar.

The toolbar should has the commands that are not available via sidebar OR are needed for view the document and add comments, ... so for view and review process sidebar isn't needed.

For edit an document you have the sidebar. 95 % of the commands from contextual toolbars are available in the sidebar. In addition the sidebar should reduce the usecase of dialogues.

when you have a look at the first attachment you see that instead of the right align tabbar I prefer an top align tabbar (similar to what NC use).
Comment 2 andreas_k 2020-10-01 09:09:56 UTC
If you think, that LOOL will look to simple, check the menubar release of LOOL. All commands from the toolbar are available. Some are now available only in the sidebar, but now the usecase of the sidebar is much cleaner.

An additional benefit will be that LOOL and LibO will be different, but can look very similar so if user use LOOL and LibO there is no workflow issue.
Comment 3 andreas_k 2020-10-01 09:14:57 UTC
If you say, but the sidebar is not sexy enough, true, but than make it more sexy. I don't know how the Android viewer pharse the commands from the sidebar but it did. In addition for iOS LibO get an theme egine, maybe it will work for LOOL?

Now LOOL show the sidebar, so there will be no difference to now, the only difference will be that the proposed layout is simple, fit the UX guidelines of Nextcloud better and as you use the sidebar, you don't have to reimplement all the context related toolbars, ... less work with better solution.
Comment 4 Michael Meeks 2020-10-01 13:04:28 UTC
Interesting idea  =) To confirm - you want a simplified toolbar, and to move the menu in Nextcloud up over the header ?

If you fire up online and play with F12 in the browser - you can see how the iframe interacts with the Nextcloud surround; unfortunately it's really tough to get much outside the iframe - so possibly we'd need to do our own surround - but then the PHP/JS code re-use is harder; so a bit tricky.

Any ideas for things inside the frame ? (and do have a poke at it).
Comment 5 Xisco Faulí 2020-11-11 14:59:24 UTC
Hi Andreas Kainz,
Please, provide feedback to comment 4
Comment 6 Aron Budea 2020-11-11 16:20:11 UTC
The following GitHub issue has further discussion on the topic:
https://github.com/CollaboraOnline/online/issues/55
Comment 7 andreas_k 2020-11-12 08:27:56 UTC
discussion in on https://github.com/CollaboraOnline/online/issues/55