We have begun migration of most wikis to our new host, Amazon Web Services. All but the top 100 wikis are in read-only mode until the migration is complete. Estimated completion: End of Week.

Template talk:Desktop

From Minecraft Wiki
Jump to: navigation, search

Poor approach[edit source]

This would be better as an indicator rather than a massive message box, and would be better as a single template to note all editions a feature is available in. MajrTalk
Contribs
02:15, 30 September 2016 (UTC)

Maybe a template with usage like {{feature|computer|pocket}}, replacing the current functionality of Template:Console and Template:Pocket? -- Orthotopetalk 03:28, 30 September 2016 (UTC)
We could also create a template similar to {{pocket}}. It could use this image, although I am not sure what colors to use. The BlobsPaper.png 18:22, 21 December 2016 (UTC)
This discussion was started because Majr was thinking we could make it less big and intrusive. – Sealbudsman talk/contr 20:30, 21 December 2016 (UTC)
We could make it a line in the infobox templates? – Sealbudsman talk/contr 20:30, 21 December 2016 (UTC)
If we were to do this, we should do the same for exclusive features in other versions, therefore deleting {{pocket}} and {{console}}. The BlobsPaper.png 22:09, 21 December 2016 (UTC)
Agreed, any approach should equally handle any edition I think. – Sealbudsman talk/contr 01:41, 22 December 2016 (UTC)
Agreed. As far as compactness goes, a line in the infobox would be short, informative, and most likely a better alternative to an entirely new template. Maethoredhel (tcLogs) 01:50, 22 December 2016 (UTC)
Another way would be to use {{only}}. This would work for features that exist in multiple versions but not all. An example would be as follows:
Should we use this method? The BlobsPaper.png 04:20, 29 December 2016 (UTC)
Directly in the lead like that? It would have the advantage of being in a prominent place, and wouldn't be particularly dependent on an info box. – Sealbudsman talk/contr 04:43, 29 December 2016 (UTC)
That is what I am suggesting. The BlobsPaper.png 14:29, 29 December 2016 (UTC)
It looks good. Would you have any objection to the use of an infobox row, for those pages which use infoboxes? – Sealbudsman talk/contr 17:27, 10 January 2017 (UTC)
It would work, but we would need to add parameters to all of the infobox templates, and readers might not notice it as much. The BlobsPaper.png 17:58, 10 January 2017 (UTC)
Either of these sound good. Infobox is the more standard approach, but having it in the lead is easier to do. MajrTalk
Contribs
23:17, 29 December 2016 (UTC)
My opinion stands equal with Majr. Either option is viable; however, the method described by TheBlobs with the {{only}} template seems to be a more noticeable approach for the average reader. — Maethoredhel (TalkContribsLogs) 18:52, 10 January 2017 (UTC)
How about something more visible, like this? (The icons are just something I threw together for demo purposes.) – Auldrick (talk) 02:02, 17 January 2017 (UTC)
If we end up using your template, what part of the page would transclude it? The BlobsPaper.png 02:32, 17 January 2017 (UTC)
I wish it could follow the page title, but I don't think MediaWiki supports that. Second preference would be after the infobox title, I think. BTW, I just uploaded smaller 16x16 icons. – Auldrick (talk · contribs) 02:57, 17 January 2017 (UTC)
If we want some icons, we can just use the page status indicator section. However, I don't think small icons are noticeable enough on their own so we should probably still have one of the proposed options in the article itself. MajrTalk
Contribs
03:42, 17 January 2017 (UTC)
Does "a single template to note all editions a feature is available in" imply that the bulk of articles would list all three editions? If so, I think that's a mistake. When readers see the same note on page after page, they soon learn to disregard it, and then they won't notice when the edition they're using is absent. I suggested icons with the idea that they would be shown by exception and would be colorful enough to attract attention. Actually, what I've been leading up to is suggesting that we should highlight which editions an article doesn't apply to, for exactly this reason: Highly repetitive information isn't informative, it's clutter; exceptions are what people need to see, at least those people affected by them (and the corollary is that they should be visually small enough for everybody else to easily dismiss). I didn't know about page status indicators–that's exactly what I have in mind. Plus, in the drive toward feature parity exception templates could generate categories of formerly unimplemented features for checking against changelogs, making maintenance a little easier. I'm pretty new around here and I don't mean to derail this discussion, so if I'm out of bounds please forgive me, but these thoughts have been slowly gelling in my mind. – Auldrick (talk · contribs) 04:59, 17 January 2017 (UTC)
I definitely support having the eventual solution generate some maintenance categories.
I affirm that exceptions are what people need to see. Though (perhaps a finicky point but I'll make it anyway) I think when we're on those pages with exceptions, it doesn't actually matter (except maybe for consistency's sake) whether it's saying only these editions, versus all except these editions. As long as on the "all editions" pages like Flower and Tree, it's explicit, yet subtle enough that the exceptional pages stand out. Isn't that the important part of reducing information clutter: making the info on one page stand out, as opposed to that on the other? – Sealbudsman talk/contr 07:04, 17 January 2017 (UTC)

 Support The one thing is that I am not sure about your design. I could show my idea in my sandbox. Users can decide which design is better. The BlobsPaper.png 16:59, 17 January 2017 (UTC)
By all means! This is the first template I've ever written. I was too distracted figuring out how to do it to actually think much about making it pretty. – Auldrick (talk · contribs) 20:10, 17 January 2017 (UTC)
I created my template at User:Blobs2/Sandbox/Soul. Please check it for anything that should be changed. The BlobsPaper.png 22:35, 17 January 2017 (UTC)

 Question Shouldn't it say "Not in the following edition"? – Auldrick (talk · contribs) 16:54, 18 January 2017 (UTC)
In {{pocket}} and {{console}}, the whole thing is bold. I think it would work best if the header is bold, but the rest isn't. The BlobsPaper.png 18:00, 18 January 2017 (UTC)
Sorry, I wasn't clear enough. Your template says "Not in the following version". I was asking whether "version" should read "edition". – Auldrick (talk · contribs) 23:39, 18 January 2017 (UTC)

 Maybe We need multiple users to decide which is better. The BlobsPaper.png 00:58, 19 January 2017 (UTC)
It's a long established convention though, that these things are called editions. I don't think it needs to be re-decided at this particular point. – Sealbudsman talk/contr 01:34, 19 January 2017 (UTC)

 Done The BlobsPaper.png 01:55, 19 January 2017 (UTC)
This is my version for the template. So far, if we enter {{Edition|pocket|console}}, then:
{{Edition|pocket|education}}:
But maybe, there is a better version than this. - ItsPlantseed.png ItsPlantseed | Book and Quill.png 07:27, 5 May 2017 (UTC)
I like this. Its strengths: one template that says only in pocket and console is nicer, and less confusing, than one that says only in pocket and another that says only in console.
Criticism: The rotating image seems distracting.
Idea: Parameters meaning upcoming PC and upcoming pocket, for cases where it's already in PC, but upcoming in the other edition ... what do you think
Sealbudsman talk/contr 16:41, 31 May 2017 (UTC)
Kinda basic mockup; points of difference: handles upcoming editions, notes other PE versions in a tooltip, color, formatting, alignment, no image
{{Edition|pocket|console|desktop upcoming}}
Exclusive content
{{Edition|console}}
Exclusive content
{{Edition|pocket upcoming}}
Exclusive content
Where would this appear? Could we use a parameter to make it applicable to either a page or a section? For that matter, if it had a parameter for page/section/inline, it could replace {{only}} and generate a tag instead of a msgbox. That would give us a single template for all edition-specific differences; easier to remember and easier to maintain the template and the maintenance categories. I don't think the tooltip is necessary though—unless you're anticipating greater granularity in the parameters at some future time. – Auldrick (talk · contribs) 07:35, 9 June 2017 (UTC)
Ooh, I like the idea of a template having page/section/inline parameters, and replacing 'only'. On the other hand, {{only}} could be expanded to have all that functionality too. Either way I guess. The tooltip, I was trying to balance having a short name, "Pocket Edition", with the fact that people are always tacking on "and Windows 10", as if they might not understand what Pocket encompasses. It might not be so important. We don't go crazy over the distinction in most other places on this wiki. – Sealbudsman talk/contr 11:29, 9 June 2017 (UTC)

 FYI A relevant discussion is under way at the Community Portal Talk page about the upcoming merger of Console and Pocket editions into a single product to be named Minecraft. That discussion should inform this one. – Auldrick (talk · contribs) 02:26, 13 June 2017 (UTC)
I made a template based off the one above by ItsPlantseed: {{exclusive}}


only
NixinovaGrid Book and Quill.png Grid Diamond Pickaxe.png Grid Map.png • 19:15, 16 June 2017 (UTC)
Can someone good at wikicoding make it so that {{exclusive}} can have java, console, etc, perimeters put into it; something like {{only}}? – NixinovaGrid Book and Quill.png Grid Diamond Pickaxe.png Grid Map.png • 19:34, 16 June 2017 (UTC)
{{only}} doesn't actually limit the edition parameters, although it checks for "java" and translates it to "Minecraft". Limiting the edition parameters would just add a maintenance task when new "edition"s are created. The only people who should be inserting these templates can be trusted to preview their edits, and even if they goof the template will add the page to an undefined category for the misspelled name, which somebody should catch and fix before long. – Auldrick (talk · contribs) 20:38, 16 June 2017 (UTC)
Changed wording – NixinovaGrid Book and Quill.png Grid Diamond Pickaxe.png Grid Map.png • 20:49, 16 June 2017 (UTC)