[web2py] Re: Suggestion: db stats in response.toolbar format

2011-12-29 Thread Massimo Di Pierro
Can you identify the cause of the problem? is it css related?

On Dec 29, 12:47 am, lyn2py lyn...@gmail.com wrote:
 Hi Massimo,

 1.99.4 stable

 The db stats in response.toolbar is one long single line, which is
 less readable than 1.99.2 (a lot of scrolling).
 Perhaps the readability can be improved for future versions (use the
 format in 1.99.2?).

 Thanks!


Re: [web2py] Re: Suggestion: db stats in response.toolbar format

2011-12-29 Thread Richard Vézina
It may css related because I don't have any problem with my own css that
come from older web2py version (one line per db request).


Richard

On Thu, Dec 29, 2011 at 4:41 PM, Massimo Di Pierro 
massimo.dipie...@gmail.com wrote:

 Can you identify the cause of the problem? is it css related?

 On Dec 29, 12:47 am, lyn2py lyn...@gmail.com wrote:
  Hi Massimo,
 
  1.99.4 stable
 
  The db stats in response.toolbar is one long single line, which is
  less readable than 1.99.2 (a lot of scrolling).
  Perhaps the readability can be improved for future versions (use the
  format in 1.99.2?).
 
  Thanks!



[web2py] Re: Suggestion: db stats in response.toolbar format

2011-12-29 Thread lyn2py
I would think that it is related to HTML (div wrappers or table
width), the table column width seems to be infinite in
WelcomeApp(v1.99.4 - which is the new layout):
tdpreSELECT .../pre/tdtd0.43ms/td
The column expands to fit SELECT ... (the actual database code used
to query, in my case, sqlite)
So I have very long columns, which I need to scroll (side-ways) to see
the entire query, followed by a small column, the time it took to run
the query.

Although the html used is exactly the same as the version in
WelcomeApp(v1.99.2 - which is the previous layout), the SELECT ...
column wraps itself nicely to fit the view (same width as the
content), and without any side-ways scrolling, I can see the entire
query and duration (in ms).

Does this make sense?

==
Side note:
Although not a big deal, the pre/pre in 1.99.2 is in courier font,
but the pre/pre in 1.99.4 (only referring to the html/css, not
gluon framework) is in the same font as the content. I have always
thought that pre should have a monospaced font for code readability
- but maybe you have a reason for this? This could be a change in the
CSS.

Thanks for considering my suggestion.


On Dec 30, 5:41 am, Massimo Di Pierro massimo.dipie...@gmail.com
wrote:
 Can you identify the cause of the problem? is it css related?

 On Dec 29, 12:47 am, lyn2py lyn...@gmail.com wrote:







  Hi Massimo,

  1.99.4 stable

  The db stats in response.toolbar is one long single line, which is
  less readable than 1.99.2 (a lot of scrolling).
  Perhaps the readability can be improved for future versions (use the
  format in 1.99.2?).

  Thanks!