Usability Improvements for large screens

1 Requirements

A) position of togglebutton for treeview

In DELOS (since ILIAS 5.0), the togglebutton for the optional treeview of the Respository is anchored at the top-left corner of the contentarea.
When using large screens (width: 1600 px and beyond) this button is fairly detached from the controlled treeview. To improve intuitiveness the button should be attached at the top-left of the content.
see:  bugreport 16253

B) width of centered content

Since ILIAS 5.0, the content is expanded to a centered column with a maximum width of approx. 1340 px. If the content only contains 'plain text', a limit makes sense. But on large screens its annoying, that a good part of the available width is unuseable - especially in scenarios like "A)": the limited width of the content is shared into 3 columns (the tree, the list and several boxes on the right (news, calendar, etc.)).
The width of the centered content should use more of the available space reflecting the layout of the current content: the more columns exists, the more space should be used.
Or even more, what about an checkbox-attribute in the settings of repository objects: "disable limitation of content width"? Then the user optional regains full control over the appropriate width by sizing his browser-window.

C) height of footer

Since ILIAS 5.0 the footer has a fixed heigth of 160 px. I can't imagine, what this is good for. Even the screnshot in UI: Footer is cut off directly beneath the one and only relevant content!  Am I'm missing situations where in fact the free space IS used?
When scrolling content to the bottom - often one is coerced to scroll back a little back to have some more content visible.
The footer should be reduced vertically, so that the 'one and only' line appeares centered in the footer.

2 Additional Information

• Idea / concept: Tesche, Uwe [utesche]
• Interest in funding: (please indicate if you are interested/able to fund this feature)
• Maintainer: (will be set by Jour Fixe / maintainer)
• Implementation of the feature is done by (will be set by Jour Fixe / maintainer)
• Testcases by: (please add your name if you want to create the testcases for this feature)

3 Discussion

4 Implementation

{please 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}.