Template talk:Infobox computing device/Archive 1
![]() | This is an archive of past discussions about Template:Infobox computing device. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 |
Move
From WP:CFD: It is probably also a good idea to move Template:Information appliance to Template:Infobox IA. Jacoplane 00:05, 16 December 2005 (UTC)
Merge
This is really just an uglier duplicate of {{infobox computer}}, so I'm going to work on merging them. Chris Cunningham (not at work) - talk 23:23, 24 March 2008 (UTC)
- Do what I did for the now extinct Template:Infobox PMP: switch all Infobox computer articles to Information appliance/Infobox IA, then delete Infobox Computer. The monopoly is growing... --Jw21/PenaltyKillah 23:53, 24 March 2008 (UTC)
- "information appliance" is a horrible, contrived term and the other infobox is much more widely used. Plus, I've got some serious misgivings about {{infobox}} which haven't yet been addressed. Merging the other way makes more sense. Chris Cunningham (not at work) - talk 00:47, 25 March 2008 (UTC)
- Update: the giant merge is complete. All computing devices should now be using this template. Woo. Chris Cunningham (not at work) - talk 11:47, 18 July 2008 (UTC)
Price?
Why is there no price field, like in Template:Infobox_Motorcycle? or at least an initial price. --Hm2k (talk) 11:06, 26 August 2008 (UTC)
hCalendar microformat
{{editprotected}}
Please add the hCalendar microformat, thus:
bodyclass = vevent
titleclass = summary
class1 = organiser
the relevant date can then be included by using {{Start date}} for the Release date vlaue. Thank you. Andy Mabbett | Talk to Andy Mabbett 15:24, 26 August 2008 (UTC)
Done. Cheers. --MZMcBride (talk) 23:53, 27 August 2008 (UTC)
Protected?
Apparently this is a protected template because it's "high-risk", however reviewing the history I can't understand what justifies it to be "high-risk". I propose it no longer needs to be protected. --Hm2k (talk) 11:11, 9 September 2008 (UTC)
- FWIW, there are ~286 links to/ transclusions of this template, including a few from talk pages. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 11:15, 9 September 2008 (UTC)
- That only indicates the impact levels, not the risk levels. 87.254.83.229 (talk) 02:55, 29 December 2008 (UTC)
Prices?
What happened to WP:NOPRICES? AlistairMcMillan (talk) 10:32, 3 November 2008 (UTC)
- The WP:NOPRICES shortcut is only three days older than the merge which introduced the base price parameter here; I dare say that the template it was merged from contained the parameter before WP:NOT made any mention of prices. But yeah, it's removal time. Chris Cunningham (not at work) - talk 11:43, 3 November 2008 (UTC)
VG system merge
{{editprotected}}
I've started a sandbox for this page, in which I've merged in the relevant fields from {{Infobox Video game system}}. Just needs syced; I'll update the documentation once that's complete. Chris Cunningham (not at work) - talk 09:55, 26 November 2008 (UTC)
Done. Cheers. --MZMcBride (talk) 19:57, 28 November 2008 (UTC)
What happened to the picture of the PS3 on the side of the page? —Preceding unsigned comment added by Bozo33 (talk • contribs) 20:13, 29 November 2008 (UTC)
- Is there a reason the merged version moved "predecessor" and "successor" to somewhere in the middle of the box? IMO, it made more sense for them to be at the end. Also, it seems "Media" and "Units sold" are now output twice (13 and 23, and 9 and 30, respecively).
- BTW, you forgot to fix the double redirects created when you redirected {{Infobox Video game system}}; I fixed that for you. Anomie⚔ 22:00, 29 November 2008 (UTC)
- Yes, the duplication of "Media" and "Units sold" needs to be fixed, and I agree that "Predecessor" and "Successor" should be placed at the end. --Silver Edge (talk) 23:58, 30 November 2008 (UTC)
- You know, that template is really a pain to adjust; if you move one field, you have to renumber everything after. Here is a stab at what the requested edit should look like. For future reference, running it through this perl snippet will do that automatically: Anomie⚔ 01:54, 1 December 2008 (UTC)
perl -pwe 'BEGIN { $l=1; $d=1; } $l++ if s/^\| label\d+ */ sprintf("| label\%-6s", $l) /e; $d++ if s/^\| data\d+ */ sprintf("| data\%-7s", $d) /e;'
- You know, that template is really a pain to adjust; if you move one field, you have to renumber everything after. Here is a stab at what the requested edit should look like. For future reference, running it through this perl snippet will do that automatically:
- Yes, the duplication of "Media" and "Units sold" needs to be fixed, and I agree that "Predecessor" and "Successor" should be placed at the end. --Silver Edge (talk) 23:58, 30 November 2008 (UTC)
Output order?
I don't know that the current order (just above) is really optimal. I'll post it below, people can mess with it, and if no one else can use my perl snippet I will take that and make a new editprotected once it is worked out. Anomie⚔ 01:54, 1 December 2008 (UTC)
- Developer
- Manufacturer
- Product family
- Type
- Generation
- Release date
- Retail availability
- Discontinued
- Units sold
- Units shipped
- Base price
- Media
- Operating system
- Power
- CPU
- Storage capacity
- Memory
- Display
- Graphics
- Input
- Controller input
- Camera
- Touchpad
- Connectivity
- Online services
- Dimensions
- Weight
- Best-selling game
- Backward compatibility
- Predecessor
- Successor
- Related articles
- Web site
Disabled the editprotected request here. You gotta be more clear about what needs doing; I'm lost. --MZMcBride (talk) 02:34, 4 December 2008 (UTC)
{{editprotected}}
As I said above, "Here is a stab at what the requested edit should look like." That edit will fix the errors discussed above. This subsection was intended for further discussing the best order for the parameters, although no one seems to be particularly interested in that. Anomie⚔ 03:32, 4 December 2008 (UTC)
- I went ahead and implemented your request above - it makes sense. I put the middle section (technical specs) in a different order than what you had above - in my opinion, it makes more sense. Take a look?
- I have no idea what order things should be in, I just put the list there to let others discuss it if they want. Anomie⚔ 22:00, 4 December 2008 (UTC)
Units sold
...appears twice. Eightball (talk) 03:04, 1 December 2008 (UTC)
- Media does too. See the editprotected request above. Anomie⚔ 03:33, 1 December 2008 (UTC)
- I went ahead and fixed both of these. Should be good now. — KieferSkunk (talk) — 20:31, 4 December 2008 (UTC)
{{editprotected}}
{{{unitssold|}}}
needs to be changed to {{{units sold|{{{unitssold|}}}}}}
so that the "Units sold" section will display in articles that already have the parameter written as "units sold" instead of "unitssold", similar to "Units shipped" in template. --Silver Edge (talk) 12:32, 5 December 2008 (UTC)
Done. Cirt (talk) 23:54, 6 December 2008 (UTC)
Wikilinked titles
{{editprotected}} I believe none of the pages linked from the row titles provide necessary information, and, indeed, some of them are actively wrong (video games?) and the whole thing smack of overlinking. Please remove. 87.254.83.229 (talk) 02:58, 29 December 2008 (UTC)
- Oppose. Some of the links may be bad, but others (e.g. that for CPU are good. Let's discuss which should be kept, and which go, and not throw the baby out with the proverbial. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 12:21, 29 December 2008 (UTC)
Proposed removal of Best-selling game/top game parameter
I propose the removal of the "Best-selling game"/"top game" parameter as per WP:No original research and WP:SELFPUB.
Nearly all the video game console articles using the aforementioned parameter violates WP:NOR, because the source(s) provided with the video game does not specifically state that it is the best-selling game for the console it was released for, the source(s) only indicate that the video game sold X number of copies. I believe the Nintendo GameCube article is the only article that has a video game listed, using this parameter, with a source that specifically states that it is the best-selling video game for its respective console. If this parameter is removed, this information can be rewritten in prose elsewhere in the GameCube article.
The use of this parameter, excluding the Nintendo GameCube article, also violates WP:SELFPUB ("Articles and posts on Wikipedia, or other websites that mirror Wikipedia content, may not be used as sources"), since it is most likely that List of best-selling video games is being used as a source to determine which video game is the best-selling game for a console, which is chosen based on the game that currently has the highest sourced sales figure.
If there is consensus to remove this parameter, the following code is required to be removed from this template:
| label28 = [[List of best-selling video games|Best-selling game]]
| data28 = {{{top game|{{{topgame|}}}}}}
--Silver Edge (talk) 10:02, 16 February 2009 (UTC)
- But, it's not referring to List of best-selling video games, but the reference that the game is best-selling. There IS a list of best-selling games made by the company itself. Therefore, it's not original research.--ZXCVBNM (TALK) 19:11, 16 February 2009 (UTC)
- I agree. The link to "List of best-selling video games" is for context on sales numbers, which should always come from reliable sources. The actual item shown in that field should be corroborated by those sources, and the company's own sales figures should be reliable enough. IMO, a proper source in this case would be one that ranks the individual game's sales against other games for the system, rather than a source about that game itself, so that it can be immediately verified in one shot rather than having to search for the data. — KieferSkunk (talk) — 19:35, 16 February 2009 (UTC)
- I think I see the point of confusion here: The problem is not with the parameter itself - the label for the parameter links to a Wikipedia article, which is correct - it links to a general list of best-selling games. We count on the data on that page to be correctly sourced, of course. But the confusion seems to be in how the individual game is referenced. It's up to each game system's article to provide a source for the best-selling game item. Sources for that data can be garnered from the list article, but the item must be referenced to that source, not to the list article. So in any cases where a system article is referencing the list article directly, that should be corrected. But I think the information itself is valid and should remain, as it is significant and notable to the information about the game system. — KieferSkunk (talk) — 19:40, 16 February 2009 (UTC)
I'm a bit confused here. ZXCVBNM's comment makes little to no sense to me, as I'm pretty sure it's directed at a specific use of the parameter somewhere. Not all game platform companies release a statement about which games are best-selling on a regular basis, if at all. (They don't seem to care so much if it's not a game they published themselves.) A quick look around the console articles using this parameter shows me that it is really only encouraging people to violate WP:SYNTH, because while figuring out which game is best-selling may seem like a routine calculation, labeling a game as such is, in fact, presenting new information. And KieferSkunk, the problem, then, isn't just that the list of best-selling video games is used as a reference the individual articles, but also that the citations used solely to report the number sold in the list article is turned around and used in the console article as a source stating that what is listed is its best-selling game, while they really say nothing of the sort.
I see no compelling reason to keep this parameter then, as it is rarely used within Wikipedia standards. In the few cases where it is, the information should be mentioned elsewhere in the article anyway. KhalfaniKhaldun 20:16, 21 February 2009 (UTC)
- I can live with that. — KieferSkunk (talk) — 20:52, 21 February 2009 (UTC)
Sound, Video, and Price.. missing.
This template is used for many home computers. And those computers certainly had special and varying sound hardware (one example is Commodore 64). It also features a "display" parameter, but misses a "video" parameter or something along that line to generate something for the display. These things ought to be in the template. As well as introduction price. But it's hardlocked. So for now I will do a workaround with the base template. Electron9 (talk) 21:02, 1 May 2009 (UTC)
- I have undone your fork of the template to {{Infobox Personal computer}}. If you have issues with parameters here, please discuss them rather than forking the template. If you wish to propose changes, make them in the sandbox and provide a rationale here. I have imported the changes you made from the recent fork into the sandbox to provide a starting point. Chris Cunningham (not at work) - talk 12:07, 3 May 2009 (UTC)
- Rationale:
- 0) Home computers had special and varying sound hardware. Compare ABC 80 and Commodore 64.
- 1) The price at the introduction year helps to comprehend it's place in the marketplace.
- The price matter has already been pointed out by Hm2k in 2008-08-26 without any action. And sound parameter is still missing, but my template got redirected to the locked template that still miss that and price. The sound paramter is needed to indentify the capabilities on the product category. Home computers had its "soundcard" builtin in ~95% of the cases. I get the feeling the editors of this template won't listen. Electron9 (talk) 22:33, 3 May 2009 (UTC)
- I don't disagree with either of those suggestions. You're mistaken about the base price parameter: it was added after that comment was made, and then removed again. I reckon that including an introductory price is fair enough. I don't see there being any ground for the assertion that "the editors of this template won't listen" to changes, but the solution is not to fork the template in any case. I'll see whether I can get both of these changes implemented. Chris Cunningham (not at work) - talk 08:10, 4 May 2009 (UTC)
Update
{{editprotected}}
Requesting sync with the sandbox to re-add a parameter for introductory price (re-labelled to ensure that it is treated as a historical rather than current value, per WP:NOPRICES) and add a "sound" parameter for built-in sound hardware. Neither should be controversial. Chris Cunningham (not at work) - talk 09:38, 4 May 2009 (UTC)
Done don't forget about the docs btw. —TheDJ (talk • contribs) 11:33, 4 May 2009 (UTC)
Dimensions not working??
MSI Wind Netbook has an infobox specifying the dimensions of the computer but it's not visable. And the template source code (label27) specifies it. Aswell as the documentation. This just seems quite odd. Bug? Electron9 (talk) 14:00, 7 May 2009 (UTC)
- Attributes are case-sensitive. When {{infobox Computer}} was merged here, its own parameters (which were capitalised) were supported for compatibility purposes; however, this was not extended to parameters not supported by the old {{infobox Computer}}, such as {{{dimensions}}}. I've fixed the article by making all of its parameters lowercase. Chris Cunningham (not at work) - talk 09:04, 8 May 2009 (UTC)
Sound not working
Hi, I'm over at iPhone and I've noticed that the sound parameter is not showing up. Is this my fault or the templates'? (And wouldn't "audio" be a bit more formal?) Thanks in advance, HereToHelp (talk to me) 23:01, 11 May 2009 (UTC)
- Never mind; fixed it myself.--HereToHelp (talk to me) 22:04, 12 May 2009 (UTC)
{{editprotected}}
Please don't replace the names of parameters on already-deployed templates without providing backwards compatibility. {{{audio|}}} needs to be changed to {{{audio|{{{Sound|}}} }}}. Chris Cunningham (not at work) - talk 12:56, 20 May 2009 (UTC)
Done — Martin (MSGJ · talk) 14:15, 20 May 2009 (UTC)
- I'm fine with backwards compatibility, but I prefer the term "Audio" to be displayed to the user in the infobox. Is there a way to do both?--HereToHelp (talk to me) 02:54, 23 May 2009 (UTC)
- I now found several articles with non-working audio, ohh now it's sound, or maybe it was audio?. Please stay with ONE choice. Or update all articles using the template yourself. Electron9 (talk) 21:21, 13 November 2009 (UTC)
- I'm fine with backwards compatibility, but I prefer the term "Audio" to be displayed to the user in the infobox. Is there a way to do both?--HereToHelp (talk to me) 02:54, 23 May 2009 (UTC)
- I still don't believe the sound is working any more. Both the example and documentation needs to be updated, or the person who broke all of the
- computer templates needs to revert their changes. It's unacceptable to merge templates and provide a bad example. It's more unacceptable to change templates
- and not test the impact of those changes.
- There are enough problems policing facts to be running around fixing obvious errors that simple testing would find.
- I'd recommend splitting computer and information appliance, the two subjects are very different, since computers go back several thousand years,
- there are analog computers and other varieties of computing devices (some mechanical) that will require new infobox types, distinct from
- [[Information Appliance<]], which is stritcly a digital computer thing. (Ultimately, templates that inherit from each other is a more useful
- solution, but I'm not proposing that here)rhyre (talk) 14:24, 29 June 2010 (UTC)
hProduct microformat
{{editprotected}}
| bodyclass = vevent
| titleclass = summary
to:
| bodyclass = hproduct vevent
| titleclass = fn summary
and add:
| class2 = brand
| class8 = price
Thank you. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 13:42, 26 May 2009 (UTC)
Done — Martin (MSGJ · talk) 12:45, 27 May 2009 (UTC)
- Great. Thanks. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 20:53, 27 May 2009 (UTC)
hProduct microformat and identifier (UPC, etc)
Can someone add a section for several hProduct identifer rows, for UPC and such? Something similar to:
| label35 = identifier1
| class35 = identifier
| label36 = type1
| class36 = identifier::type
| label37 = identifier2
| class37 = identifier
| label38 = type2
| class38 = identifier::type
Int21h (talk) 23:35, 27 June 2009 (UTC)
Help further define service field
Currently, the "service" field is defined as "online service(s) offered". This apparently is quite vague. In the case of a smart phone, such as the iPhone, additional applications could be installed, and therefore increase the online services. I can easily see someone add, for example, a Twitter application, and then add "Twitter" to the service field of the smart phone. In other words, the service field could end up being huge and virtually meaningless. I want to avoid something like this from happening. The only way to fix this is to write better documentation for the "service" field, and just about all other fields in this infobox. Groink (talk) 02:51, 4 August 2009 (UTC)
Merge with {{Mac specs}}
{{editprotected}}
Requesting sync with the sandbox to allow for {{Mac specs}} to be merged here. No new parameters, simply support for the attribute titles used in that template. Chris Cunningham (not at work) - talk 10:44, 6 August 2009 (UTC)
Not done The hcard classes are different between the sandbox and the original. I'm not sure if that is intentional —TheDJ (talk • contribs) 15:26, 6 August 2009 (UTC)
- Wasn't deliberate. Now fixed. Re-enabling. Chris Cunningham (not at work) - talk 08:26, 7 August 2009 (UTC)
- It appears TheDJ already merged it. At least there is no difference between the current sandbox and the template. MBisanz talk 20:24, 7 August 2009 (UTC)
"Supports:" field
Any objections if I add an optional "Supports:" field? That would be useful for media players, e-book readers etc. to indicate what content formats or other standards are supported by the device, e.g.: "Supports: MP3, WAV, OGG". Sandstein 08:32, 7 October 2009 (UTC)
- Never mind, I see that there is already a "Music:" field for this, although that is a bit counterintuitive for e-book readers, as in Sony Reader. Sandstein 08:41, 7 October 2009 (UTC)
Hearing Aid Compatibility
I am adding hearing aid compatibility rating information on phones as I find it. A while ago I added it to the "mobile phone" infobox, but now I see many (smart) phones are using the "information appliance" infobox instead. Please add 'hac=' to information appliance, or otherwise indicate the distinction between when this template should be used instead of mobile phone.
(some reference pages: Motorola Droid, HTC Hero, Blackberry Storm, Treo 700p, Treo 700w, Treo 650, Treo 755p, Palm Treo Pro)
Dsh13 (talk) 20:37, 24 October 2009 (UTC)
Specific absorption rate
It would probably be in the best interest, and safety, to add Specific Absorption Rate (SAR) to wireless telephone devices. We know that various governments have placed limits on radiation levels, but how much is really too much? Clearly, the cell phone is an important tool that many people use daily. But we also don't want to use phones with an SAR of 1.6 W/kg if the maximum SAR limit is 1.6 W/kg. So how much is too much? Could it be that 1 W/kg is too much? The lower exposure would be better but at the same time would lower SARs mean greater inadequate phone service? --Bushido Hacks (talk) 20:46, 28 October 2009 (UTC)
- If this figure is widely available enough for devices that there is genuine comparative value in adding it to infoboxes then this could be considered, but we shouldn'd add it for reasons like "it's in the public's best interest". It's in the public's best interest not to use Wikipedia as a health guide. Chris Cunningham (not at work) - talk 23:08, 28 October 2009 (UTC)
- CNet has compiled a list of SAR values on just about every phone that is currently on the market in the United States and have matching FCC ID numbers to query information. From this data, comparative values can be made available. --Bushido Hacks (talk) 06:41, 29 October 2009 (UTC)
Remove price parameter
This is confusingly mentioned in an earlier thread. Shouldn't the price parameter be removed because of WP:NOPRICES? -- Alan Liefting (talk) - 00:11, 24 January 2010 (UTC)
- WP:NOPRICES is reference to street prices, not to the price often used with the template, such as MSRP. Daniel.Cardenas (talk) 00:50, 24 January 2010 (UTC)
- The previous statement is not correct, or is at least out of date. NOPRICES makes no mention of a distinction between street prices and RRPs or SRPs. What it says is that prices should only be included WITH GOOD REASON, ie if independent reliable sources suggest that the price is worth mentioning. This is not an argument to remove the parameter, but it is an argument to change the template instructions to make clear that using this field should be the exception rather than the norm. I will update the instructions now. GDallimore (Talk) 11:03, 8 April 2011 (UTC)
Model numbers
What happened to the model number field? Many Macintosh models were only listed in this field used in the Mac spec template, not in the article. Can we please get this added back?--Mac128 (talk) 16:48, 20 March 2010 (UTC)