Template talk:Infobox computing device

message: this edit broke several entries in the template. See the diff, the ones that haven't had the label# data# parameters changed are in problem, for example, CPU field overrides the earlier Power field. Can anyone with edit privileges fix that? Thank you. 1exec1 (talk) 11:43, 12 January 2012 (UTC)
replies: text: Fixed. Sorry about that. Chris Cunningham (user:thumperward) (talk) 15:38, 13 January 2012 (UTC)

text: See #SoC and GPU should be added (2 years have passed!) above. A user added a comment to an old section of the talk page where nobody could see it, and then added documentation as if the template had been updated. I've undone the changes to the doc: if there's a real need for new parameters then it should be discussed here rather than in a thread from 2010. Chris Cunningham (user:thumperward) (talk) 08:56, 8 August 2012 (UTC)
replies: text:  Agreed. I left a message at your talk page too. -Kai445 (talk) 16:44, 8 August 2012 (UTC)
thread_title:  An edit broke several entries in the template 

message: I think that it is a good idea to add both the SoC and Chipset fields. A System on Chip field is highly relevant as we move towards integrated devices that employ SoC's, as I don't feel that a Chipset field would do them justice (where you would more likely find a Northbridge/Southbridge or Unified chipset, not the SoC which has a CPU/GPU on it). Both would make for good additions. -Kai445 (talk) 16:44, 8 August 2012 (UTC)
replies: text: I've added  for now. Chris Cunningham (user:thumperward) (talk) 18:45, 13 August 2012 (UTC)
replies: text:  Thanks! I think it is a good addition. -Kai445 (talk) 18:52, 13 August 2012 (UTC)
thread_title:  Proposal to add "SoC" and "Chipset" fields 

message: This box is used for tablets (see Nexus 7). The needed information is about removable storage (aka memory_card in Template:Infobox mobile phone), so please add this. Thank you. --Milan Kerslager (talk) 19:47, 30 October 2012 (UTC)
thread_title:  Missing memory_card 

message: Where it says connectivity under that I would like to add Bluetooth please 
Google9999 (talk) 13:53, 8 November 2012 (UTC)
replies: text: Bluetooth would seem to come under the umbrella of "connectivity" so I'm not sure a separate field is warranted. In any case, please discuss this before using . Thanks — Martin (MSGJ · talk) 16:03, 8 November 2012 (UTC)
thread_title:  Edit request on 8 November 2012 

message: The label (label 16) for SoC is "System-on-chip used" at the moment. Please remove "used" so that it is compliant with the other labels. It looks awkward. Kapitaenk (talk) 17:27, 17 March 2013 (UTC)
replies: text: It should be just link directly to System on a chip, without dashes, Right? [I already changed another template (used in iPhone5s)]. Maybe the a could or should(?) be skipped but still don't point to a redirect, right? I was going to do this myself but this template is protected (should I be an administrator?). I would probably not anyway since I don't see how it works.. comp.arch (talk) 10:19, 17 September 2013 (UTC)
thread_title:  SoC label 

message: Is the OS field intended to reflect the OS the computer was sold with, the one the vendor supports, or all OSes the box is capable of running? I ask because many (most?) computers are sold with MS Windows, the vendor only supports MS Windows, but they are capable of running linux, various flavors of bsd, etc. I would lean toward only listing the OS the vendor supplies, otherwise it's a lengthy list, but then what about computers that are sold with no OS? Kendall-K1 (talk) 21:55, 31 March 2013 (UTC)
replies: text: If it's unclear what a field is supposed to represent then than obvious answer would be to not list it in the infobox at all (because how is the reader then to know what the field means exactly?) I think the OS field would make sense for a smartphone, probably even for a MacBook, but not for any PC-compatible laptop. —Ruud 17:12, 4 April 2013 (UTC)
thread_title:  OS field 

message: This template is used for a number of gaming consoles and other hand=held devices. These increasingly use one of a range of USB connector types for charging and perhaps syncing. Others are significant for not doing so. I've looked at a couple of our articles on Nintendo consoles, for example Nintendo DSi, and we don't seem to say anything about the charging connectors, or the fact that some at least are apparently proprietary variants on standard USB types. Are {para|power}] or  meant for this purpose? If not, I suggest we add a parameter to this infobox, for such content. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:10, 17 August 2013 (UTC)
replies: text: Answered here. I've added this on DSi. « Ryūkotsusei » 01:11, 29 September 2013 (UTC)
thread_title:  Power connector 

message: In cases like iPhone 4S, do we really need the title listed so many times in one-inch of screen? « Ryūkotsusei » 01:11, 29 September 2013 (UTC)
thread_title:  Making the title field optional 

message: I just changed Surface 2 cpu field, that was only used, to include the Nvidia Tegra as ARM is just the core (or architecture). CPU could be used when it applies (and not the SoC). However I saw the SoC used for the Surface, should the CPU then also be used? And not mention manufacturer? Or should the fields be mutually exclusive? comp.arch (talk) 14:50, 29 October 2013 (UTC)
thread_title:  CPU vs SoC field for the actual chip 

message: Hi. This template is still using the esoteric  hack and suffering its consequences.
| above      =  
| image      = 
| caption    =  
By now, however, the underlying  is supporting two image parameters. Here is the replacement code, which can be found in up-to-date infoboxes like  and .
| image      = 
| caption    = 
| image2     = 
| caption2   = 
Best regards,Codename Lisa (talk) 13:05, 20 November 2013 (UTC)
replies: text: . Please let me know of any problems — Martin (MSGJ · talk) 13:12, 20 November 2013 (UTC)
replies: text: It sure seems like we've broken the template atm. All the video game articles with images aren't showing their images. At least the one's with a "nowrap" line involved.--SexyKick 15:03, 20 November 2013 (UTC)
replies: text: Nevermind, you fixed it right as I put this here.--SexyKick 15:04, 20 November 2013 (UTC)
thread_title:  Replace the above hack 

message: Given that this template is used more on tablets in lieu of  (which does contain it), I think we could use a memory_card field in there too. It's a simple change. ViperSnake151  Talk   00:20, 11 January 2014 (UTC)
replies: text: . I have added . Best regards, Codename Lisa (talk) 00:49, 11 January 2014 (UTC)
thread_title:  Add memory_card field 

message: After looking at some articles, the power fields seems out of place to me.  This is a request to move the "Power" field from its current location to below "Connectivity" field.  • Sbmeirow • Talk • 04:47, 3 February 2015 (UTC)
replies: text: Done Yes, it was quite obviously out of context. Best regards, Codename Lisa (talk) 16:15, 3 February 2015 (UTC)
thread_title:  Request to move "Power" field to below "Connectivity" field 

message: "Generation" field should not link to History of video games article. It makes no sense in Nexus 7 (2012 version) article for example as this is not really a game console.  — Preceding unsigned comment added by 85.193.200.21 (talk) 18:30, 14 August 2015 (UTC)
replies: text: Done Looks like that link was introduced back in 2008 when the template was expanded/updated in this edit. I will delink it as it's blatantly incorrect here. EvergreenFir (talk) Please  00:04, 28 February 2016 (UTC)
thread_title:  "Generation" field 

message: The template doc appears to be partially out of date. If I've read it correctly, there is mention of a cpuSpeed field, but attempting to use it did not produce any visible text. I also found a usage at New Nintendo 3DS of the "gpu" field, but it did not display. I updated it to "graphics" instead, which fixed it, but the documentation suggests "gpu" should have worked. -- ferret (talk) 18:55, 4 November 2015 (UTC)
thread_title:  Template doc out-dated-ness 

message: Watchers may be interested in Talk:Xbox One#RfC about the inclusion of third party values in infobox, which is discussing the use of official sales figures versus third-party estimates. One suggestion has been to add an estimated sales field to this template. -- ferret (talk) 17:43, 13 June 2017 (UTC)
thread_title:  RfC on estimated sales figures 

message: Shouldn't the parameter  be titled  for consistency? -- User-duck (talk) 21:32, 17 October 2019 (UTC)
thread_title:  "logo caption" parameter. 

message: Right now, the "related" field, if populated, puts out "Related articles" in the infobox. But the instructions suggest this is for sibling consoles (eg Nintendo Switch Lite to the Nintendo Switch, or Xbox One X to the Xbox One). I don't know if "sibling" would be understood by masses, but given we have "predecessor" and "successor", I would suggest we use "concurrent" instead. We'd also need to stress this should be consoles from the same family. The Wii or Wii U are not concurrent with the Nintendo DS line, as they are completely different console families.
Also to that end, I would suggest possibly a "family" field. We know, for example, the Xbox Series X is part of the Xbox 4th gen series, and more consoles are to come. I don't know if reusing the "related" field works here for that, whereas a "family" field that spits out "Console family" in the infobox would be good. --Masem (t) 02:38, 24 December 2019 (UTC)
thread_title:  Better name for "related" field? 

message: Some devices, such as the Toshiba AC100 have a codename. It would be a good idea to add that parameter. The infobox "mobile phone" already has it. PhotographyEdits (talk) 12:56, 8 March 2021 (UTC)
thread_title:  Add codename 

message: This parameter is unclear in its instructions, and could be (and has been) read as implying a single number ("5 years") or a range ("1998–2004"). Can anyone explain why the phrasing  is used? Is there a type of product that this template has in mind? Because for something like an iPad or a Gameboy Color, it doesn't make sense to talk about the average expected lifespan. 
Seperately, it seems like we should not use the lifespan parameter if both the release date and discontinued parameters are filled. I could amend the TemplateData to instruct that, but I want to make sure I'm not missing anything first. — HTGS (talk) 10:01, 11 July 2021 (UTC)
replies: text: This has been bothering me, too. Doesn't anyone know what the lifespan parameter was intended for? Martin IIIa (talk) 22:29, 1 September 2022 (UTC)
thread_title:  Lifespan 

message: Currently this infobox has an entry called 'developer'. Is this supposed to be a company name or a person? That is not documented. I would also like to have a 'designer' field, which might be made by renaming this, because I think there is considerable overlap between a 'developer' and a 'manufacturer'. I think that the person who made a design style for a computer is not really a 'developer'. PhotographyEdits (talk) 10:40, 9 May 2023 (UTC)
thread_title:  Developer 

message: is the parameter marketing target valid or not?  — GhostInTheMachine talk to me 18:50, 20 December 2023 (UTC)
replies: text: Alias for , fixed — GhostInTheMachine talk to me 11:53, 21 December 2023 (UTC)
thread_title:  marketing target? 

message: Quantum Processing Unit? AggressiveC (talk) 19:31, 23 December 2023 (UTC)
replies: text: (for quantum computers, of course). AggressiveC (talk) 19:31, 23 December 2023 (UTC)
thread_title:  Adding QPU?