5,391
edits
m (comments) |
m (more on headers) |
||
Line 67: | Line 67: | ||
:::Anyway, I'm colorblind, so I'll let you handle those matters as you see fit. | :::Anyway, I'm colorblind, so I'll let you handle those matters as you see fit. | ||
:An "End" column is not needed. I'm not sure I'd call the first column "Start", but it's OK. | :An "End" column is not needed. I'm not sure I'd call the first column "Start", but it's OK. | ||
:I also don't like "Translation" and "Meaning" at all, but it's also cosmetic. | |||
:As for the "Bytes", I think I'd replace it with a ''type'' when applicable | |||
::(long, short, float, level ID, file ID, RAW/SEP address) | |||
:::(maybe with a distinction between different DAT-link and RAW-link types, OBD-style) | |||
::::(ideally, informative tables should replicate fully functional struct-defs and vice-versa) | |||
::Actually, I wouldn't integrate the column headers (or their sizes) into the template at all. | ::Actually, I wouldn't integrate the column headers (or their sizes) into the template at all. | ||
:::Because in specific cases, you may want to organize the data somewhat differently | :::Because in specific cases, you may want to organize the data somewhat differently |