Property talk:P1414

Documentation

GUI toolkit or framework
framework or toolkit a program uses to display the graphical user interface
Descriptionframework or toolkit a program uses to display windows
Representswidget toolkit (Q1193246), software framework (Q271680)
Data typeItem
Domain
According to this template: software
According to statements in the property:
software (Q7397), software bug (Q179550), fictional software (Q55566469) or software version (Q20826013)
When possible, data should only be stored as statements
Allowed valuesitems should be instance/subclass of GUI framework (note: this should be moved to the property statements)
ExampleGIMP (Q8038)GTK (Q189464)
Source Filmmaker (Q4049816)Qt (Q201904)
Sourceofficial websites of programs (note: this information should be moved to a property statement; use property source website for the property (P1896))
Tracking: usageCategory:Pages using Wikidata property P1414 (Q23909113)
Lists
Proposal discussionProposal discussion
Current uses
Total1,645
Main statement1,63099.1% of uses
Qualifier150.9% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Item “software version identifier (P348): Items with this property should also have “software version identifier (P348)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1414#Item P348, search, SPARQL
Value type “widget toolkit (Q1193246), user interface (Q47146): This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value widget toolkit (Q1193246), user interface (Q47146) (or a subclass thereof). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1414#Value type Q1193246, Q47146, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1414#Entity types
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1414#Scope, SPARQL

Is single value constraint actually appropriate? edit

Is single-value constraint (Q19474404) actually appropriate here? Some software is implemented with multiple toolkits, or has migrated between different toolkits. For instance, Dolphin (Q1236429) previously was implemented using wxWidgets (Q284982), but now is implemented using Qt (Q201904), and for a time both implementations were present (Qt was added in 4.0-3258, made the default over wx in 5.0-7062, and wx was removed in 5.0-8279; slightly awkwardly, Dolphin 5.0 is the latest fully released version; only beta builds and development builds have come out since. I've attempted to model that here, with Qt marked as preferred, but that still violates the constraint since there are multiple values. Perhaps it could be changed to single-best-value constraint (Q52060874), though that still doesn't quite resolve the situation where multiple toolkits are present at the same time (as in 5.0). (Ping to @IXavier). --Pokechu22 (talk) 19:46, 11 January 2021 (UTC)Reply

I concur. Further examples include Transmission (Q875055) and Qalculate! (Q6027344). Theanswertolifetheuniverseandeverything (talk) 13:40, 31 October 2021 (UTC)Reply
I've removed the constraint. --Pokechu22 (talk) 16:40, 31 October 2021 (UTC)Reply
Return to "P1414" page.