fixed column withs in the data display are not good for viewing data

google-code-export / ords

Automatically exported from code.google.com/p/ords

1 stars 0 forks source link

fixed column withs in the data display are not good for viewing data #18

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Go to the Data View
2. Observe that the column width is the same for a record id# as it is for a 
free-text 'notes' field
3. Try in vain to resize the columns

This is a minor feature enhancement really, but would almost certainly be very 
popular amongst our users

Original issue reported on code.google.com by jajwil...@gmail.com on 23 Oct 2012 at 3:37

GoogleCodeExporter commented 9 years ago

Original comment by jajwil...@gmail.com on 8 Mar 2013 at 10:58

Added labels: Priority-High
Removed labels: Priority-Low

GoogleCodeExporter commented 9 years ago

Original comment by jajwil...@gmail.com on 2 May 2013 at 2:14

Changed state: New
Added labels: Priority-Medium
Removed labels: Priority-High

GoogleCodeExporter commented 9 years ago

How would you like this to work? I could make each field resizable individually 
but it would still be a pain to have to go through each field to resize them, 
and be pointless if the field were an int or only contained a small number of 
chars... please advise

Original comment by thest...@gmail.com on 6 Aug 2013 at 2:29

GoogleCodeExporter commented 9 years ago

I'm imagining that each field would be the width of the longest string of data 
within it, up to a certain maximum (e.g. 40 characters). I think that this 
would make better use of screen 'real estate', especially given that the 
average column of ints doesn't need to be very wide. It's something we'd need 
to evaluate with users, however. It shouldn't be a high priority.

Original comment by jajwil...@gmail.com on 6 Aug 2013 at 3:53

GoogleCodeExporter commented 9 years ago

Original comment by jajwil...@gmail.com on 19 Sep 2013 at 10:06

GoogleCodeExporter commented 9 years ago

One for Joe?

Original comment by thest...@gmail.com on 11 Oct 2013 at 10:14

GoogleCodeExporter commented 9 years ago

Possibly - although I'm guessing that because the width of each column will be 
depended on the nature of the data in that column its display will need to be 
quite tightly integrated with the source code in this instance. Maybe assign it 
to Joe and see if he has any ideas?

Original comment by jajwil...@gmail.com on 11 Oct 2013 at 1:06

GoogleCodeExporter commented 9 years ago

I've had a look into this and I can't really see any solution.  There's no way 
to know which columns are going to contain lots of data and which aren't.  
There may be some Javascript widget to allow users to drag column widths, but 
I"m not sure this is a priority...

Original comment by jos...@josephbloggs.com on 11 Oct 2013 at 3:36

GoogleCodeExporter commented 9 years ago

I've had a think about this and a chat with James. I think the way forward is 
to have ORDS "understand" the fields it is presenting and provide a suggested 
field width for each column in a page of data. That width can then be used in 
table.jsp to give the sizes.

Original comment by thest...@gmail.com on 11 Nov 2013 at 2:51