Template talk:InfoboxShip

Notes (2018)

Ship 1 Stock Template (Alphabetized):

{{InfoboxShip
|name     = 
|alsosee  = 
|architect= TBD
|caption  = 
|cargo    = 
|crew     = 
|cost     = 
|IOC      = TBD
|enlisted = TBD
|footnote = TBD
|g        = 
|hp       = 
|hpass    = 
|image    = Imperial Sunburst-Sun-IISS-Traveller.gif
|jump     = 
|lpass    = 
|marines  = TBD
|model    = TBD
|officers = TBD
|origin   = Third Imperium
|QSP      = TBD
|size     = 
|tdes     = 
|TL       = 
|type     = 
|usp      = TBD
|manufacturer= Various
}}

Experimental Ship 2 Stock Template (Alphabetized w/definitions):

{{InfoboxShip
│Name     =
│agility  = TBD
│armor    = (Armor type in tons)
│bridge   = TBD
│caption  = TBD
│cargo    = (in tons)
│compTL   = TBD
│cost     = TBD MCr
│crew     = TBD
│dateIOC  = (Initial Operational Capacity)
│defense  = (major defensive systems)
│footnote = TBD
│fuel     = TBD
│fuelproc = TBD
│G        = Maneuver / Sublight Drive (Sublight)
│Hp       =
│Hpass    = (HiPass)
│Hullcnfig= [per architect guides] 
│image    = [[file: Imperial Sunburst-sun-IISS-Traveller.gif]]
│jump     = Jump Drive (JumpDriv)
│Lpass    = (LoPass)
│Maneuver = Will replace G in InfoBoxShip2
│Mpass    = (MedPass)
│size     = [in tons]
│smallcrft= TBD
│stealth  = TBD
│streamlne= TBD 
│Tdes     = Type
│TL       = Tech
│type     = Military
│weaponry = Offensive systems.
│manufacturer= TBD
}}

Experimental Ship 2 Stock Template (Alphabetized):

{{InfoboxShip
│Name     = TBD
│agility  = TBD
│armor    = TBD
│bridge   = TBD
│caption  = TBD
│cargo    = TBD
│compTL   = TBD
│cost     = TBD
│crew     = TBD
│dateIOC  = TBD
│defense  = TBD
│footnote = TBD
│fuel     = TBD
│fuelproc = TBD
│G        = TBD
│Hp       = TBD
│Hpass    = TBD
│Hullcnfig= TBD
│image    = [[file: Imperial Sunburst-sun-IISS-Traveller.gif]]
│jump     = TBD
│Lpass    = TBD
│Maneuver = TBD
│Mpass    = TBD
│size     = TBD
│smallcrft= TBD
│stealth  = TBD
│streamlne= TBD 
│Tdes     = Type
│TL       = TBD
│type     = TBD
│weaponry = TBD
│manufacturer= TBD
}}

Edits and additions to the Template (2019)

Maksim, you asked me to add a few things to both the template and the underlying cargo tables. In reading through the existing template I have found a number of changes that could be made. I'm putting the list here for discussion:

• Aerodynam: Since every rule set refers to this as Streamline, I think that make a better parameter name than the truncated Aerodynam.
• Architect: In the original this was the Architect fee, part of the cost of creating a ship. Not all ship design system include this as a calculation. I am re-asserting this parameter as the fee (in MCr).
• Canon: In all the other templates this is a simple Yes/No flag. I'm going to assume this is true here too.
• Cost: Pedantically, this should be price, but every system uses Cost. There are three parts to the cost of a ship: Architect fees, price singly, and price in quantity. I've seen several ships trying to put both into this field. Cost will be assumed to be for singly, and add a costQuantity field. And architect parameter will hold the Architect fee.
• Designer: The designer is a new parameter, holding the name of the person who created the design (if known). e.g. Ronald Klein. The ref parameter is for book references.
• Design System: The designSystem is a new parameter. This holds the name of the design system used for the original design. e.g. Book 2, High Guard, MT, GT: Starships, T5, FF&S1, FF&S2, etc. The different design systems can produce different results.
• Hpass / Lpass: These are assumed to be Staterooms and Low Berths (respectively). Some designs include barracks between these two. And small-craft may have seats (think airplane).
• Illustration: Like Canon and Blueprint this will be a simple Yes/No flag
• IOC : I wish the linked page would explain the IOC refers to year of starting operation. This will be only a year. Is there a corresponding term for when the ship leaves service?

- Tjoneslo (talk) 23:23, 23 May 2019 (EDT)

---

Thank you for all of your hard work and brainstorming.

• I will respond back later.
• Great ideas!

- Maksim-Smelchak (talk) 13:51, 24 May 2019 (EDT)

Modest Update Proposals (2019)

Thomas, feedback: Why don't we proceed with two new updates:

1. InfoboxShip2: A gradual update of the older template along very modest lines.
2. InfoboxShip3: A more differentiated update of the template with the ideas you have presented which are quite excellent.

---

FYI, a discussion like this is why the wiki style of comments works better. We can create a thread of discussion about each topic.

I dislike the idea of creating two new templates. There should be at any one time one infobox template to be used for a type of article. In the case, like this one, where we're making major changes we should have an old template, and a new template. The editors should be instructed to use the new template on new articles, and if possible update existing article to the new template as needed. With too many templates it becomes confusing as to which should be used.

- Tjoneslo (talk) 21:38, 25 May 2019 (EDT)

---

InfoboxShip3:
All of the ideas should be implemented exactly as you have proposed.

• Aerodynam: Since every rule set refers to this as Streamline, I think that make a better parameter name than the truncated Aerodynam.
• Architect: In the original this was the Architect fee, part of the cost of creating a ship. Not all ship design system include this as a calculation. I am re-asserting this parameter as the fee (in MCr).
• Canon: In all the other templates this is a simple Yes/No flag. I'm going to assume this is true here too.
• Cost: Pedantically, this should be price, but every system uses Cost. There are three parts to the cost of a ship: Architect fees, price singly, and price in quantity. I've seen several ships trying to put both into this field. Cost will be assumed to be for singly, and add a costQuantity field. And architect parameter will hold the Architect fee.
• Designer: The designer is a new parameter, holding the name of the person who created the design (if known). e.g. Ronald Klein. The ref parameter is for book references.
• Design System: The designSystem is a new parameter. This holds the name of the design system used for the original design. e.g. Book 2, High Guard, MT, GT: Starships, T5, FF&S1, FF&S2, etc. The different design systems can produce different results.
• Hpass / Lpass: These are assumed to be Staterooms and Low Berths (respectively). Some designs include barracks between these two. And small-craft may have seats (think airplane).
• Illustration: Like Canon and Blueprint this will be a simple Yes/No flag
• IOC : I wish the linked page would explain the IOC refers to year of starting operation. This will be only a year. Is there a corresponding term for when the ship leaves service?

InfoboxShip2 (IBS2):
This would ideally be a more modest update:

• Aerodynam: Since every rule set refers to this as Streamline, I think that make a better parameter name than the truncated Aerodynam.
  • IBS2 would leave this alone without changes.
• Architect: .Architect fee...
  • This will become the designer in IBS2, I have been laboriously interviewing Marc to find these as in the Type S and am hesitant to update all of the templates. Other users have asked to convert this to fees. So, let's do it overriding my preferences.
• Canon: In all the other templates this is a simple Yes/No flag. I'm going to assume this is true here too.
  • I would like to leave this as a text box rather than a boolian integer. Many of the entries have responses more complicated than y/n.
• Cost: There are three parts to the cost of a ship: Architect fees, price singly, and price in quantity...
  • I am good with changes anyway you do it. It does makes sense as a three-part venture.
• Designer: The designer is a new parameter, holding the name of the person who created the design (if known). e.g. Ronald Klein. The ref parameter is for book references.
  • I quite agree with you. Ref is for published sources... ideally. But, we still have homebrews to deal with. Dsigner can become the designer... sigh. ;-)
• Design System: The designSystem is a new parameter. This holds the name of the design system used for the original design. e.g. Book 2, High Guard, MT, GT: Starships, T5, FF&S1, FF&S2, etc. The different design systems can produce different results.
  • Brilliant.
• Hpass / Lpass: These are assumed to be Staterooms and Low Berths (respectively). Some designs include barracks between these two. And small-craft may have seats (think airplane).
  • What do you think? I think we need to expand to this:
    • PassLP: Low Passage
    • PassMP: Middle Passage or Working Passage
    • PassHP: High Passage
    • PassFW: Frozen Watch
• Illustration: Like Canon and Blueprint this will be a simple Yes/No flag
  • Ok.
• IOC : I wish the linked page would explain the IOC refers to year of starting operation. This will be only a year. Is there a corresponding term for when the ship leaves service?
  • I updated the article awhile back. Added the other end of the equation:
    • IOC
    • EoS

Thanks!

- Maksim-Smelchak (talk) 21:06, 24 May 2019 (EDT)

Two New Templates (2019)

FYI, a discussion like this is why the wiki style of comments works better. We can create a thread of discussion about each topic.

I dislike the idea of creating two new templates. There should be at any one time one infobox template to be used for a type of article. In the case, like this one, where we're making major changes we should have an old template, and a new template. The editors should be instructed to use the new template on new articles, and if possible update existing article to the new template as needed. With too many templates it becomes confusing as to which should be used.

- Tjoneslo (talk) 21:38, 25 May 2019 (EDT)

---

I am going to agree to disagree with you here.

• I think that this technique works if one is not willing to use newer common techniques.
• Otherwise, much more can be done much more quickly with a cooperate and collaborative technique.
• This system creates bottlenecks and was pretty advanced for the 1990s. It's old school and often not in a good way.