Discussion: Edit

Editing BattleTechWiki talk:Project Systems

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 178: Line 178:
 
:::::::::::::- I'd prefer the dead/vanished worlds to remain on the system tables - that's what we've been doing so far, and as various systems have shown us in canon, at least some of them are not completely dead (see: Touring the Stars: Tyrfing, touring the Stars: Inglesmond mentions of medieval-level human settlements on Haddings in one of the BattleCorps short stories, etc). In terms of number of systems to show on the Distant Neighbours table, I'd recommend a multiple of 4; from the testing I've done, the table works well when each row has four planets in it - pushing it up to five moves the table boundaries outside the screen area/easy scrolling area of a lot of monitors. [[User:BrokenMnemonic|BrokenMnemonic]] ([[User talk:BrokenMnemonic|talk]]) 15:46, 29 August 2018 (EDT)
 
:::::::::::::- I'd prefer the dead/vanished worlds to remain on the system tables - that's what we've been doing so far, and as various systems have shown us in canon, at least some of them are not completely dead (see: Touring the Stars: Tyrfing, touring the Stars: Inglesmond mentions of medieval-level human settlements on Haddings in one of the BattleCorps short stories, etc). In terms of number of systems to show on the Distant Neighbours table, I'd recommend a multiple of 4; from the testing I've done, the table works well when each row has four planets in it - pushing it up to five moves the table boundaries outside the screen area/easy scrolling area of a lot of monitors. [[User:BrokenMnemonic|BrokenMnemonic]] ([[User talk:BrokenMnemonic|talk]]) 15:46, 29 August 2018 (EDT)
  
:::::::::::::: I'm with you on keeping them on both maps ''and'' tables. I think Sarna's role is to track the status of items of interest, not "delete" them for the periods of time the canon does. We already do this on Ownership tables by reporting "no record" at critical years; I think ownership tables, maps, and distance tables should maintain the focus.
+
:::::::::::::: I'm with you on keeping them on both maps ''and'' tables. I think Sarna's role is to track the status of items of interest, not "delete" them for the periods of time the canon does. We already do this on Ownership tables by reporting "no record" at critical years; I think ownership tables, maps, and distance tables should maintain the focus.--[[User:Revanche|Revanche]] <sup>([[User_talk:Revanche|talk]]|[[Special:Contributions/Revanche|contribs]])</sup> 21:59, 29 August 2018 (EDT)
:::::::::::::: Good point about the multiples of four. Is there a technical reason why the columns would not be limited to four, though. For example, if we went with 20 (for the Distant Neighbors table, wouldn't we have 4 columns, 5 rows? With the Nearby Systems table, we won't have the option of limiting them to multiples of four systems listed. --[[User:Revanche|Revanche]] <sup>([[User_talk:Revanche|talk]]|[[Special:Contributions/Revanche|contribs]])</sup> 21:59, 29 August 2018 (EDT)
 
  
 
::::::::::::::: Sorry, I'm not sure I was clear above. The tables I've been putting together manually effectively have eight columns, with each row covering four worlds using two cells for each (name, distance). The table then has as many rows as it needs to fit all the worlds in below. When I experimented with rows containing ten columns/five worlds at a time, they were too wide for a lot of displays, particularly in instances where very long planet names cropped up (like [[Bob]]'s alter-ego). Unless you can dynamically generate the table with each view, so that they resize to the size of the display on the device viewing them, then four worlds per row is probably the way to go. [[User:BrokenMnemonic|BrokenMnemonic]] ([[User talk:BrokenMnemonic|talk]]) 12:21, 30 August 2018 (EDT)
 
::::::::::::::: Sorry, I'm not sure I was clear above. The tables I've been putting together manually effectively have eight columns, with each row covering four worlds using two cells for each (name, distance). The table then has as many rows as it needs to fit all the worlds in below. When I experimented with rows containing ten columns/five worlds at a time, they were too wide for a lot of displays, particularly in instances where very long planet names cropped up (like [[Bob]]'s alter-ego). Unless you can dynamically generate the table with each view, so that they resize to the size of the display on the device viewing them, then four worlds per row is probably the way to go. [[User:BrokenMnemonic|BrokenMnemonic]] ([[User talk:BrokenMnemonic|talk]]) 12:21, 30 August 2018 (EDT)

Please note that all contributions to BattleTechWiki are considered to be released under the GNU FDL 1.2 (see BattleTechWiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Advanced templates:

Editing: {{Merge}}   {{Moratorium}}   {{Otheruses| | | }}

Notices: {{NoEdit}}   {{Sign}}   {{Unsigned|name}}   {{Welcome}}

Administration: {{Essay}}   {{Policy}}   {{Procedure}}

Template used on this page: