[kde-guidelines] Styleguide: Tool-tips

[Thomas Pfeiffer]

On 10.07.2013 14:31, Aurélien Gâteau wrote:
> Le mercredi 10 juillet 2013 11:16:10 Thomas Pfeiffer a écrit :
>> On 09.07.2013 18:05, Aurélien Gâteau wrote:
>>> On Monday 08 July 2013 11:55:27 Heiko Tietze wrote:
>>>> Am Donnerstag, 4. Juli 2013, 15:10:57 schrieb Aurélien Gâteau:
>>>>>> * Use user defined default timeouts for initialization, reshow, and
>>>>>> removal. Don't disable auto hide feature.
>>>>>
>>>>> Developers cannot alter any of those so it may not be worth keeping it.
>>>>
>>>> Removed.
>>>>
>>>>> QWhatsThis is not really info-tip though, because its primary use case
>>>>> is
>>>>> to support the "what's this?" mode. The ability to show a QWhatsThis
>>>>> window independently from this mode is a by-product. I think we should
>>>>> not
>>>>> promote info-tips and we should not mention QWhatsThis as implementing
>>>>> them info-tip for now, instead we should get a proper widget to show
>>>>> them,
>>>>> this widget would look either like a '?' button or a link-like label and
>>>>> would show the tip when triggered.
>>>>
>>>> The question mark button is mentioned with "* Consider to add small info
>>>> buttons for use tips with a touch screen."
>>>
>>> Yes, I understood this. I was saying kdelibs could provide a standard API
>>> for this button, so that not every developer reimplements it... slightly
>>> differently.
>>
>> Yes, it should. The question is: Should we hide the guideline for info
>> buttons until the API is in place?
>
> Maybe I could put together a short code snippet to create one? I do not expect
> this to be too much code.

That would be great, yes. A central class in the library might still be 
preferable because it would allow us to centrally change behavior later 
on, but everyone using the same code to manually create it would still 
avoid any chaos.