Hi all,
Currently the database operations tab is organized in such a way that all the operations can't be seen in one screen and vertical scrollbars are added to the page due to this. I suggest we organize the database operations tab in a similar way to table operations tab, where the operations are listed in two columns. What do you all think?
A patch for this lies at https://sourceforge.net/tracker/?func=detail&aid=3292121&group_id=23... . Please check that out.
I have also attached a screenshot of the new db operations tab here.
Le 2011-04-23 14:54, Madhura Jayaratne a écrit :
Hi all,
Currently the database operations tab is organized in such a way that all the operations can't be seen in one screen and vertical scrollbars are added to the page due to this. I suggest we organize the database operations tab in a similar way to table operations tab, where the operations are listed in two columns. What do you all think?
I agree that the current way is not compact enough and we should use divs to enclose the blocks.
As a side note: people with a wide screen (not me) may not like the current disposition of table operations either, which is "forced" in two columns by enclosing each block in a div, making it float to the left, setting a min-width of 48% and using "clear: both" to force a block to go to the left side.
I haven't look at your patch yet, but maybe using jQuery's .width() could help us optimize the min-width of these divs.
On Sun, Apr 24, 2011 at 4:36 AM, Marc Delisle marc@infomarc.info wrote:
Le 2011-04-23 14:54, Madhura Jayaratne a écrit :
Hi all,
Currently the database operations tab is organized in such a way that all the operations can't be seen in one screen and vertical scrollbars are
added
to the page due to this. I suggest we organize the database operations
tab
in a similar way to table operations tab, where the operations are listed
in
two columns. What do you all think?
I agree that the current way is not compact enough and we should use divs to enclose the blocks.
As a side note: people with a wide screen (not me) may not like the current disposition of table operations either, which is "forced" in two columns by enclosing each block in a div, making it float to the left, setting a min-width of 48% and using "clear: both" to force a block to go to the left side.
I am using a wide screen and I'm not sure I follow you when you talk about the disposition. Actually I used the same styles used in table operations (float: left, min-width: 48%, and clear: both when necessary), so the patch too might be prone to the problems you described.
Le 2011-04-23 23:36, Madhura Jayaratne a écrit :
On Sun, Apr 24, 2011 at 4:36 AM, Marc Delisle marc@infomarc.info wrote:
Le 2011-04-23 14:54, Madhura Jayaratne a écrit :
Hi all,
Currently the database operations tab is organized in such a way that all the operations can't be seen in one screen and vertical scrollbars are
added
to the page due to this. I suggest we organize the database operations
tab
in a similar way to table operations tab, where the operations are listed
in
two columns. What do you all think?
I agree that the current way is not compact enough and we should use divs to enclose the blocks.
As a side note: people with a wide screen (not me) may not like the current disposition of table operations either, which is "forced" in two columns by enclosing each block in a div, making it float to the left, setting a min-width of 48% and using "clear: both" to force a block to go to the left side.
I am using a wide screen and I'm not sure I follow you when you talk about the disposition. Actually I used the same styles used in table operations (float: left, min-width: 48%, and clear: both when necessary), so the patch too might be prone to the problems you described.
What I meant is that with a wider (and bigger) screen, two columns might not be enough to fill the screen horizontally.
-
Madhura Jayaratne -
Marc Delisle