CommonDialog
QueryDialog
SelectionDialog
the base Dialog is still not exported
in future version on the desktop, QueryDialog will create a standard qt dialog instead
some dataengines can have a different set of keys for each item (ie metadata dataengine) the whole mapped roles must be the complete superset
this is not very efficient, but unfortunately is necessary.
(another reason why DataContainers should become models)
Also refactored the busy indicator gallery code and
agregated it with the progress bar gallery.
Signed-off-by: Daker Fernandes Pinheiro <dakerfp@gmail.com>
The ProgressBar is defined in the Qt Components common API.
It has a orientation property, usign Qt.Horizontal or
Qt.Vertical to set the orientation of the component.
Signed-off-by: Daker Fernandes Pinheiro <dakerfp@gmail.com>
The TextArea is defined in the Qt Components common API.
Some features were added as a plasma specific behaviour for this component:
- It emit the keys pressed and released signals
- Implements a focus policy
- The current implementation only covers the desktop use case.
For mobile use, a flickable text area with scroll decorators
would be more appropriate.
- Scroll bars appears only if the content is bigger than the content.
- The width of the the scroll bars can be setted through the scrollWidth
property
- The size of the text content can also be setted. For this the properties
contentMaxWidth and contentMaxHeight must be used. The default value
is the dimensions of the TextArea.
The current state of the implemention lacks of:
- A behaviour for hover state, present in other components
- A errorHighlight usage
- Polish the visual alignment of the SVGs items
- Lacks of right mouse button interaction.
Would be interesting to use it to cut & paste operations.
Signed-off-by: Daker Fernandes Pinheiro <dakerfp@gmail.com>
- The function was not bounding the value after incremented
inside the flickable content size.
Signed-off-by: Daker Fernandes Pinheiro <dakerfp@gmail.com>
The TextField is defined in the Qt Components common API.
Some features were added as a plasma specific behaviour for this component:
- It emit the keys pressed and released signals.
- Implements a focus policy
The current state of the implemention lacks of:
- A behaviour for hover state, present in other components
- A errorHighlight usage
Signed-off-by: Daker Fernandes Pinheiro <dakerfp@gmail.com>
- The current disabled scroll bar have less opacity when disabled
instead of custom graphics. Needs to be defined if this is
the expected behaviour.
Signed-off-by: Daker Fernandes Pinheiro <dakerfp@gmail.com>
- The current disabled slider have less opacity when disabled
instead of custom graphics. Needs to be defined if this is
the expected behaviour.
- The gallery example was also updated.
Signed-off-by: Daker Fernandes Pinheiro <dakerfp@gmail.com>
- The current disabled CheckBoxes, RadioButtons and Switches,
have less opacity when disabled instead of custom graphics.
Needs to be defined if this is the expected behaviour.
Signed-off-by: Daker Fernandes Pinheiro <dakerfp@gmail.com>
- The current disabled buttons have less opacity when disabled
instead of custom graphics. Needs to be defined if this is
the expected behaviour.
Signed-off-by: Daker Fernandes Pinheiro <dakerfp@gmail.com>
- When a button is clicked it aqcuires the focus.
- The space and return keys now can be used to press the button if
it has the activeFocus
Signed-off-by: Daker Fernandes Pinheiro <dakerfp@gmail.com>
The RangeModel value was being incremented directly by the mouse and keys
events, and it was overriding the binding with the flickableItem position.
Once the ScrollBar button was clicked, the direct manipulation of the
flickable component was not updating the scroll position.
The new function 'incrementValue' now does the correct work.
Signed-off-by: Daker Fernandes Pinheiro <dakerfp@gmail.com>
- Move columns present in the gallery into separate files
- Move Gallery into a subdir of tests
Signed-off-by: Daker Fernandes Pinheiro <dakerfp@gmail.com>
