Codename Lisa (talk | contribs) m →Webcams: * |
|||
Line 99: | Line 99: | ||
::P.S. Actually, {{para|camera}} is working nicely on these. I'd say we stick with that. |
::P.S. Actually, {{para|camera}} is working nicely on these. I'd say we stick with that. |
||
::Best regards,<br/>[[User:Codename Lisa|Codename Lisa]] ([[User talk:Codename Lisa|talk]]) 13:39, 21 November 2013 (UTC) |
::Best regards,<br/>[[User:Codename Lisa|Codename Lisa]] ([[User talk:Codename Lisa|talk]]) 13:39, 21 November 2013 (UTC) |
||
:::works for me. there are still a few extra parameters in [[EyeToy]], but the rest look fine now. thank you. [[User:Frietjes|Frietjes]] ([[User talk:Frietjes|talk]]) 15:40, 21 November 2013 (UTC) |
Revision as of 15:40, 21 November 2013
![]() | Computing Template‑class | ||||||
|
![]() | Video games Template‑class | |||||||||||
|
|
|
An edit broke several entries in the template
[1] 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)
- Fixed. Sorry about that. Chris Cunningham (user:thumperward) (talk) 15:38, 13 January 2012 (UTC)
Just my imagination or is the "GPU" field broken? I added the field in an article, but it resulted in nothing displayed. -Kai445 (talk) 06:34, 28 July 2012 (UTC)
- 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)
- Agreed. I left a message at your talk page too. -Kai445 (talk) 16:44, 8 August 2012 (UTC)
Proposal to add "SoC" and "Chipset" fields
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)
- I've added
{{{soc|}}}
for now. Chris Cunningham (user:thumperward) (talk) 18:45, 13 August 2012 (UTC)
- Thanks! I think it is a good addition. -Kai445 (talk) 18:52, 13 August 2012 (UTC)
Missing memory_card
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)
Edit request on 8 November 2012

This edit request has been answered. Set the |answered=
or |ans=
parameter to no to reactivate your request.
Where it says connectivity under that I would like to add Bluetooth please
Google9999 (talk) 13:53, 8 November 2012 (UTC)
- 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 {{editprotected}}. Thanks — Martin (MSGJ · talk) 16:03, 8 November 2012 (UTC)
Add new section
Please add discontinued please
SoC label
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)
- 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)
OS field
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)
- 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)
Power connector
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 |connectivity=
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)
- Answered here. I've added this on DSi. « Ryūkotsusei » 01:11, 29 September 2013 (UTC)
Making the title field optional
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)
CPU vs SoC field for the actual chip
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)
Replace the above hack

This edit request has been answered. Set the |answered=
or |ans=
parameter to no to reactivate your request.
Hi. This template is still using the esoteric |above=
hack and suffering its consequences.
| above = {{{logo|{{{Logo|}}} }}}
| image = {{#invoke:InfoboxImage|InfoboxImage|image={{{image|{{{Image|{{{photo|{{{Photo|}}} }}} }}} }}}|size={{{image_size|{{{ImageWidth|}}}}}}|sizedefault=frameless|alt={{{alt|}}}}}
| caption = {{{caption|{{{Caption|}}} }}}
By now, however, the underlying {{infobox}} is supporting two image parameters. Here is the replacement code, which can be found in up-to-date infoboxes like {{infobox software}} and {{infobox OS}}.
| image = {{#invoke:InfoboxImage|InfoboxImage|image={{{logo|}}}|size={{{logo_size|}}}|sizedefault=250px|alt={{{logo_alt|}}}}}
| caption = {{{logo caption|}}}
| image2 = {{#invoke:InfoboxImage|InfoboxImage|image={{{image|{{{Image|{{{photo|{{{Photo|}}} }}} }}} }}}|size={{{image_size|{{{ImageWidth|}}}}}}|sizedefault=300px|alt={{{alt|}}}}}
| caption2 = {{{caption|}}}
Best regards,
Codename Lisa (talk) 13:05, 20 November 2013 (UTC)
Done. Please let me know of any problems — Martin (MSGJ · talk) 13:12, 20 November 2013 (UTC)
- 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)
- Nevermind, you fixed it right as I put this here.--SexyKick 15:04, 20 November 2013 (UTC)
Webcams
I was able to convert Xbox Live Vision to use this template, with the exception of two missing fields: (1) platform and (2) resolution. any objections to adding these? Frietjes (talk) 00:52, 21 November 2013 (UTC)
- just found EyeToy, Kinect, and PlayStation Eye which could use these fields as well. Frietjes (talk) 00:54, 21 November 2013 (UTC)
- Hi. I am adding
|platform=
but as for resolution: We have |graphics=
, |display=
and |camera=
; a resolution parameter cannot co-exist we these. Either one should override resolution or else resolution should override one; e.g. it should either conditionally say "Camera" or "Resolution" not both. The question is: which?
- Best regards,
- Codename Lisa (talk) 13:34, 21 November 2013 (UTC)
- P.S. Actually,
|camera=
is working nicely on these. I'd say we stick with that.
- Best regards,
Codename Lisa (talk) 13:39, 21 November 2013 (UTC)
- works for me. there are still a few extra parameters in EyeToy, but the rest look fine now. thank you. Frietjes (talk) 15:40, 21 November 2013 (UTC)
You must be logged in to post a comment.