An Unified File Browsing Experience in the ChRIS_ui

[PintoGideon]

Background:

Currently, the ChRIS_ui has different file browsers that don't use the same file browsing api that cube has to offer.

For example:

1. The Feed Browser use the filebrowser api written by Jorge Bernal.

2. The browser in the Create Feed Wizard fetches files and builds the tree before rendering it on the screen. The approach is not scalable and highly ineffecient. High wait times have been observed for a larger swift space making this browser unusable.

3. The browser in the Library Page uses the filebrowser api, but a feature request to provide an alternative browsing view has been requested. The Library page is being used by researches in the lab for searching through the feeds/pacs space and a tree view would be great UX for the feeds space especially, since the folders there are deeply nested.

4. A Swift Browser for the Dicom Viewer has been requested where the user can choose the files they want to view with XTK or the Dicom Viewer.

Reality

Though two of the three filebrowsers use the same api, the code is currently repeated in the code base adding to significant bloat
and a larger bundle size when deploying the UI.

Criticisms

The ChRIS_ui should be moving towards a unified browsing experience where the underlying code for browsing should be modularized and reusable. The user can choose the layout in which the wish to view the files.

The two options for layouts are:

1. The Tree View
2. The Folder Based View.

Reflection

This feature is medium effort (2-4 weeks), but has a high reward.