Difference between revisions of "Projects/Usability/HIG/CustomControls"

< Projects‎ | Usability‎ | HIG
Jump to: navigation, search
(Guidelines: add keyboard navigation bullet point)
(HIG moved to community)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
__NOTOC__
+
{{ Moved To Community | KDE_Visual_Design_Group/HIG/CustomControls }}
{{Construction}}
 
== Purpose ==
 
 
 
== Examples ==
 
 
 
== Guidelines ==
 
* Do you really need a custom widget? Check whether an existing widget cannot be used instead.
 
* It is strongly recommended to consult the usability team (https://git.reviewboard.kde.org/groups/usability/) and the accessibility team (https://git.reviewboard.kde.org/groups/kdeaccessibility/) in advance of your implementation.
 
* Create interaction by following natural design. Find the appropriate metaphor and create interface as near to real usage as possible.
 
* Make sure your new widget:
 
** Resizes correctly
 
** Handles right-to-left setups
 
** Supports keyboard navigation (receives and gives focus, indicates when it is focused)
 
** Works well with different color schemes
 
** Looks as close to existing Qt or kdelibs widgets as possible (use QStyle or QStylePainter to draw elements).
 
** Is based on an existing widget rather than a plain QWidget if possible
 
* If possible, consider making your widget reusable enough so that it can be integrated in standard widgets
 
 
 
== Implementation ==
 

Latest revision as of 11:26, 4 August 2016

This page is now on the community wiki.


This page was last edited on 4 August 2016, at 11:26. Content is available under Creative Commons License SA 4.0 unless otherwise noted.