-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Viewer integration issues #7
Comments
May I ask a stupid question? Why is it important to have it integrated into the viewer? I understand that we get the sidebar for free which is nice. But on the other hand we loose the header bar which can be useful to navigate around, see other people in the same document, search, setting, ... |
We also aimed to have a more standardized way for apps to show file content. Before the viewer, each app needed to handle the overlay, styling and edgecases themselves, so just integrating in the viewer makes it a lot easier to maintain and the overall experience more consistent.
I agree that the header bar is useful here. Maybe we can have some different styling in the viewer for editing files, which could also be used by collabora/other file editors. Showing the header is something that is pretty straight forward with some basic styles: cc @skjnldsv |
Agree, but the nextcloud header bar should not be used for apps-customisations (like richdocuments for example) We can add the informations we want into the viewer header, which is already where we have infos, so it is better in a UX point of view. cc @jancborchardt
Well, if you click anything in the header, you'll quit the collaborative editing anyway as it will change the page. So I'd rather have the user make sure to quite the text app and navigate away than thinking it will not lose its current editing session and go into another app/setting section :) |
So basically, aside from the fileid prop, we should just add a config to force an independant view? I'd say, if the dev do not provide a |
Yes, I had the same in mind. 👍 |
Closed by nextcloud/viewer#79 |
All fixed already, thanks @skjnldsv |
There are some issues with the viewer integration:
The text was updated successfully, but these errors were encountered: