View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0020120 | mantisbt | bugtracker | public | 2015-09-16 19:38 | 2016-12-30 14:07 |
Reporter | cproensa | Assigned To | |||
Priority | low | Severity | tweak | Reproducibility | always |
Status | new | Resolution | open | ||
Product Version | 1.3.0-beta.3 | ||||
Summary | 0020120: my view page boxes layout | ||||
Description | I found in "my_view_page.php" Current layout is boxes layered in one column. This happens when having the setting:
Fix is trivial if you can confirm | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Some thoughts to discuss with some more developers: I don't like the timeline that much as it takes a lot of space and enforces some vertical scrolling. I am running one of my production environments using 1.2.x. Nowadays most of the current displays have a width screen layout. Not sure if we can have it the same way in 2.0 as we need some horizontal space for the new navigation bar at the left. BTW there is a PR for 1.3.x to have a configuration to deactivate the timeline |
|
Reminder sent to: dregad, rombert, syncguru, vboctor Thoughts? |
|
I think the Timeline is better suited to reporters than developers. In my site reporters have its view limited to their own issues, so Timeline would be a great tool to keep them updated. For that reason, a view threshold seems not to be the best approach, unless it works backwards, like a "hide" threshold. |
|
I personally use the timeline a lot, and it does not bother me so much that it takes a lot of vertical space. I don't remember off-hand if the number of displayed items is configurable or not, but if not maybe it's a feature that could be added. That being said, I agree it would be nice to allow boxes layout on 2 columns, if the display area allows it. Ideally, this layout should be automatic, i.e. adjust based on screen width.
Currently, this space is proportional to the screen's width (no time to check the code to determine if and how this could be changed). Maybe syncguru who is better at this CSS stuff than I am, can comment.
This comes from the "content" div which adds padding. Should not be a big deal to change
I agree with that, but as I said [1] this PR can't be merged as it is because of the 1-column layout which does not look good. [1] https://github.com/mantisbt/mantisbt/pull/592#issuecomment-93680455 |
|
But note that whith The bug seems to be that when option is ON, its not setting correctly the rows, columns, whis is also intended to be two columns (the comments in code says so). The fixed result is on my screenshot previously attached |
|
I never missed a timeline as there is the "Recently Modified" box which is triggered by ALL modifications.
So the question at least for 1.3.x is: I tried a bit and found that I prefer 3 columns. I added $g_my_view_boxes_fixed_position = OFF; temporary to our configuration to get a real life feeling for the layout. |
|
This is the code for case $g_my_view_boxes_fixed_position = ON
|
|
Added a screenshot 3columns.png how it looks on an old school 1280x1024 display. |
|
The "3 columns" layout causes display problems on narrow screens (column 2 overlaps with timeline), as shown in attached mantisbt_myview_2cols_overlap.png |
|
It does no longer overlap if you make the window even smaller. Seems we shouldn't introduce the "3 columns" layout without some CSS tweaks. BTW, I added just $g_my_view_boxes_fixed_position = OFF; but didn't apply the patch. |
|
I'm OK with 3 column layout. However, as mentioned above we should do a better job with CSS and being responsive as the window is smaller or MantisBT is visited on a mobile phone. Long term, I would like us to think of My View page as a Dashboard page that is basically a grid of 3 columns. The following components are placed on such grid.
The trick with the above is providing an easy way to customize the view that ideally would support default and per user configurations. Bunch of that will have to depend on the modern responsive UI + some fancy ajax + javascript. |
|