aboutsummaryrefslogtreecommitdiffstats
path: root/qt-mobile/qml/Log.qml
AgeCommit message (Collapse)Author
2016-03-08port to Kirigami imports and new apiGravatar Marco Martin
first quick and dirty port of the imports to Kirigami 1.0 (using system installed for now) adapt to api changes and try out some of the proposed ui changes from the HIG Signed-off-by: Marco Martin <notmart@gmail.com>
2016-02-12QML UI: remove the redundant context menus that just close the pageGravatar Dirk Hohndel
Android users are well used to using the back key for this. I kept the code in place as things may end up completely different on IOS or other mobile platforms. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2016-02-12QML UI: experimentally enable context menu on each pageGravatar Dirk Hohndel
This is necessary to allow all user interaction when removing action buttons from the top bar. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2016-02-09QML UI: Back buttons for app log and theme infoGravatar Henrik Brautaset Aronsen
The app log and theme info had context menus with a single close item. No need for that. Signed-off-by: Henrik Brautaset Aronsen <subsurface@henrik.synth.no> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2016-01-06adjustments needed for latest mobilecomponentsGravatar Sebastian Kügler
- flickable is gone, Page now just takes the children items, meaning we can remove this assignment - BasicListItem is factored out, and we now need it in our qrc Signed-off-by: Sebastian Kügler <sebas@kde.org>
2016-01-01QML UI: allow the user to close the LogGravatar Dirk Hohndel
Same context menu idea. The reason for adding this is that the context menu always acts on the last page in the stack (so I guess the "right-most-one"). So if you edit a dive and then open the log, you can't save the dive until the dive edit is the last page which means you have to close the log, first. Not ideal, but better than nothing and it works well enough. I still think we might want to go back to a traditional "Save" button... Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2015-12-08Page margins for app logGravatar Sebastian Kügler
Adds consistent page margins also to Log page. Signed-off-by: Sebastian Kügler <sebas@kde.org>
2015-12-08Fix text wrapping in log viewerGravatar Sebastian Kügler
Apparently, the width setting got lost in the previous change. This sets the width of the log text explicitely to the grandparent's width. It fixes text clipping in the log window. Signed-off-by: Sebastian Kügler <sebas@kde.org>
2015-12-07simplify and style log pageGravatar Sebastian Kügler
- less instantiated objects inside each other - add page heading - allow wrapping of text Signed-off-by: Sebastian Kügler <sebas@kde.org>
2015-12-04QML UI: log the text shown on the log pageGravatar Dirk Hohndel
Sadly this doesn't work, even though it appears to be the thing to do based on the documentation. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2015-12-03QML-UI: make Log page scrollableGravatar Dirk Hohndel
I noticed when sending a bunch of debug output to the log that it didn't scroll and that seemed wrong. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2015-11-11kill warningGravatar Sebastian Kügler
This line seems to be a left-over from a refactoring. It doesn't do anything, just produces a warning, so just remove it. Signed-off-by: Sebastian Kügler <sebas@kde.org> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2015-11-08Android: remove duplicate top bar from log windowGravatar Joakim Bygdell
The log page have an extra top bar that is not needed. Signed-off-by: Joakim Bygdell <j.bygdell@gmail.com> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2015-11-07organize qml files in subdirectoriesGravatar Sebastian Kügler
This makes the organization of the qml files a bit more fine-grained, it prevents mixing of .cpp and QML files, and also of what's compiled, and what's included in the app as qrc data. In particular: - subsurface specific QML items go into the qml/ subdirectory - theme and unit definitions to into qml/theme subdirectory (they already were located in a theme directory) - generic components, such as our Label goes into qml/components This facilitates sharing of functionality and identifying common stuff better. Ideally, we can pull qml/theme and qml/components from a standardized set at some point, so we don't have to maintain that code. Signed-off-by: Sebastian Kügler <sebas@kde.org> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>