Quote:
Originally Posted by chaley
One of the interesting "problems" with doing this derives from something related to what you say: are the cells the same?
Consider a cell where something in both left and right have a value. You see left and right. But what happens in another cell where the left (or right) doesn't have a value? Do we show the empty cell?
Another question: do left and right take 50% of the space each, or does the space allocate? For example, if I put tags on the left and publisher on the right, does the left grow as needed?
In both cases the cells for individual books would differ from one another. This is in fact what Android would want to do, but it might look rather unusual to the user.
|
I think all of these issues, are going to make you crazy. Especially, what's going to happen if one book has tags and another doesn't. Metadata items will not be in the same relative position on a book by book basis. (This might be an argument for having blanks areas where the metadata doesn't exist).
How about instead of having two columns of metadata, you limit them to one column but have an option to show two columns of books in list view? Then you kill a lot of the dead space on tablets but avoid all of the two columns of metadata complexity.
Quote:
Originally Posted by chaley
Finally, are there borders? Something separating the cells?
|
I think not, because that will just make everything take up more space.
Quote:
Originally Posted by chaley
My position is that these first 2 (or three) lines are inviolate. They will always be there. The optional cells will appear below. That might create some duplication in the case where one sorts on a date that is also shown in the optional fields. So be it.
|
Good, that sounds perfect.