-
Notifications
You must be signed in to change notification settings - Fork 1
Evaluate Switch between classic frontend and ocis-web #227
Description
- Add a switch between frontends using navigation items (app launcher)
- Improve wording and icons for the switches
- Links (private/public) should redirect to the ocis-web UI
Documentation
-> decide where to put it
Motivation / abstract
We want to let users switch between classic and new design as easy as possible. For this both classic and new frontend need their own URL (can be relative urls).
Configure oc10
As soon as phoenix is configured in oc10, a menu item becomes available in the app switcher. By default it shows an icon with a browser window and arrows to the left and right and New Design as label. Both the icon and the label can be configured by setting phoenix.icon (absolute or relative URL to an svg file) and phoenix.label (text of your choice) respectively.
Configure phoenix
By default there is no link back to the oc10 frontend. However, you can add an application item in your config.json file like this:
"applications": [
{
"title": {
"en": "Classic Design",
},
"icon": "switch_ui",
"url": "https://url-of-your-oc10-instance",
"target": "_self"
}
]
- The icon can be picked from ownCloud design system icons by name or as an absolute URL.
- the URL needs to point to your ownCloud 10 instance
- If you don't provide
_selfas a target (for opening the url in the same tab/window), it will be opened in a new tab/window by default.
You can add more items to the applications list (e.g. directly to any oc10 app) if needed. Native phoenix apps will be first in the app switcher, while items from the applications list will be the last items in the app switcher.