Feature Wiki

Information about planned and released features

Tabs

streamlining cloud object ui

1 Initial Problem

Currently the content page of a cloud object has its own toolbar. It contains a breadcrump and the "Add new item" button.

2 Conceptual Summary

The content of a cloud object should behave like container objects in ILIAS. For the user it is just another knot in the tree.

3 User Interface Modifications

3.1 List of Affected Views

  • cloud object content view

3.2 User Interface Details

  1. The "Add new item" button shoud have the same position as in every container object.
  2. The cloud object breadcrump shoud extend the ILIAS breadcrump.
  3. If the user browses into a folder inside the cloud object, the icon should switch to the cloud folder icon.
  4. If the user browses into a folder inside the cloud object, the headline should show the folder name.

3.3 New User Interface Concepts

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

7 Discussion

Schmid, Fabian [fschmid] 03.10.2017: In general I fully support the streamlining of the Cloud-Object to the other locations in ILIAS which provide containers and items in it. Currently the cloud object is implemented client-side due to performance issues: every pageload would lead to many request to the cloud-api of the cloud-service used in the Cloud-Object which can lead to huge loading times. therefore all the data is synced in the background to provide a fluent user experience. the streamline the UI we have to implement different ways to interact to the UI-Elements outside of the container (just the content-part where your cload-objects are dispalyed). These hooks are currently not implemented and I assume the implementation would be quite costly. I think a small "feasability study" would be needed to check if there is a more performant server-side way or if it is possible to design the client-side version (as it is now) accordingly.

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

  • {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.

Last edited: 4. Oct 2017, 09:07, Schmid, Fabian [fschmid]