Template talk:Infobox software/Archive 7
Template-protected edit request on 20 October 2016
Two horizontal separators between Initial release and Stable release on MobileDoes anybody know why there are two separator between Initial and Stable release when browsing an Infobox-software on mobile? Alcotor (talk) 15:37, 7 November 2016 (UTC) Cross-posted to WP:VP/T Can anyone figure out why pages are added to Category:Articles which use infobox templates with no data rows if
no repositories bug "no%20value"see for yourself : https://en.wikipedia.org/w/index.php?title=Bzip2&oldid=757243753 another example : https://en.wikipedia.org/w/index.php?title=Lzip&oldid=744171043 — Preceding unsigned comment added by 176.182.238.130 (talk) 12:14, 31 December 2016 (UTC)
Official websiteHi, I think there's a bug in this infobox when there's two official websites in a Wikidata item: Special:Permalink/759631374. Cheers. --Thibaut120094 (talk) 07:54, 17 January 2017 (UTC)
Additional parameterMany software tools described with that template are used to create images; in Commons are lists like c:Category:SVG created with ... templates and c:Category:Created with ... templates how such images are created with such software tools. How about a possibility to show about the usage of the software? An Infobox-parameter like "usage={{PAGENAME}}" could link to a creation template at Commons where always the categories with the images are shown. A tool like CorelDRAW would show
Repo property data is poorly formattedCurrently on GNU Units this infobox is very wide, as it want's to show:
These are Wikidata properties. Firstly, the external link is not formatted. Secondly, it is unreasonably wide, and does not wrap. I'm not sure the appropriate method to fix this. +mt 20:39, 9 March 2017 (UTC)
Official website (2)On MongoDB, the official website in the infobox is rendered as: www.mongodb.org/,%20https://www.mongodb.com/. This is most likely because wikidata:Q1165204 for MongoBD has two external links specified. While this can be fixed there by removing one, can we fix the template so that only one value is used instead of querying all - which forced them to be merged by a comma and used as one (broken) value. Krinkle (talk) 06:48, 23 March 2017 (UTC)
Original authorsThe above phrase is redundant. By definition, an author is the one who created the work. I would change it, but there does not seem to be a way here. — Preceding unsigned comment added by BeenAroundAWhile (talk • contribs) 23:46, 1 April 2017 (UTC)
Repo revisitedIn cases where the
Initial release versionCan we have a flag for this as well, like we have for "latest release version"? Not all software are initially released as version 1.0.0. Thanks! SharkD Talk 15:14, 11 April 2017 (UTC)
Video games and infoboxesThere is talk at Template_talk:Infobox_video_game#missing_fields on which infobox to use for open source video games. I thought many of you might be interested. SharkD Talk 11:36, 25 May 2017 (UTC) Add title to the images
Please add
RFC: Initial releaseHello. I am calling upon the community to review and redefine the purpose of the "Initial release" field of the infobox (
This description is at best problematic: When someone sees the phrase "initial release", he or she does not take it to mean "RTM of 1.0" and these two are not synonymous right now. We must revise this state of affair. But which way?
Best regards, PollPlease start your verdicts with "Option 1" or "Option 2". Because this infobox is transcluded 12,528 times, the dominant verdict must be have a margin of 10.
Discussion
"Repository" field: bad handling of null valuesSpotted: Cobian Backup. Whether there is "| repo =" in the code or not, the result is such a link: no%20value. Google gives more examples. 195.187.108.4 (talk) 14:13, 24 August 2017 (UTC) use wikidata for developer, license by defaultPlease use wikidata for developer and license by default (as in Template:Infobox OS). Please change the code as followed, | data2 = {{{developer|{{#invoke:WikidataIB|getValue|P178|fetchwikidata=ALL |onlysourced=false}}}}}
| data16 = {{{license|{{#invoke:WikidataIB|getValue|P275|fetchwikidata=ALL |onlysourced=false}}}}}
Thanks you. --Ans (talk) 14:13, 22 August 2017 (UTC)
IndentPlease indent the
Template-protected edit request on 25 October 2017
Add | rowstyle4 = display: none; to avoid the extra space between the third and forth row (i.e. between "Developer(s)" and "Stable release" here). – Srdjan m (talk) 08:32, 25 October 2017 (UTC)
|
 | This edit request to Template:Infobox software has been answered. Set the |answered= parameter to no to reactivate your request. |
Please do the following changes
- {{Infobox software/stacked}}:
LatestLastrelease(s)→Final release(s)(two instances) - {{Infobox software/simple}}:
LatestLastrelease→Final release
- {{Infobox software/stacked}}:
"Last" is ambigous with "latest", "final" resolves this. Please note that a previous request for this by Nurg went unnoticed. Paradoctor (talk) 10:22, 22 February 2019 (UTC) Paradoctor (talk) 10:22, 22 February 2019 (UTC)
Not done. "Final" implies that there will be no future versions of that software. This would be misleading for software that is continously developed on. "Latest" refers to the most recently released version, which is more what we want to express. Lordtobi (✉) 10:51, 22 February 2019 (UTC)
Done I initially misunderstood your request because it appeared as though you wanted to have "Latest" changed to "Final". I assume these are typos. The templates are now fixed. Lordtobi (✉) 10:54, 22 February 2019 (UTC)
- Gah! Sorry about the confusion. Paradoctor (talk) 11:17, 22 February 2019 (UTC)
Allowing long labels to break onto a second line with an optional parameter
There are some cases where the infobox label area is much larger than necessary. For example Operating system makes the width of the label column extremely wide. It would be helpful to allow the label column to "wrap" so it would look like this:
I know this is technically possible, but before I write it up I wanted to make sure there was support to include this option. Please let me know if any of this is unclear. - PaulT+/C 16:56, 7 April 2019 (UTC)
More use of wikidata
This template should use more data form wikidata as done ine the french version https://fr.wikipedia.org/wiki/Mod%C3%A8le:Infobox_Logiciel
This allow to update latest release and other things in one place instead of editing the page in all translations.
--Agouti (talk) 08:34, 10 April 2019 (UTC)
Merging Template:Infobox web browser
| This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
I made changes in the sandbox to support the merger of Template:Infobox web browser per this TfD. The discussion only mentioned bringing over the engine parameter, but I also transferred the included with parameter as well since the web browser infoboxes use it and it seems useful for other software. --Abgnac (talk) 18:10, 13 April 2019 (UTC)
- Abgnac, it appeared as though the
|engine=parameter was broken due to a missing pipe within the if-check at the end of the line beginning with|data8=. Note that|engines=was working fine. I believe to have fixed it (diff), so please review my changes before I push it to live. Regards, Lordtobi (✉) 18:34, 13 April 2019 (UTC)- Good catch. It appears to be working correctly now. --Abgnac (talk) 18:50, 13 April 2019 (UTC)
- Aight. Done. Lordtobi (✉) 18:56, 13 April 2019 (UTC)
- Aight.
- Good catch. It appears to be working correctly now. --Abgnac (talk) 18:50, 13 April 2019 (UTC)
Multiple website values
Integrated Performance Primitives website link renders incorrectly because P856 property for WikiData entry used on that page has multiple values. From the discussion page, it seems that the property does not have single value constrain intentionally, and this template has to be changed to support multiple values. — Preceding unsigned comment added by IamNikita (talk • contribs) 23:57, 6 July 2019 (UTC)
Adding development status for compatibility with Template:Infobox web browser
Copy the sandbox content to the main template. I added the development status parameter for compatability with Template:Infobox web browser which is currently being merged into this template after a TfD. This parameter seems to have been forgotten in the main merger performed by Abgnac. -- Trialpears (Talk) 22:03, 13 July 2019 (UTC)
Add Maintainers field
Hello, some projects (especially open source) have maintainers. They don't need to be the original author. Can someone add this field? --Emil Engler (talk) 02:13, 7 August 2019 (UTC)
Proposal to Add a field to link to Changelog or release Notes
— Preceding unsigned comment added by Tech201805 (talk • contribs) 11:18, 20 September 2019 (UTC)
website parameter - consider adding archive url property (P1065)
In Netscape_Navigator website is dead (archive.netscape.com). I've added archive url (Property:P1065), but infobox doesn't use that wikidata property. End time could be recognized as well (both "archive url" and "end time" wikidata qualifiers are suggested when changed website property is being tried to publish). MarMi wiki (talk) 20:05, 22 September 2019 (UTC)
Version Number and Wikidata
The excuse given in the FAQ about not using Wikidata for version numbers is bogus. Wikidata is a centralized source, and any vandalism will be visible in ALL lingual editions of wikipedia, not only the english one. This means also, that it is much faster noticed and corrected in Wikidata. There is really no point in not using Wikidata for such data. --91.89.138.29 (talk) 16:49, 24 September 2019 (UTC)
Infobox title vs page title and redirections
I migrated Cura (software) to use the "Template:Latest stable software release" system for specifying the version number. The page title is "Cura (software)" but the infobox title is simply "Cura". When I first created the template, I used Template:Latest stable software release/Cura (software) but then moved it to Template:Latest stable software release/Cura when the former didn't work. However, now when I press "[±]" to edit the latest version, it opens the redirect page, not the final page. Is there some way of specifying which page gets opened when "[±]" is pressed?S-1-5-7 (talk) 05:04, 25 September 2019 (UTC)
- @S-1-5-7: Remove " (software)" from article parameter (leave only "Cura"). MarMi wiki (talk) 18:58, 5 October 2019 (UTC)
sanity check for the discontinued parameter
discontinued must be yes or omitted. Instead, the article Adobe Flash passed the URL of Adobe's announcement of future deprecation and end of life: it was not shown in the infobox, instead as a ref without the usual link [1]. Please consider adding a red error at runtime for the wrong parameter usage, as seen for other templates. It would have been helpful to spot the problem earlier. --151.70.49.182 (talk) 08:04, 1 December 2019 (UTC)
Why P1324 and P408 are special case?
I couldn't figure out. --Ｔｅｓｔｍｅｎｔ７７７ (talk) 00:43, 2 December 2019 (UTC)
- "Special case" in what way? They don't seem "special" to me at all. MarMi wiki (talk) 18:50, 2 December 2019 (UTC)
Adding Alexa To Google
There is an issue when adding alexa to Google. It is acting as an invalid parameter.
WeTalkWiki 14:24, 11 December 2019 (UTC)
Add support status field
Software generally has a support period, where if a user is using a supported version then they can reasonably assume that bugs will be fixed or addressed as they arise. This information is of general interest to people who are reading the article for a piece of software. Some more specialised software templates have a field for this (such as a the support_status field in Template:Infobox OS version) but this generic software infobox template does not have such a field. I think we should add an optional support_status field in line with the one used in infobox OS version et al. which can be used to list the versions of software that are supported. Thoughts? --Deskana (talk) 11:33, 29 January 2020 (UTC)
Support. Came here for the same. And would say we need a "End-of-life date" field. Tabdiukov (talk) 00:31, 3 February 2020 (UTC)
- I made a prototype modification in my userspace, User:Deskana/infobox software, which seems to be working just fine on User:Deskana/infobox software/kubernetes. I'll probably copy it over here in the next few days. --Deskana (talk) 22:38, 6 February 2020 (UTC)
- I am not a fan whatsoever of covering parameters in this template (or apparently in the other) which need routine changing/maintenance like this one. The real general reader is one who doesn't understand what the software is or does, not one who cares about the version numbers that are indicated, and that reader is also not served by this information. --Izno (talk) 22:41, 6 February 2020 (UTC)
Adding parameter 'number of users' to the template
The infobox is used in pages of most of the apps and software pages. I propose the addition a new parameter num_users (number of users) to the template. The parameter will depict number of active registered users. - Sanyam.wikime (talk) 17:19, 12 February 2020 (UTC)
- That's too vague. Not all users are "registered users". And it is too difficult to have reliable information. Vincent Lefèvre (talk) 17:40, 12 February 2020 (UTC)
"Publisher" section
Can we add a section for a publisher? "Original author" just isn't a true description for some publishers. AntiGravityMaster (talk) 18:04, 21 March 2020 (UTC)
Empty "Usage" section
Recently, an empty "Usage" section displays in the infobox in many articles, for example PuTTY, Far Manager or Firefox. Can you please take a look? I do not have the privileges to edit this template. --Prikryl (talk) 07:06, 20 April 2020 (UTC)
- Fixed here. Nardog (talk) 12:38, 20 April 2020 (UTC)
- Thanks. --Prikryl (talk) 13:51, 20 April 2020 (UTC)
Wikidata website info
Was it really such a smart idea to automatically pull in official websites from Wikidata? I've just been tearing my hair out trying to remove a link that has become an attack site. It is not obvious where it is coming from. I really don't see the point of storing this on Wikidata. SpinningSpark 11:52, 27 March 2020 (UTC)
- While I think it is a good idea to pull this information from Wikidata, it needs to be more clearly/prominently documented. Also, the current implementation doesn't handle items with multiple websites correctly. Take a look at Node.js for example. --Alex Rosenberg (talk) 16:04, 20 April 2020 (UTC)
- Update: The multiple website bug was fixed by IceWelder --Alex Rosenberg (talk) 18:05, 20 April 2020 (UTC)
Can you clarify that other than repo the data is meant for binary/end user versions?
Some programs might have a source code version that is newer than the actual release/binary.
I assume it applies more for independent developers due to various reasons such as:
- They don't care for source code QA (which is "nice to have") like they care for end user QA (which is a must and lack of it might cause abandonment of the program and bad press).
- They care more for developers than for end users.
I saw such a case in which an editor entered the latest release version/date and license of the source code rather than the binary.
Since this is Wikipedia and not development hub, will you consider adding a verification that all fields, other than repo, are meant for binary/end user releases?
-Cardace (talk) 21:49, 23 April 2020 (UTC)
Issues with "platform" parameter
Bash_(Unix_shell) now has an extra Platform section, linked to Video game#Platforms under "Usage", as does Godot_(game_engine), although I assume the link to Computing platform is the extra one in that case. I assume this is a side effect from merging with Template:Infobox video game engine in Special:MobileDiff/951532688, so pinging Primefac in hopes you know a way to untangle them! (I assume some sort of conditional is needed to swap out the label depending on the type of article, and remove the second platform parameter definition, but don't know how to surely distinguish one from the other at first glance, and it's too late at night to try writing code in a language I don't know anyway...) Thanks in advance! —{{u|Goldenshimmer}} (they/them)｜Talk｜Contributions 02:59, 23 April 2020 (UTC)
- This has been fixed: Special:MobileDiff/953026477. Thanks! —{{u|Goldenshimmer}} (they/them)｜Talk｜Contributions 05:59, 26 April 2020 (UTC)
Template-protected edit request on 16 May 2020
| This edit request to Template:Infobox software has been answered. Set the |answered= parameter to no to reactivate your request. |
Can we add belowstyle and below to add footnotes for apps. Smithr32 (talk) 11:50, 16 May 2020 (UTC)
Not done: please make your requested changes to the template's sandbox first; see WP:TESTCASES. – Jonesey95 (talk) 13:52, 16 May 2020 (UTC)
Some unnecessary game engine fields
Through the merger of {{Infobox video game engine}}, this template has received various field relating to video game engines, however, some of these seem rather unnecessary:
- Main genre(s): An engine usually does not have a fixed genre. With proprietary engines, the dominant genre using it usually stems from the developers' preference, not the engine's limitations. Engines that are available to the public (Unity, Unreal Engine, GameMaker, etc.) can have endless genres, depending on how the thousands of potential developers use it. There usually is no single "main genre" that an engine could be reduced to.
- Major game(s):. With proprietary engines, these would be all of the handful of games the engines' developers created themselves. Publicly available engines could list thousands of possible games. Reducing them to just a few cherry-picked entries constitutes original research.
- Latest game: Unlike {{Infobox video game series}}, wherein this parameter would only need to be updated once every few years, games using a particular engine tend to be released every other week, or even more frequently with more popular engines (Unity's developers claim that half of all games user their engine). Using Unity as an example, not only would we need to index every new (notable) game that uses it, we would have to constantly update this field. This is unnecessary work and also prone to vandals inserting their games ("List of ENGINE games" articles are already polluted frequently).
- Removing these would only leave Earliest game, which has similar problems as the "Latest game" parameter. It is rather difficult (let alone verifiable) to point out the very first game to use an engine that has been available to the public for years. GameMaker used to list Clean Asia! as its first. Clean Asia! was released in "ca. 2007" (I have since fixed this), the same year as Mondo Medicals, so it was unclear which game released first. Furthermore, GameMaker was first released in 1999, and I would doubt that it saw no game released for eight years straight. Again, original research is at play here. If there really is one identifiable and verifiable first game, it should be mentioned in the body instead.
I would advocate removing all of these, with emphases on the first three. Thoughts? IceWelder [✉] 11:21, 25 April 2020 (UTC)
- The consensus after the TfD was to delete the template and replace it with {{Infobox software}} (see Wikipedia:Templates_for_discussion/Log/2020_March_18#Template:Infobox_video_game_engine) Christian75 (talk) 08:51, 26 April 2020 (UTC)
- I am aware of the merger situation (which is the first statement in my original comment). These fields had the same issues on the old template but there was no review, and the template only survived a couple of days. There was consensus to delete the template, but it was merged instead. There was no consensus to keep these specific fields. IceWelder [✉] 09:21, 26 April 2020 (UTC)
- I can see the thread in the TFD that lead to a merge rather than full deletion, but I can also see how some of the discussion might have been misinterpreted to lead to that conclusion. Primefac? --Izno (talk) 12:57, 26 April 2020 (UTC)
- Couldn't rightly say why I merged instead of replacing the transclusions. What I can say is that when I do merge, I prefer to do as little on-article editing, which is why I converted it to a redirect (I only needed to make one article-space edit after the merge was complete). I clearly misread the close, and I therefore see no prejudice against undoing my merge on this template. Let me know if I can be of any further assistance (e.g. using my bot to update the transclusions). Primefac (talk) 02:05, 29 April 2020 (UTC)
- @Primefac, Izno, and Christian75: I've boldly removed the field as there was no opposition. Primefac, if you have the time, could you configure PrimeBOT to remove the four former fields? IceWelder [✉] 15:33, 21 May 2020 (UTC)
- Done. Primefac (talk) 17:39, 21 May 2020 (UTC)
- @Primefac, Izno, and Christian75: I've boldly removed the field as there was no opposition. Primefac, if you have the time, could you configure PrimeBOT to remove the four former fields? IceWelder [✉] 15:33, 21 May 2020 (UTC)
- Couldn't rightly say why I merged instead of replacing the transclusions. What I can say is that when I do merge, I prefer to do as little on-article editing, which is why I converted it to a redirect (I only needed to make one article-space edit after the merge was complete). I clearly misread the close, and I therefore see no prejudice against undoing my merge on this template. Let me know if I can be of any further assistance (e.g. using my bot to update the transclusions). Primefac (talk) 02:05, 29 April 2020 (UTC)
- I can see the thread in the TFD that lead to a merge rather than full deletion, but I can also see how some of the discussion might have been misinterpreted to lead to that conclusion. Primefac? --Izno (talk) 12:57, 26 April 2020 (UTC)
- I am aware of the merger situation (which is the first statement in my original comment). These fields had the same issues on the old template but there was no review, and the template only survived a couple of days. There was consensus to delete the template, but it was merged instead. There was no consensus to keep these specific fields. IceWelder [✉] 09:21, 26 April 2020 (UTC)
Discontinued not used when containing a reference
discontinued
For technical reasons, anything for this parameter has the same effect, be it "yes", "no" or anything else. To nullify the effect of this parameter, you need to omit it.
Actually, that's not true. If you include a reference (in order to prove, at least to editors, that it wasn't declared in vain) then it nullify this parameter as if you omitted it. -Cardace (talk) 17:45, 28 May 2020 (UTC)
Taking more data from wikidata
As of this writing, only engine, website and repo are taken from wikidata.
Will you consider also taking from there publication date (date of first release), software version identifier, etc.?
Otherwise, people just add duplicated info (same data, and possibly even references for this data, in wikidata and Wikipedia in multiple languages), which is inefficient, time consuming and might also cause inconsistencies.
-Cardace (talk) 20:58, 23 April 2020 (UTC)
Hi there,
I have an idea for the Software and Operating system Infoboxes, but I should discuss it for its possible bugs and side effects here.
What do you think about fetching the "Software(or OS) latest(preview) version" and "Software(or OS) release(preview) date" data from Wiki Commons items(WikiData)? In the following Infoboxes
and
As such this is the case for "Repository" URI item.
I should note that "version" and "date" is a frequently changing item, and this idea has the advantage that with one change in this (WikiData) item, all Wiki Infoboxes (in all languages English, Dutch,German, Persian, Arabic, Chinese, etc.) change at once, only by a single modifying.
Are there any problems (or bug producing) with this idea?
Thanks, Hooman Mallahzadeh (talk) 05:13, 27 May 2020 (UTC)
- You're not the only one with this idea. See above as this this was already asked. Now we just need someone to agree to implement it. -Cardace (talk) 17:53, 28 May 2020 (UTC)
- @Cardace: Thanks for your reply, I don't have permission to edit this template page, but it is so simple and elementary, just like these codes:
| data6 = {{#if:{{{repo|}}}
|{{{repo|}}}
|{{#if: {{#property:P1324}}
|{{#ifeq: {{wikidata|property|P1324|best|format=%p}} | none
|{{wikidata|property|P1324|best|format=%p}}{{EditAtWikidata|pid=P1324}}
|{{Plainlist|<ul><li>{{URL|{{wikidata|property|P1324|best|format=%p}}}}</li></ul>}}{{EditAtWikidata|pid=P1324}}
}}
}}
}}
- Simply change "repo" to "software version(date)", and change "#property:P1324" to an item in WikiData.
- Thanks again, Hooman Mallahzadeh (talk) 08:49, 29 May 2020 (UTC)
- But it is possibly better to make a "secondary template" named something like "Template:articleTemplateData_Or_WikiData" that takes as argument "version/releaseData data" and "WikiData ID" and checks article's TemplateData, if it is empty, then checks WikiData and outputs something like the above codes, therefore, some "template" does the above mentioned code.
- "Template:articleTemplateData_Or_WikiData" should have two parameters (1) Article template data (may be empty) and (2) ID of and item in WikiData.
- Also "Simple Infobox" and "Stacked Infobox" takes as input data something from this "second template"'s output.
- Thanks again. Hooman Mallahzadeh (talk) 05:18, 30 May 2020 (UTC)
| This edit request to Template:Infobox software has been answered. Set the |answered= parameter to no to reactivate your request. |
This is also a good idea to implement. Would some one take care of this idea, at least for «Infobox software/simple»?
Thanks again. Hooman Mallahzadeh (talk) 15:23, 2 July 2020 (UTC)
- Not done: please make your requested changes to the template's sandbox first; see WP:TESTCASES. – Jonesey95 (talk) 16:11, 2 July 2020 (UTC)
Lead developers vs developers?
If one has a source for a name of a lead developer on a piece of software, but there are many other developers as well, how would one phrase that in the infobox? JimKaatFan (talk) 20:00, 17 August 2020 (UTC)
- To editor JimKaatFan: parentheses have been used, such as "Jacob Mentor (lead)". Hope this helps! P.I. Ellsworth ed. put'r there 02:48, 24 August 2020 (UTC)
Better control for wikidata (disable or alternative QID)
When an article mentions forks or bindings, multiple instances of this template may be used to refer to different pieces of software. This creates a problem as the same wikidata entry is used for all these boxes, filling incorrect values for stuff like website and repository link. There should be a way to either disable wikidata-taking or to specify another QID.
I checked the documentation for the wikibase parserfunctions, and it seems that neither option is not hard to implement. To make another ID available, just add |from={{{qid|}}} to all the invocations of the parser func (an empty value gives the same behavior as not specifying one in this case). To disable the taking all together, just add {{{noqid|}}} to all the if-empty-then-wikidata checks like {{#if:{{{repo|}}}{{{noqid|}}}|{{{repo|}}}|...}}. And of course we can do both.--Artoria2e5 🌉 02:20, 2 July 2020 (UTC)
| This edit request to Template:Infobox software has been answered. Set the |answered= parameter to no to reactivate your request. |
Please apply the following diff to the source code of the template:
Extended content
|
|---|
@@ -51,12 +51,12 @@
}}
}}
| label6 = [[Repository (version control)|Repository]]
-| data6 = {{#if:{{{repo|}}}
+| data6 = {{#if:{{{repo|}}}{{#ifeq:{{{qid|}}}|none|-}}
|{{{repo|}}}
- |{{#if: {{#property:P1324}}
- |{{#ifeq: {{wikidata|property|P1324|best|format=%p}} | none
- |{{wikidata|property|P1324|best|format=%p}}{{EditAtWikidata|pid=P1324}}
- |{{Plainlist|<ul><li>{{URL|{{wikidata|property|P1324|best|format=%p}}}}</li></ul>}}{{EditAtWikidata|pid=P1324}}
+ |{{#if: {{#property:P1324|from={{{qid|}}}}}
+ |{{#ifeq: {{wikidata|property|{{{qid|}}}|P1324|best|format=%p}} | none
+ |{{wikidata|property|{{{qid|}}}|P1324|best|format=%p}}{{EditAtWikidata|pid=P1324}}
+ |{{Plainlist|<ul><li>{{URL|{{wikidata|property|{{{qid|}}}|P1324|best|format=%p}}}}</li></ul>}}{{EditAtWikidata|pid=P1324|qid={{{qid|}}}}}
}}
}}
}}
@@ -69,10 +69,10 @@
| label10 = [[Software engine|Engine]]{{#if: {{{engines|}}} |s}}
| data10 = {{#if: {{{engines|}}}
|{{{engines}}}
- |{{#if:{{{engine|}}}
+ |{{#if:{{{engine|}}}{{#ifeq:{{{qid|}}}|none|-}}
|{{{engine|}}}
- |{{#if: {{#property:P408}}
- |{{Plainlist|<ul>{{wikidata|properties|P408|best|format=<li>%p</li>}}</ul>}}{{EditAtWikidata|pid=P408}}
+ |{{#if: {{#property:P408|from={{{qid|}}}}}
+ |{{Plainlist|<ul>{{wikidata|properties|{{{qid|}}}|P408|best|format=<li>%p</li>}}</ul>}}{{EditAtWikidata|pid=P408}}
}}
}}
}}
@@ -104,12 +104,12 @@
| label24 = [[Alexa Internet|Alexa]] rank
| data24 = {{#if:{{{alexa|}}}|{{nowrap|{{{alexa|}}}}}}}
| label25 = Website
-| data25 = {{#if:{{{website|}}}
+| data25 = {{#if:{{{website|}}}{{#ifeq:{{{qid|}}}|none|-}}
| {{#ifeq:{{{website|}}} | hide | | {{{website|}}} }}
- | {{#if:{{wikidata|property|raw|P856}}
+ | {{#if:{{wikidata|property|raw|{{{qid|}}}|P856}}
| {{#invoke:WikidataIB |url2 |url={{if empty
- |{{#invoke:WikidataIB|getValueByLang|P856|fwd=ALL|osd=no|maxvals=1}}
- |{{Wdib|P856|fwd=ALL|osd=no|maxvals=1}}
+ |{{#invoke:WikidataIB|getValueByLang|P856|qid={{{qid|}}}|fwd=ALL|osd=no|maxvals=1}}
+ |{{Wdib|P856|qid={{{qid|}}}|fwd=ALL|osd=no|maxvals=1}}
}} }}
}}
}}
@@ -121,7 +121,7 @@
}}{{#invoke:Check for unknown parameters | check | showblankpositional=1
| unknown = {{main other|[[Category:Pages using Infobox software with unknown parameters|_VALUE_{{PAGENAME}}]]}}
| preview = Page using [[Template:Infobox software]] with unknown parameter "_VALUE_"
-| alexa | AsOf | author | bodystyle | caption | collapsible | developer | discontinued | engine | engines | genre | included with | games list | language | language count | language footnote | latest preview date | latest preview version | latest release date | latest release version | latest_preview_date | latest_preview_version | latest_release_date | latest_release_version | licence | license | logo | logo alt | logo caption | logo size | logo_alt | logo_size | middleware | name | operating system | operating_system | other_names | platform | programming language | programming_language | released | replaced_by | replaces | repo | screenshot | screenshot alt | screenshot size | screenshot_alt | screenshot_size | service_name | size | standard | title | tools | ver layout | website
+| alexa | AsOf | author | bodystyle | caption | collapsible | developer | discontinued | engine | engines | genre | included with | games list | language | language count | language footnote | latest preview date | latest preview version | latest release date | latest release version | latest_preview_date | latest_preview_version | latest_release_date | latest_release_version | licence | license | logo | logo alt | logo caption | logo size | logo_alt | logo_size | middleware | name | operating system | operating_system | other_names | platform | programming language | programming_language | released | replaced_by | replaces | repo | screenshot | screenshot alt | screenshot size | screenshot_alt | screenshot_size | service_name | size | standard | title | tools | ver layout | website | qid
}}</includeonly><noinclude>
{{documentation}}
</noinclude>
|
The template documentation should be updated to include qid as a string type value. When it is "none", it disables all wikidata fetching by pretending there is a value in "if". When it is a valid QID, it causes the corresponding QID to be used instead (adds to the expensive count, but it's necessary). When it is empty, the default value of the page's QID will be used. (Google "online diff patch" for some in-browser stuff if you don't have the patch tool.) --Artoria2e5 🌉 02:27, 2 July 2020 (UTC)
- The usual way to illustrate your proposed changes is to make your changes to the Template:Infobox software/sandbox. Can you please do that? Also, it looks like this template uses a lot of if statements that might not be necessary. Please take a look at {{Infobox person/Wikidata}}, which may have the functionality you are proposing without all of the logical tests. – Jonesey95 (talk) 03:33, 2 July 2020 (UTC)
- Ditto that request. Consider syncing the sandbox to the main template first. Feel free to reactivate/provide a new edit request after doing so. --Izno (talk) 04:02, 2 July 2020 (UTC)
- Synced the sandbox and applied the changes. Added a new testcase for qid. --Artoria2e5 🌉 13:50, 2 July 2020 (UTC)
- I added some more testcases, but I am unable to see any differences when I use different options for
|qid=. Am I doing something wrong? Please modify the Chrome testcases that I have added such that they demonstrate the new features that you are attempting to add. – Jonesey95 (talk) 14:10, 2 July 2020 (UTC)- I am marking this request as answered pending feedback on the testcases. Feel free to reactivate it after pointing out what I am doing wrong. – Jonesey95 (talk) 13:14, 4 July 2020 (UTC)
- My friend Jonesey95, of course the Chrome testcases appear the same with or without QID! All the fields that would have used Wikidata already have a provided value, so why did you expect that to kick in? I removed the website value in the cases with QID so you can see it. --Artoria2e5 🌉 17:32, 7 July 2020 (UTC)
- I am marking this request as answered pending feedback on the testcases. Feel free to reactivate it after pointing out what I am doing wrong. – Jonesey95 (talk) 13:14, 4 July 2020 (UTC)
- I added some more testcases, but I am unable to see any differences when I use different options for
- Synced the sandbox and applied the changes. Added a new testcase for qid. --Artoria2e5 🌉 13:50, 2 July 2020 (UTC)
- Ditto that request. Consider syncing the sandbox to the main template first. Feel free to reactivate/provide a new edit request after doing so. --Izno (talk) 04:02, 2 July 2020 (UTC)
@Izno: for update. --Artoria2e5 🌉 12:45, 15 July 2020 (UTC)
- To editor Artoria2e5: done, and thank you for your patience! Please update the template documentation as needed. P.I. Ellsworth ed. put'r there 02:57, 24 August 2020 (UTC)
Use of Alexa in infoboxes
Watchers of this page may be interested in Wikipedia:Village pump (proposals) § RfC: Alexa Rankings in Infoboxes. Izno (talk) 21:20, 18 September 2020 (UTC)
Bogus website?
The PSPP article shows several bogus websites ... and smushes them all into one link. It seems like the code in this template to pull the official website from WikiData is broken. -- Mikeblas (talk) 20:39, 26 September 2020 (UTC)
- I see one link in "Repository" and one link in "Website", and they both work fine. What are you seeing that appears to be broken? – Jonesey95 (talk) 15:56, 28 September 2020 (UTC)
Date format for releases
At OpenSSL I presume this template gets release dates invisibly from Wikidata since no such parameters are specified. Unfortunately these are presented with two different date formats (mdy for latest and dmy for preview), and I can't figure out how to make them consistently mdy. Can someone help? Hairy Dude (talk) 23:40, 14 October 2020 (UTC)
Website URL - wikidata rank beng ignored
On the article cURL the infobox pulls all URLs from the wikidata item. It should only pull the preferred rank URL (i.e. the currently URL) rather than the normal ranked URL. --Tagishsimon (talk) 00:14, 12 November 2020 (UTC)
- Visible on an old version -https://en.wikipedia.org/w/index.php?title=CURL&oldid=988008197 - I'm going to set the URL in the template on the wikipedia side for the live version. --Tagishsimon (talk) 00:19, 12 November 2020 (UTC)
Cite has empty unknown parameter: |date6=
{{Infobox software
|name = OneDrive
}}
on Microsoft OneDrive emits error "Cite has empty unknown parameter: |date6=", populates Category:CS1 errors: empty unknown parameters, and is not easily found. Please correct. ~ Tom.Reding (talk ⋅dgaf) 17:04, 20 November 2020 (UTC)
- @Trappist the monk: may know best how to do so. --Izno (talk) 17:32, 20 November 2020 (UTC)
Fixed with this edit. Petscan can help find templates in CS1 maint categories. Note that sometimes the error is shown only on the template page itself because a parameter is invalid there but works fine when the template is transcluded, so the template page should not be "fixed". Ping me if you have any questions. – Jonesey95 (talk) 17:32, 20 November 2020 (UTC)
- Doesn't
<!--|date6 = Dunno-->make it look like|date6=is a valid parameter? Why not just delete? - —Trappist the monk (talk) 17:42, 20 November 2020 (UTC)
- Noted.
|date6=belonged outside the cite template, which I subconsciously saw but did not fix correctly. Now fixed in a better way. – Jonesey95 (talk) 20:37, 20 November 2020 (UTC)
- Noted.
- Doesn't
Template-protected edit request on 31 December 2020
| This edit request to Template:Infobox software has been answered. Set the |answered= parameter to no to reactivate your request. |
When it links "Preview release" to Software_release_life_cycle, (as it does from, e.g. Active Agenda) it should be tweaked to link to Software_release_life_cycle#Beta instead. 50.201.195.170 (talk) 18:16, 31 December 2020 (UTC)
- Done if this is controversial for some reason, I will revert on request — Martin (MSGJ · talk) 16:52, 4 January 2021 (UTC)
Specify that it is still maintained, albeit without new releases
Extending discontinued I suppose is one option… for example there hasn't been a new Tiny_C_Compiler] release in 3 years, but the repo is still active https://repo.or.cz/w/tinycc.git — Preceding unsigned comment added by Samuel Marks (talk • contribs) 06:38, 14 January 2021 (UTC)
- Might hinge on WP:OR, depending on what you consider active. Last commit pushed two months ago? One random pull requested after two years of staleness? The current parameter might have the same problem, even. One way or another, I would even support removing stuff like preview versions (or versions in general), which have to be updated frequently with no real benefit to the reader. IceWelder [✉] 11:09, 14 January 2021 (UTC)
Date format
I can't quite figure out what's going on at Signal (software), but I assume the instance of this infobox there is pulling the most recent value of wikidata:Property:P348 for the stable and preview release params. Is there a way for me to make it display {{Start date and age}} in those params in dmy as opposed to mdy format? It defaults to mdy and I don't know how to change it without manually inputting all the data, which for obvious reasons I would prefer not to do. AleatoryPonderings (???) (!!!) 05:42, 15 January 2021 (UTC)
- Ah, it seems Hairy Dude asked a similar question a while ago. I'm also perplexed at the FAQ above, which suggests that the template doesn't pull release versions from Wikidata … In which case I'm even more confused, because I don't know where the info is coming from! AleatoryPonderings (???) (!!!) 05:44, 15 January 2021 (UTC)
- @AleatoryPonderings: The data is taken from this (stable) and this (preview) template page. It's an ages-old implementation that works but is somewhat archaic. IceWelder [✉] 07:13, 15 January 2021 (UTC)
Template-protected edit request on 1 March 2021
| This edit request to Template:Infobox software has been answered. Set the |answered= parameter to no to reactivate your request. |
The display of the "Screenshot" dropdown bar should look like the one at Template:Infobox website (which looks better, in my opinion). I have implemented the change in this sandbox revision, and the test cases look as intended. — Goszei (talk) 01:25, 1 March 2021 (UTC)
- To editor Goszei: curious about this one. Not sure a collapsible is better in an infobox, but if it is, I would think you'd show an example on the test cases page that depicts a screenshot when the reader clicks "show". Also, if there is no screenshot, as is the case in some examples on the test cases page, I would think that it would become invisible in those cases. Is that viable and doable? You might need a consensus for this edit. And {{Infobox website}} might need to be changed to an uncollapsed screenshot version. Collapsibility in iboxes is possibly a controversial issue. P.I. Ellsworth ed. put'r there 11:18, 1 March 2021 (UTC)
- @Paine Ellsworth: I think there's been a bit of a misunderstanding. This template already has a collapsible feature/parameter, and I have just changed how the dropdown bar looks.
- JJMC89 bot removed the (non-free, oops) images I put in the test cases before you took a look. That did make me realize that I forgot to account for the "no screenshot" case though, which I have now fixed. — Goszei (talk) 16:55, 1 March 2021 (UTC)
- Done – forgot about the non-free screenshot thing. We can see how other editors respond to it. Noticed you also removed some Alexa stuff; since you didn't explain that I didn't include it. Thank you very much for your improvements! P.I. Ellsworth ed. put'r there 00:21, 2 March 2021 (UTC)
Wrong hyperlink
Hi, the "tools" argument hyperlink is now pointing to Game development tool which is wrong and should be pointed to Software tool, please modify this link to the correct link. i.e. change
| label9 = [[Game development tool|Tools]]
to
| label9 = [[Software tool|Tools]]
Thanks, Hooman Mallahzadeh (talk) 09:16, 10 March 2021 (UTC)
- That is a redirect to Programming tool. Still want it changed? — Martin (MSGJ · talk) 12:09, 10 March 2021 (UTC)
- @MSGJ: Much better than Game, and more relevant. I think is correct.Hooman Mallahzadeh (talk) 12:23, 10 March 2021 (UTC)
- Done — Martin (MSGJ · talk) 12:27, 10 March 2021 (UTC)
- (edit conflict) The documentation does designate the field to be used for game development tools. The only articles that use it as far as I can find are Dark Engine, Rockstar Advanced Game Engine, and Windows Registry, the first two of which do use it as intended by the documentation (apparently it was added as a result of a merger with {{Infobox video game engine}}). The latter just lists related executables (added by you), which are certainly not programming tools and don't strike me as information so vital as to be included in the infobox. Nardog (talk) 12:30, 10 March 2021 (UTC)
- Agreed, this could just be removed. IceWelder [✉] 12:35, 10 March 2021 (UTC)
- @Nardog and IceWelder: I'm not agree with you, programming tools are very important, e.g., for databases, instant messengers etc. Software tools are like tools in mechanics e.g. Screwdriver or Wrench. Choosing the correct one should be mentioned in their Infoboxs. Hooman Mallahzadeh (talk) 12:39, 10 March 2021 (UTC)
- Important or not, the executables you listed in Windows Registry are certainly not programming tools as defined in Programming tool. Nardog (talk) 12:46, 10 March 2021 (UTC)
- @Nardog: Why not, we use a tool like RegEdit.exe for create or visit registry items (create and debug), and use Cfgback.exe for backup (maintain), and poledit.exe for editing policies(maintain). This use is according to this definition :"A programming tool or software development tool is a computer program that software developers use to create, debug, maintain, or otherwise support other programs and applications.". Isn't that? Note that by definition "Windows Registry" is a database and so is a software (or program or application). Hooman Mallahzadeh (talk) 12:54, 10 March 2021 (UTC)
- But that is not a programming tool. The programming tool is what was used to develop the registry itself. The original definition for
|tools=were tools that shipped with a game engine, where game development tool would have been correct. Given the ambiguity around the field and its apparent original research use, I still advocate deletion of the entire field. That you can use RegEdit to edit registry entries is not infobox material. IceWelder [✉] 13:04, 10 March 2021 (UTC)- @IceWelder: As I know "Windows Registry" itself is written by C programming language and some of its libraries. Is C or its library a tool? No, I think "programming language" is not a tool, but tool is an "application" or "computer program" as this is explicitly mentioned in the definition of programming tool. Hooman Mallahzadeh (talk) 13:35, 10 March 2021 (UTC)
- "Programming tool" would be e.g. CLion or Eclipse but this is rarely documented and can, for most software products, change at any time. "Programming language" is a separate parameter. IceWelder [✉] 13:43, 10 March 2021 (UTC)
- @IceWelder: You are completely right. But this sentences also exists in the "Windows Registry" article:
- "Programming tool" would be e.g. CLion or Eclipse but this is rarely documented and can, for most software products, change at any time. "Programming language" is a separate parameter. IceWelder [✉] 13:43, 10 March 2021 (UTC)
- @IceWelder: As I know "Windows Registry" itself is written by C programming language and some of its libraries. Is C or its library a tool? No, I think "programming language" is not a tool, but tool is an "application" or "computer program" as this is explicitly mentioned in the definition of programming tool. Hooman Mallahzadeh (talk) 13:35, 10 March 2021 (UTC)
- But that is not a programming tool. The programming tool is what was used to develop the registry itself. The original definition for
- @Nardog: Why not, we use a tool like RegEdit.exe for create or visit registry items (create and debug), and use Cfgback.exe for backup (maintain), and poledit.exe for editing policies(maintain). This use is according to this definition :"A programming tool or software development tool is a computer program that software developers use to create, debug, maintain, or otherwise support other programs and applications.". Isn't that? Note that by definition "Windows Registry" is a database and so is a software (or program or application). Hooman Mallahzadeh (talk) 12:54, 10 March 2021 (UTC)
- Important or not, the executables you listed in Windows Registry are certainly not programming tools as defined in Programming tool. Nardog (talk) 12:46, 10 March 2021 (UTC)
- @Nardog and IceWelder: I'm not agree with you, programming tools are very important, e.g., for databases, instant messengers etc. Software tools are like tools in mechanics e.g. Screwdriver or Wrench. Choosing the correct one should be mentioned in their Infoboxs. Hooman Mallahzadeh (talk) 12:39, 10 March 2021 (UTC)
- Agreed, this could just be removed. IceWelder [✉] 12:35, 10 March 2021 (UTC)
- Windows Registry can be edited manually using programs such as RegEdit.exe, although these tools do not expose some of the registry's metadata such as the last modified date.
- Optional and/or third-party tools similar to RegEdit.exe are available for many Windows CE versions.
- The Reg.exe and RegIni.exe utility tools are included in Windows XP and later versions of Windows.
- Registry permissions can be manipulated through the command line using RegIni.exe and the SubInACL.exe 'tool.
- . Another way is to use the Windows Resource Kit Tool, Reg.exe by executing it from code,[24] although this is considered poor programming practice.
- Windows 98 and Windows ME include command line (Scanreg.exe) and GUI (Scanregw.exe) registry checker tools to check and fix the integrity of the registry, create up to five automatic regular backups by default and restore them manually or whenever corruption is detected.
- The Windows 95 CD-ROM included an Emergency Recovery Utility (ERU.exe) and a Configuration Backup Tool (Cfgback.exe) to back up and restore the registry.
- The policy file is created by a free tool by Microsoft that goes by the filename poledit.exe for Windows 95/Windows 98 and with a computer management module for Windows NT.
Here the writer of article is mentioning what sort of tool? Some how "utility tool" but not a programming tool. But we do not have an utility tool article in the English Wikipedia. Here I think the hyperlink should be removed and the "tool" word becomes "Utility tool". Do you agree? — Preceding unsigned comment added by Hooman Mallahzadeh (talk • contribs) 14:21, 10 March 2021 (UTC)
- The infobox should not be stuffed with random tools that can be used with certain software or systems, that was never the point of the parameter (which also was never discussed for inclusion in the first place). Game development tool was somewhat well-defined, programming tool already is not, and changing it to "utility tool" (which is also a bad name) will just invite vandals to promote their own tools that could be used in conjunction with any software. I still favor deletion of the parameter altogether, as its inclusion was never discussed and its proper use is very limited. IceWelder [✉] 15:49, 10 March 2021 (UTC)
- @IceWelder: You are right, I am now agree with you, I believe deleting is reasonable. @MSGJ: You can now decide to delete this argument. Thanks, Hooman Mallahzadeh (talk) 16:43, 10 March 2021 (UTC)
| This edit request to Template:Infobox software has been answered. Set the |answered= parameter to no to reactivate your request. |
- Done. Please remove from the documentation — Martin (MSGJ · talk) 16:58, 10 March 2021 (UTC)
Rename "Original author(s)" to "Creator(s)"?
"Software creator" seems to be a common expression. fgnievinski (talk) 00:34, 4 February 2021 (UTC)
- I oppose this change, and think it's fine as it is. If you think a change is necessary, a non-loaded phrase would be "Original developer(s)". DesertPipeline (talk) 05:14, 23 March 2021 (UTC)
Import more from WikiData
Hello folks,
i know using WikiData is a big change in the way of working, but it is worth the effort. Especially having in mind our declining active user base.
In many lingual editions of Wikipedia (Spanish, Portuguese, German, French, ...) most content of the software infobox is pulled from WikiData.
This makes for a huge workload reduction.
And it works great now, e.g. :de:Everything and Everything
Also it is suggested very often:
- Version Number and Wikidata
- Taking more data from wikidata
- License doesn't fetch from Wikidata for Audacity
- Date format - Archaic workaround with a template to ease work.
- use wikidata for developer, license by default
And this Template talk:Infobox software/FAQ is outdated. It's being displayed at the header of this discussion-page. (Explanation why it is outdated)
One reason the English Wikipedia lags behind in implementing was the opposition of User:Codename Lisa.
What's your opinion?
--Alex42 (talk) 19:06, 14 April 2021 (UTC)
- You are welcome to create a demonstration in the sandbox. For some example code, take a look at {{Infobox telescope}}. Remember that all information imported into infoboxes from Wikidata must cite a reliable source. The easiest way to ensure that is to use Module:WikidataIB in its default configuration. – Jonesey95 (talk) 20:02, 14 April 2021 (UTC)
Job hard to complete
The question is on https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Job_hard_to_complete . Category:Latest stable software release templates have a lot of versions to update... What can be done to simplify the work? I think to transfer to Wikidata, it is very simple to manage the release versions on Wikidata. You can check this source code. On the Italian Wikipedia, the template Software have the Stable release parameter with empty value, the value come from Wikidata. Maybe on the Infobox software template could be use template for call version value from Wikidata. And I attempted to repost the question for improve visibility, but the repost was deleted. If I cant repost the question, nobody can see the question and will be remain without answer forever... ----93.35.184.189 (talk) 13:51, 26 April 2021 (UTC)
add article to Category:Discontinued software if discontinued=yes?
Would it make sense to add the article to Category:Discontinued software if the discontinued field is set? Ixfd64 (talk) 19:22, 23 July 2021 (UTC)
- Probably not, per WP:TEMPLATECAT. – Jonesey95 (talk) 19:36, 23 July 2021 (UTC)
- Fair enough. Ixfd64 (talk) 19:54, 23 July 2021 (UTC)
Author and Developers
Both the Author and Developer parameters caused links to redirects, so I've moved them to their eventual target to avoid the redirect. Notably, they both go to Programmer. Do we really need two different parameters for the same thing? Maybe one is meant to be a company (or team) and the other an individual, or small list of individuals? -- Mikeblas (talk) 19:06, 29 July 2021 (UTC)
Please make EditAtWikidata inline with Repository URL
| This edit request to Template:Infobox software has been answered. Set the |answered= parameter to no to reactivate your request. |
Hi, Wikidata fetched "repository URL" data item can be inline with pen shaped EditAtWikidata, see CodeMirror article and its Infobox and "Repository data item" to see what I mean (they are not inline now), this pen shaped EditAtWikidata item can be inline with repository URL to save space, i.e., via changing the following code:
| data6 = {{#if:{{{repo|}}}{{#ifeq:{{{qid|}}}|none|-}}
|{{{repo|}}}
|{{#if: {{#property:P1324|from={{{qid|}}}}}
|{{#ifeq: {{wikidata|property|{{{qid|}}}|P1324|best|format=%p}} | none
|{{wikidata|property|{{{qid|}}}|P1324|best|format=%p}}{{EditAtWikidata|pid=P1324}}
|{{Plainlist|<ul><li>{{URL|{{wikidata|property|{{{qid|}}}|P1324|best|format=%p}}}}</li></ul>}}{{EditAtWikidata|pid=P1324|qid={{{qid|}}}}}
}}
}}
}}
into this code:
| data6 = {{#if:{{{repo|}}}{{#ifeq:{{{qid|}}}|none|-}}
|{{{repo|}}}
|{{#if: {{#property:P1324|from={{{qid|}}}}}
|{{#ifeq: {{wikidata|property|{{{qid|}}}|P1324|best|format=%p}} | none
|{{wikidata|property|{{{qid|}}}|P1324|best|format=%p}}{{EditAtWikidata|pid=P1324}}
|{{Plainlist|<ul><li>{{URL|{{wikidata|property|{{{qid|}}}|P1324|best|format=%p}}}}{{EditAtWikidata|pid=P1324|qid={{{qid|}}}}}</li></ul>}}
}}
}}
}}
Note that this change causes the software Infobox to become more compact and so more beautiful. Thanks, Hooman Mallahzadeh (talk) 09:27, 25 August 2021 (UTC)
- @MSGJ: Hi, all the below articles have a redundant "newline" in Infobox and its "Repository" data item:
- npm (software)
- pip (package manager)
- APTonCD
- RPM Package Manager
- Composer (software)
- Synaptic (software)
- Node.js
- and etc. Pen shaped EditAtWikidata can be inline with the URL. Am I right? Would you please do this code change? Hooman Mallahzadeh (talk) 04:47, 31 August 2021 (UTC)
- Done – Jonesey95 (talk) 05:16, 31 August 2021 (UTC)
Edit Proposal
| This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
I want to add a new parameter, slogan = which displays it's slogan. Leomk0403 (talk) 02:23, 17 November 2021 (UTC)
- Not done for now: please establish a consensus for this alteration before using the
{{edit template-protected}}template. Slogans and mottos have generally been removed from infoboxes in recent years. – Jonesey95 (talk) 03:09, 17 November 2021 (UTC)
What does qid do?
I didn't any changes when I tried to add it. I tried to write id with q and without so I don't understand format of this field. — Preceding unsigned comment added by DustDFG (talk • contribs) 15:10, 18 January 2022 (UTC)
- It fetches values for
|repo=,|engine=, and|website=from Wikidata if those values are not provided. You can see it in action at american fuzzy lop (fuzzer), where repo and website are not provided in the infobox, but they are displayed anyway. There are more automated ways to retrieve this data, but the template would have to be rewritten a bit, in part because it does not currently comply with the 2018 RFC requiring reliable sources for all infobox data fetched from Wikidata. – Jonesey95 (talk) 15:17, 18 January 2022 (UTC)
Template-protected edit request on 29 January 2022
| This edit request to Template:Infobox software has been answered. Set the |answered= parameter to no to reactivate your request. |
It seems that some of my request was lost...
Could you change in the Template code:
sizedefault=300x64px > sizedefault=64px
maxsize=300x64px > maxsize=300px
A computer icon (called "logo" here), is always "square".
Template:Infobox_software documentation "Size of the logo. Defaults to 64px."; please add "Max size is 300px."
Antoine Legrand (talk) 19:43, 29 January 2022 (UTC)
- Not done. Logos do not need to be desktop icons nor are they always square. Bash (Unix shell) is one such example. IceWelder [✉] 21:22, 29 January 2022 (UTC)
Template-protected edit request on 3 February 2022
| This edit request to Template:Infobox software has been answered. Set the |answered= parameter to no to reactivate your request. |
Could the [show] collapsible button be placed to the right (preferably right-aligned) of List of languages?
This design seems to be done in {{Infobox website}}. In my opinion it looks better that way. ZaidhaanH (talk) 02:09, 3 February 2022 (UTC)
Portal di Ensiklopedia Dunia
