Template talk:CarriageNavbox

From SVR Wiki
Revision as of 15:19, 17 January 2017 by Robin (talk | contribs) (In conclusion)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

I have a feeling it will be too unwieldy with all the carriages added. I have added a possible simpler version for comparison. --Robin (talk) 14:31, 15 January 2017 (UTC)

Yes, I thought it was moving towards being quite big, given that I hadn't even touched BRBritish Rail or British Railways yet! Mind, the long list of numbers is quite intimidating... --Danny252 (talk) 15:12, 15 January 2017 (UTC)
The SVRSevern Valley RailwaySVRA:Severn Valley Railway AssociationSVRS:Severn Valley Railway Society has an intimidating collection of carriages! I split out the BRBritish Rail or British Railways MK3 and NPCCS for just that reason. To me, the new Steam Loco navbox still looks just about OK at 11 rows, but I think that's about the limit we should aim for. I'm open to any ideas on some sort of half-way house that can break it down a bit more without going over the top.--Robin (talk) 16:49, 15 January 2017 (UTC)
All I can currently think of is adding the "BG", "TK", etc. labels as I have here, but I imagine those would only make the lists look longer, rather than helping. --Danny252 (talk) 09:25, 16 January 2017 (UTC)
As a test, I’ve added the simple Navbox to GWR 98 Full Brake to see how it looks on a page which already has a carriage Infobox (adding all the other carriage infoboxes is high on my ‘to do’ list). Personally I don’t think it’s too bad – the lines wrap if the screen width is too small.
Adding the BG etc labels would make the already long lists that much longer as you say. I can think of a couple of ways to make the lines shorter without more than doubling the number of rows. One would be simply to have “GWRGreat Western Railway” and “GWRGreat Western Railway (continued)”, although that seems a bit contrived and may make it worse rather than better with the line wrap. The other would be to have something like “GWRGreat Western Railway In service” and “GWRGreat Western Railway other”. However you then have to maintain the Navbox as items come and go between those classes.
For Navbox functionality generally, I see it mainly as a quick way to jump from one page to another rather than as a way of classifying the items within it (it would remove the need for the “previous” and “next” links under “See also”). Some structure is needed, so it makes sense to split between companies. However I think things like which are BG and TK are better handled through the category pages. These can be accessed from the Infobox if type is made a link as I have done for 98, and/or from the categories at the foot of the page. And/or we could add a line of Carriage Types in the Navbox itself. Or we could not bother with a Navbox!
Any more thoughts or suggestions? --Robin (talk) 18:21, 16 January 2017 (UTC)
It doesn't look overly terrible, actually, as you say - and thinking on it more, adding classes etc. to the list would really just be duplicating the far more detailed lists on Carriages. We could add the categories to the navbox - but looking at, there's 25 of them, several with their own subclasses! Maybe a link like in the footer, but again, the list in Carriages covers it already (and in more detail).
In conclusion, I think I've argued myself out of all my suggestions? --Danny252 (talk) 09:41, 17 January 2017 (UTC)
I guess so. I'll move the simple one into here and delete Navbox2, the original code will be in the history of this page if ever needed. I have a feeling that a WagonNavbox may be a step too far... --Robin (talk) 15:19, 17 January 2017 (UTC)