Since the manifest table is a table and all, I wondered how it would render on screens large and small if the manifest table were actually posted as a [table]. So, I reworked it (including learning things like [td][hr][/td] won't even preview and plain [hr] between rows actually renders but splits the table into multiple tables, breaking the column alignment).This is a copy of the current first post, coded as a table. (I put just the LV column in bold, as I thought as a rendered table it needed something to help visually break up/anchor the line.) Obviously reposted unquoted for "test as you post" fidelity. Since the preview is not the same width as a post in thread, and since I can't see what it looks like on my phone without it being posted, here goes nothing.Any comments, questions, or rapid mod edits/deletion if rendering this post messes up the thread display? (Hey, it looked great in preview. )
2017-06-25 1325/-7 F9 1036 S Iridium NEXT (Flight 2) PLR 9600 V-4E 38 2017-06-23 1510/-4 F9 1029.2 S BulgariaSat-1 GTO 3669 C-39A 372017-06-03 1707/-4 F9 1035 L CRS 11 LEO ~9k C-39A 36 2017-05-15 1921/-4 F9 1034 X Inmarsat 5 F4 GTO 6086 C-39A 35 2017-05-01 0715/-4 F9 1032 L NROL-76 LEO ? C-39A 34 2017-03-30 1827/-4 F9 1021.2 S SES-10 GTO 5282 C-39A 33 2017-03-16 0200/-4 F9 1030 X Echostar 23 GTO ~5500 C-39A 32 2017-02-19 0939/-5 F9 1031 L CRS 10 LEO ~9k C-39A 31 2017-01-14 0954/-8 F9 1029 S Iridium NEXT (Flight 1) PLR 9600 V-4E 30 2016-09-01 0907/-4 F9 N/A AMOS-6(destroyed in pad test) GTO 5500 C-40 29 2016-08-14 0126/-4 F9 S JCSAT-16 GTO ~4600 C-40 28 2016-07-18 0045/-4 F9 L CRS-9 LEO ~9k C-40 27 2016-06-15 1029/-4 F9 S Eutelsat 117W B & ABS-2A GTO 4200 C-40 26 2016-05-27 1740/-4 F9 1023 S Thaicom 8 GTO 3025 C-40 25 2016-05-06 0121/-4 F9 1022 S JCSAT-14 GTO 4696 C-40 24 2016-04-08 1643/-4 F9 1021 S CRS-8 LEO ~9k C-40 23 2016-03-04 1835/-5 F9 S SES-9 GTO 5271 C-40 22 2016-01-17 1042/-8 F9 S Jason-3 LEO 553 V-4E 21 2015-12-22 F9 1019 L ORBCOMM OG2 Launch 2 LEO 1892 C-40 20
The list of past launches is growing. The old policy was to trim past launches after a year on the list.However, this is such a nice display I would like to see it retained.How about putting it at the bottom of the list?
I use that list to find the mission threads, so I hate to remove the old ones.
Only quibble would be to see the Heavy core numbers in the main table - three rows?
A minor nitpick: It would be nice to have the original flight of a later re-used core updated so that the reuse was evident, e.g., 1029.1
Quote from: toren on 06/26/2017 06:59 pmA minor nitpick: It would be nice to have the original flight of a later re-used core updated so that the reuse was evident, e.g., 1029.1I'd vote for this as well. Apart from that, it's perfect!
In the "previous missions" list (second post of the manifest thread), how would you feel about putting in some sort of break between calendar years? Not too sure how best to do it, but I've demonstrated it with an added dash. Can't seem to get the table to just recognize an empty row. Would look like: ...
I just noticed that the past missions list doesn't have any of the F1 launches or the pad abort.