Am 04.02.2014 12:21, schrieb Daniel Kinzler:
Am 03.02.2014 20:37, schrieb Bene*:
I would be glad if you explained a bit further
how this feature will work on
client. There needs to be a mechanism to select which items are visible in the
interwiki links section and which are not. This will perhaps be a setting on the
client. However, even if we say, only FA and GA badges should be shown in the
article, it can still come to collisions when a sitelink has two badges which
are both specified in the client's config. How should this cases be handled?
In that case, both badges would be shown. The idea is: "if it IS wrong, it
should LOOK wrong". Having both badges on the same page violates a convention.
The convention should not be enforced by the software but by the community
(possibly with the help of bots, common.js, etc).
I would propose to add a css class for each badge that applies to a given
language link. Per default, these classes would do nothing. Each client wiki can
then define site CSS (or JS) to make some badges visible.
Interesting, so in your opinion the actual display of items should
happen via the common.css? I think this can work though I don't know if
we should leave this implementation detail to the local wikis. At least,
it would prevent another config to be added to the client which is very
recommened from my side. Also the wiki could rank the badges easier.
(New css properties override old ones.) Thus I support your idea leaving
this to the client wikis.
Another question, however, is which tooltip title should be added to the
badges sitelink. We could use the description of the wikidata item but I
am not sure if we can access it easily from client. However, it would
provide an easy way to translate the tooltip without some hacky
mediawiki messages.
Best regards,
Bene*