User talk:Abcboy/Archive 1: Difference between revisions

User talk:Abcboy/Archive 1 (view source)

Revision as of 22:17, 25 June 2015

2,240 bytes added , 25 June 2015

→‎Column Widths

CycloneGU

10,264

edits

@@ Line 505: / Line 505: @@
 ::It is true that mobile devices would of course render the tables the same width and they would look the same that way.  The concern is the different widths of the tables on a page that has a long width itself (such as a computer screen).  The text will automatically extend the width "as your "bla bla" line does", and I don't want it to do that, but also don't want to use <nowiki><br></nowiki> tags to resolve that problem when setting a width is a more clean solution.  The tags can in fact even cause the appearance of unneeded space.  [[User:CycloneGU|CycloneGU]] ([[User talk:CycloneGU|talk]]) 21:03, 25 June 2015 (UTC)
 :::I just reread the comment again.  I will reanalyze the width scenario as far as tables go after dinner.  Just heating some stuff up, then the image uploads will be after that; it's better to experiment in previews once the new images are in (created the Bulba template for pulling them earlier today).  [[User:CycloneGU|CycloneGU]] ([[User talk:CycloneGU|talk]]) 21:09, 25 June 2015 (UTC)
+::::All right, I have attempted your suggestion.  [http://oi60.tinypic.com/24o5z4o.jpg This is what happens.]  The preview test had "Order" not set to a width, "Pokémon" in fact set for a 130px width (both columns), "Type" and "HP" at 60px and 40px respectively, and "Appearance" not set per your suggestion.  As you see, even the "Pokémon" columns, with set widths, have different sizes; even accounting for "Order" being slightly larger, the column is still measured about 10px larger though I have both set to 130px.  I tried removing borders (which are not needed with table widths) and the same result occurred.  When I got rid of the table width and restored the width to the last column ("Order" doesn't need it because it's automatically longer than any entry in the column), everything was uniform both outside and inside again.
+::::So to better explain why I use column widths instead of table widths: it causes, internal columns to always be a set width in every single table, without deviation.  If we have three columns of 100, 50, and 200 respectively, the table width will ALWAYS be 350px; if we just set the width for the table and not the columns, the columns will readjust themselves dynamically, making for a much sloppier presentation all because of a concern for "whitespace" in a very small number of instances.  One more thing I should note is that I'm considering adding a "Location" column, which would also allow for a reanalysis of how the final column (the conditional) is presented, but I'm leaving it for now.  The design is therefore not final, but just a good working design for now, and it's a design I am confident with in terms of a professional presentation to the user.  I will note that I did change the width from 250 to 200 for the last column, and I may adjust it down further.  I'm undecided on that.  We could also move the conditional out of the table and set them as table notes under the table if you think that would be a better presentation (and would drastically shrink the table by that 200 pixels, not necessarily a bad thing), thus leaving the column for just "Location", which has other benefits.  [[User:CycloneGU|CycloneGU]] ([[User talk:CycloneGU|talk]]) 22:17, 25 June 2015 (UTC)