Hi there,
I just subscribed so please bear with me if I'm going over things that
have been discussed.
Some background for context:
Subsurface is a reasonably popular open source dive log program aimed
primarily at scuba divers. It's somewhat known in open source circles as
it was started by Linu
Hi Thomas,
> On Jan 5, 2016, at 3:22 PM, Thomas Pfeiffer wrote:
> as the person in charge of the KDE Mobile HIG (and therefore also responsible
> for the usability of the Plasma Components), I'm very happy to get feedback
> from users of an actual working application using our components!
Awes
Hi Thomas
On Wed, Jan 06, 2016 at 02:56:09AM +0100, Thomas Pfeiffer wrote:
You clearly have interesting working hours... just like Sebastian
> There is a difference between edge swipe and regular horizontal swipes. All
> stock Android apps that have a lef
On Wed, Jan 06, 2016 at 11:58:30AM +0100, Marco Martin wrote:
> > I will talk to Sebastian about synching our code base with upstream again
> > and hope that I can help contribute to the upstream project.
>
> One thing I would love to see, is the components downloaded and built at
> setup
> time
On Wed, Jan 06, 2016 at 11:29:16AM +0100, Marco Martin wrote:
>
> > > Therefore what I'd like to see is that when our components are used
> > > within Android, they draw the buttons in the top bar (where they are -
> > > and that is a research-supported fact - hard to reach, but consistent
> > > w
On Wed, Jan 06, 2016 at 11:14:18AM +0100, Marco Martin wrote:
> On Wednesday 06 January 2016, Thomas Pfeiffer wrote:
> > Therefore what I'd like to see is that when our components are used within
> > Android, they draw the buttons in the top bar (where they are - and that is
> > a research-supporte
On Wed, Jan 06, 2016 at 04:39:33PM +0100, Marco Martin wrote:
> On Wednesday 06 January 2016, Dirk Hohndel wrote:
> > Building for Android is painful (as Sebastian will confirm). Adding
> > something where an application after being started downloads other
> > components... no
On Wed, Jan 06, 2016 at 05:41:27PM +0100, Marco Martin wrote:
> On Wednesday 06 January 2016, Dirk Hohndel wrote:
> >
> > Well, before we removed the FAB I was quite easily able to get into
> > situations where the FAB would disappear and would not show back up,
> > r
> On Jan 6, 2016, at 10:55, Kai Uwe Broulik wrote:
>
> Hi,
>
> The issue with the virtual keyboard shifting the contents on Android is an
> issue I also face with pure Qt apps and as of now there is no way to prevent
> or detect this behavior, at least not with Qt APIs.
>
> I think Qt 5.6 w
On Wed, Jan 06, 2016 at 08:03:16PM +0100, Marco Martin wrote:
> On Wednesday 06 January 2016, Marco Martin wrote:
> > On Wednesday 06 January 2016, Kai Uwe Broulik wrote:
> > > Hi,
> > >
> > > The issue with the virtual keyboard shifting the contents on Android is
> > > an issue I also face with p
I'm sure this email will mostly just expose my ignorance - but I'm OK with
that :-) -- I asked on IRC but I think no one was around who knew.
I want to be able to change the content of the context menu, depending on,
err, context. Seems like a reasonable thing to want to do. So I'm sure
there
> On Jan 6, 2016, at 12:47, Marco Martin wrote:
>
> On Wednesday 06 January 2016, Tomaz Canabrava wrote:
>>>
>>> hmm, not sure it answers much yet.. who is mainDisplay?
>>
>> Its one of the Pages in an AplicationWindow, like the initialPage.
>> the "current" one should give the Actions for th
On Wed, Jan 06, 2016 at 10:32:59PM +0100, Marco Martin wrote:
> > > so, if it depends from pages, you just define a different
> > > contextualactions list for every page definition...
> >
> > Currently we have one page that has two different states. You view a dive
> > or you edit a dive. Dependin
On Wed, Jan 06, 2016 at 01:49:28PM -0800, Dirk Hohndel wrote:
> On Wed, Jan 06, 2016 at 10:32:59PM +0100, Marco Martin wrote:
> > > > so, if it depends from pages, you just define a different
> > > > contextualactions list for every page definition...
> > >
&
On Wed, Jan 06, 2016 at 11:31:58PM +0100, Kai Uwe Broulik wrote:
> Don't we handle the visible and enabled property of Action? That should work
> for enabling / disabling certain drawer entries if in edit mode.
> Irregardless of that usecase I would really expect that to work.
There is no "visi
On Wed, Jan 06, 2016 at 11:57:24PM +0100, Marco Martin wrote:
> On Wednesday 06 January 2016, Dirk Hohndel wrote:
> > If I write this as
> >
> > property list viewActions: [
> > Action { }, Action { }
> > ]
> > property list ed
On Wed, Jan 06, 2016 at 03:08:02PM -0800, Dirk Hohndel wrote:
> On Wed, Jan 06, 2016 at 11:57:24PM +0100, Marco Martin wrote:
> > On Wednesday 06 January 2016, Dirk Hohndel wrote:
> > > If I write this as
> > >
> > > property list viewA
So if I have one of the drawers open and then tap on the back button on
the device, I think that should close that drawer instead of going back
one level in the app and leaving the drawer open... the NEXT tap on the
back button should now move back one level.
Next, imagine a screen where you can i
Here's an interaction that I would like to have:
User long-presses on an element on screen, a popup shows a question with
several options and the user gets to decide what to do.
Somehow I'm guessing that adding a MessageDialog and acting based on the
button that was pressed isn't what the Plasma
On Fri, Jan 08, 2016 at 09:02:41PM +0100, Thomas Pfeiffer wrote:
> On Freitag, 8. Januar 2016 11:43:31 CET Dirk Hohndel wrote:
> > Here's an interaction that I would like to have:
> >
> > User long-presses on an element on screen, a popup shows a question with
> &
On Fri, Jan 08, 2016 at 09:35:05PM +0100, Thomas Pfeiffer wrote:
> On Freitag, 8. Januar 2016 12:25:19 CET Dirk Hohndel wrote:
> > Ha. I love being the guinea pig (Versuchskaninchen is even cuter).
>
> Good *rubbing hands*...
Hmm
> > We have a list with a LOT of e
On Fri, Jan 08, 2016 at 09:35:33PM +0100, Kai Uwe Broulik wrote:
> Hi,
>
> > But many of our users ask us for the ability to
> > a) see where these GPS fixes are on a map and
> > b) selectively delete some of these GPS fixes
>
> Don't we have the list item with actions for that? Swipe item to th
On Fri, Jan 08, 2016 at 10:18:31PM +0100, Marco Martin wrote:
> On Friday 08 January 2016 13:04:53 Dirk Hohndel wrote:
> > >
> > > To me, this sounds like a case for the "slide to reveal actions" pattern
> > > (see [1]). Would that work in your case?
>
On Mon, Jan 11, 2016 at 03:07:16PM +0100, Marco Martin wrote:
> On Monday 11 January 2016, Sebastian Kügler wrote:
> > How to go about it? I'd be cool with just deleting it. If anybody wants to
> > keep it, please propose how it should reflect that the info is not recent,
> > or offer to update it.
, this does not solve
the problem that my patch addressed; the external references to linearGradients
are not removed by svgo
/D
- Dirk Hohndel
On Jan. 14, 2016, 3 a.m., Aleix Pol Gonzalez wrote:
>
> ---
> This is an automatically ge
In certain cases the existing code would access an index past the end of
the pageStack
/D
>From b7097228532e41cf2efe772fb922d51c7ab72f69 Mon Sep 17 00:00:00 2001
From: Dirk Hohndel
Date: Wed, 27 Jan 2016 07:05:35 -0800
Subject: [PATCH] Don't access past the last element of the pageStack
On Wed, Feb 03, 2016 at 05:48:40PM +0100, Marco Martin wrote:
> On Wednesday 03 February 2016 16:24:10 David Edmundson wrote:
> > If you mean this one?
> > https://dot.kde.org/sites/dot.kde.org/files/plasma-mobile-logo.png
> > Sure.
> >
> > Anything more radical I'm against as it breaks not only o
We are using the mobile components for an Android application.
One of the features we get by default from the components is that when the
user presses the Android BACK key the top page is pop()-ed from the stack.
Is there a way to get a call back when that happens? So something like
onPagePopped
On Sat, Feb 06, 2016 at 04:01:01PM +0100, k...@privat.broulik.de wrote:
>
> in the apps I wrote I have a onBackRequested signal on my Page class which
> can also be used to reject the back button event (eg. event.accepted =
> false); I think something like this could be added to Plasma Mobile
> Co
On Sat, Feb 06, 2016 at 07:38:12AM -0800, Dirk Hohndel wrote:
> On Sat, Feb 06, 2016 at 04:01:01PM +0100, k...@privat.broulik.de wrote:
> >
> > in the apps I wrote I have a onBackRequested signal on my Page class which
> > can also be used to reject the back button even
I'm running into a pretty significant issues with the ActionButton:
Its MouseArea has an implicitWidth of parent.width. Which means that my page
will not receive any clicks at all in the horizontal band that includes the
ActionButton - so if the ActionButton "floats" above a ListView, the botto
On Mon, Feb 08, 2016 at 11:48:24AM -0800, Dirk Hohndel wrote:
>
> I'm running into a pretty significant issues with the ActionButton:
>
> Its MouseArea has an implicitWidth of parent.width. Which means that my page
> will not receive any clicks at all in the horizontal ba
On Tue, Feb 09, 2016 at 12:06:37PM +0100, Marco Martin wrote:
> On Monday 08 February 2016 11:48:24 Dirk Hohndel wrote:
> > I'm running into a pretty significant issues with the ActionButton:
> >
> > Its MouseArea has an implicitWidth of parent.width. Which means that my
On Tue, Feb 09, 2016 at 03:53:53PM +0100, Marco Martin wrote:
> On Tuesday 09 February 2016 14:38:42 Sebastian Kügler wrote:
> > > Sorry, that's just broken.
> >
> > Can we make it react to horizontal swipe, but nothing else?
>
> no, for how Qt events work, once it eats the events there, the even
On Tue, Feb 09, 2016 at 08:01:23AM -0800, Dirk Hohndel wrote:
>
> Current Subsurface-mobile APKs are based on a forked version of
> mobilecomponents (again) which implement just that.
Oops, crossed email. I'll switch back to master :
On Tue, Feb 09, 2016 at 05:04:44PM +0100, Thomas Pfeiffer wrote:
>
> Yes, as Marco said, this change was a result form user testing. Two of five
> users I've tested with so far have tried swiping anywhere on the Action
> Button's row to open the drawers, because they expected it to work that way
On Tue, Feb 09, 2016 at 06:43:34PM +0100, Thomas Pfeiffer wrote:
> > > I understand your user's problems, however. Even though in fact, the
> > > lowest
> > > list item can still be reached by scrolling it up (a standard function
> > > supported by the list component allows users to scroll the firs
On Tue, Feb 09, 2016 at 06:00:58PM +0100, Marco Martin wrote:
> > That isn't useful in the way it's implemented right now, though. I can
> > pull it up but it springs right back. So if my list has a "tap to open an
> > item" feature, it is /really/ hard to open the last entry in that list
> > (that
at to work (and attempts to visualize the
disabled state by reducing the opacity in that case).
/D
From d7f7ef25c54c2024ad87e23b7b7353c4655936c5 Mon Sep 17 00:00:00 2001
From: Dirk Hohndel
Date: Wed, 10 Feb 2016 18:06:36 -0800
Subject: [PATCH] Allow Actions in the GlobalDrawer to be disabled
> On Feb 11, 2016, at 3:01 AM, Marco Martin wrote:
>
> On Tuesday 09 February 2016 10:48:18 Dirk Hohndel wrote:
>>> 2) Humans' first reaction to change is always hostility (unless they are
>>> disciples of the Cult of Apple, that is).
>>
>> True.
On Thu, Feb 11, 2016 at 12:01:54PM +0100, Marco Martin wrote:
> On Tuesday 09 February 2016 10:48:18 Dirk Hohndel wrote:
> > > 2) Humans' first reaction to change is always hostility (unless they are
> > > disciples of the Cult of Apple, that is).
> >
> >
> On Feb 11, 2016, at 11:57 AM, Marco Martin wrote:
>>
>> Somewhat unrelated... the issue with the content "behind" the handles and
>> the ActionButton. I hate the idea of having a margin at the bottom (that
>> basically creates another menu bar that isn't usable for the content of my
>> app scr
he path
we just stroke it.
/D
From 8a68beef83ab7b4412fad9eec213470138ab3946 Mon Sep 17 00:00:00 2001
From: Dirk Hohndel
Date: Fri, 12 Feb 2016 10:01:05 -0800
Subject: [PATCH 1/3] Make handles obscure less of the screen behind them
Signed-off-by: Dirk Hohndel
---
components/mobilecomp
This is an odd one. Not sure what the logic was behind that, but with the
existing code on most phones the context drawer takes up the complete
screen which makes it look really weird.
/D
From 59779ccf31f7a1f48a45401655aeb7eaa98cc4fe Mon Sep 17 00:00:00 2001
From: Dirk Hohndel
Date: Fri, 12
page. But how do
you change your mind and go back? Easy again. Hit the back button.
Oops. You just quit your application.
The patch below fixes that.
/D
From 8381291d8b82a815691290bb75fe6cba3b4e08c0 Mon Sep 17 00:00:00 2001
From: Dirk Hohndel
Date: Sat, 13 Feb 2016 21:00:13 -0800
Subject: [PATCH 3
On Feb 23, 2016, at 12:51, Thomas Pfeiffer wrote:
>
>
> We had ideas like "slide", "paper" or "blocks" flying around, but then Alex
> Longo came up with Origami, which in turn led him to "Kirigami".
> For those of you who (like the rest of the brainstorming team) don't know
> what
> Kirigami
On Wed, Feb 24, 2016 at 10:52:08PM +0100, Thomas Pfeiffer wrote:
> > > It is physical, it is creative, kinda playful without being childish, and
> > > it's far less common than Origami, which helps with searchability.
> >
> > I'm always dismayed when projects have names of existing real things.
>
c Mon Sep 17 00:00:00 2001
From: Dirk Hohndel
Date: Wed, 2 Mar 2016 14:48:30 -0800
Subject: [PATCH] Allow the program to explicitly hide a notification
Signed-off-by: Dirk Hohndel
---
components/mobilecomponents/qml/private/PassiveNotification.qml | 5 +
1 file changed, 5 insertions(+)
diff --
On Thu, Mar 03, 2016 at 11:51:53AM +0100, Marco Martin wrote:
> On Wednesday 02 March 2016 14:50:52 Dirk Hohndel wrote:
> > If I want to use a PassiveNotification to give some information to the
> > user that either hides after a while or gets removed when it's no longer
> &
> On Mar 3, 2016, at 8:12 AM, Marco Martin wrote:
>
> On Thursday 03 March 2016 06:19:19 Dirk Hohndel wrote:
>> AH, right, I forgot to post about that problem.
>>
>> So for me the magic notification attached to the action button didn't seem
>> to work - or
earlier Qt versions?
/D
From b2aabd82bfb55695ab1d8ebe013abd3a1fb665b3 Mon Sep 17 00:00:00 2001
From: Dirk Hohndel
Date: Fri, 4 Mar 2016 09:55:46 -0800
Subject: [RFC-PATCH] Don't show empty pages on the right
We want to show as many of our pages as possible, so if we scroll to a page on
the stack make sure that we don&#
On Fri, Mar 04, 2016 at 07:48:05PM +0100, Marco Martin wrote:
> On Friday 04 March 2016 10:09:45 Dirk Hohndel wrote:
> >
> > The patch below seems to fix the problem, but I'm not sure it's the right
> > patch... Marco, Sebastian, comments?
> >
>
> I
Or what should I link to? The text I have right now is (based on what Thomas
suggested)
This release is the result of years of work on Subsurface and a year long
development effort towards a mobile user interface that would shine on phones
and tablets. We got tremendous help from the KDE commu
> On Mar 12, 2016, at 9:48 AM, Sebastian Kügler wrote:
>
> Sore point, really. Our web-presence currently utterly sucks (there's some
> work going on in that area), but no sensible page to link to, other than,
> perhaps. ... http://plasma-mobile.org/ or
> https://projects.kde.org/projects/playgr
Just like commit c8311b80d0a5 ("ensure the animation is stopped and
restarted") makes sure that the animation is run when showing the passive
notification, we need to do the same when hiding the animation, or a too
quick succession of show() and then hide() breaks things.
Signed-of
On Tue, Mar 15, 2016 at 01:26:22PM +, Lucas S wrote:
> Hi
>
> It is time for a quick update so here is the first version of the
> Plasma 5.6 video https://youtu.be/q-nACSvivGU
> After initial feedback on the plasma IRC channel, this is the list of
> planned changes for the next video.
>
> 1.
long email, lots of content, many ideas, many requests. At least I am
bringing along two patches and I hope the issues that I report make sense
and help to make Kirigami better!
Thanks for all your hard work on this
/D
>From 979b4cc61f6497b5583387ea6ca175dc2542139d Mon Sep 17 00:00:00 2001
From: Dirk
Responding to myself to add some clarifications based on some more
discussions with some of the testers...
On Fri, Apr 01, 2016 at 10:44:03PM -0500, Dirk Hohndel wrote:
>
> 5. the margin at the top when pulling down a list (e.g., our dive list)
> seems HUGE and unintuitive. It really l
On Sat, Apr 02, 2016 at 04:38:43PM +0200, Thomas Pfeiffer wrote:
> even though you addresses Marco, let me comment on your suggestions so Marco
> knows what's "Kirigami design approved":
Bad habit of mine to address one person instead of all of you...
> > I have spent quite a few hours on portin
Responding to myself again... must be a sign of approaching senility...
On Sat, Apr 02, 2016 at 09:55:51AM -0500, Dirk Hohndel wrote:
> >
> > > I think this is our consolidated feedback:
> > >
> > > - make it an intentional action; stop at the top when scrolling
Sep 17 00:00:00 2001
From: Dirk Hohndel
Date: Sat, 2 Apr 2016 17:47:30 -0500
Subject: [PATCH 4/4] Allow the application to notify Kirigami about changed
title
Simply calling header.updateBreadCrumbs() makes sure that the bread crumbs
in the title are correct.
Signed-off-by: Dirk H
--
Sent from my phone
> On Apr 3, 2016, at 11:11, Marco Martin wrote:
>
>
>> 2. connected to this, if the keyboard opens, now the bottom of the page is
>> the upper edge of the keyboard and the action button is shown at the right
>> spot, but the drawer(s) and the drawer handle(s) are not m
On Mon, Apr 04, 2016 at 03:02:05AM +0200, Thomas Pfeiffer wrote:
> On Sunday, 3 April 2016 11:42:31 CEST Dirk Hohndel wrote:
>
> > Well, doesn't need to be blurred home screen. Could be the blurred copy of
> > what you are moving. Or just an oddly shaded area. Just so i
On Mon, Apr 04, 2016 at 03:40:50PM +0200, Marco Martin wrote:
> On Sunday 03 April 2016, you wrote:
> > > the patch is fine, but I would prefer the property to be called "opened"
> > > that even if doesn't shound great, is the name of an analogous property
> > > for OverlayDrawer, so i would like t
> On Apr 4, 2016, at 08:08, Thomas Pfeiffer wrote:
>
> On Sonntag, 3. April 2016 23:35:29 CEST Dirk Hohndel wrote:
>>>
>> My current thinging is that I may end up doing just that in the iOS
>> version. Having a back button somewhere that isn't a corner feel
So with the latest master, a lot of the things I've been hoping for have
been improved or added. I love the speed of progress.
Couple of things that I noticed
- the overscroll looks much better now that the title bar comes down with
it - but then things behave a bit oddly. It doesn't jump back
On Mon, Apr 04, 2016 at 02:51:07PM -0700, Dirk Hohndel wrote:
> - on iOS the git log of Kirigami tells me I should now have a back button
> but I don't see it on my iPhone. I'm still investigating this one,
> though, not sure if this app error or an issue with the code in
On Mon, Apr 18, 2016 at 07:29:43PM +0200, Marco Martin wrote:
> Hi all,
>
> one thing that as i understood was needed in the mobile UI of Subsurface, is
> the possibility to add other buttons in the action buttons at the bottom.
> here's how my prototype looks like: http://imgur.com/VTHbDBJ
Hmm.
On Mon, Apr 18, 2016 at 10:07:32PM +0200, Marco Martin wrote:
> On Monday 18 April 2016, Dirk Hohndel wrote:
> > Cute. I like it. Just make sure that I can use variables to assign to this
> > as the available buttons will change depending on context for us.
> >
> > S
> On Apr 19, 2016, at 2:01 AM, Marco Martin wrote:
>
> On Monday 18 April 2016, Dirk Hohndel wrote:
>> When Sebastian and I first talked about using the "mobile components" for
>> Subsurface-mobile I explicitly agreed that I was happy with this being a
>> bi
> On Apr 19, 2016, at 4:19 AM, Marco Martin wrote:
>
> On Tuesday 19 April 2016, Dirk Hohndel wrote:
>>> the look and behavior of buttons can be tested and adjusted (that
>>> shouldn't involve further API changes), as the current implementaton
>>> in
> On Apr 19, 2016, at 4:45 AM, Marco Martin wrote:
>
> On Tuesday 19 April 2016, Dirk Hohndel wrote:
>>> would be cool :)
>>
>> As I go through our sources I notice that for Subsurface-mobile the new
>> syntax isn't really better (but that's beca
On Tue, Apr 19, 2016 at 01:54:10PM +0200, Thomas Pfeiffer wrote:
> >
> > As I go through our sources I notice that for Subsurface-mobile the new
> > syntax isn't really better (but that's because we do weird things with pages
> > that have multiple states). That isn't to say that I suddenly no lon
> On Apr 19, 2016, at 2:01 AM, Marco Martin wrote:
>
> On Monday 18 April 2016, Dirk Hohndel wrote:
>> When Sebastian and I first talked about using the "mobile components" for
>> Subsurface-mobile I explicitly agreed that I was happy with this being a
>> bi
> On Apr 19, 2016, at 5:33 AM, Marco Martin wrote:
>
> On Tuesday 19 April 2016, Dirk Hohndel wrote:
>> This is an old Nexus 7; if I have my index finger hovering over the button
>> it easily covers all three icons; yes, I can make it hit the right part of
>> the but
> On Apr 19, 2016, at 5:50 AM, Thomas Pfeiffer wrote:
>
> On Dienstag, 19. April 2016 05:26:35 CEST Dirk Hohndel wrote:
>>> On Apr 19, 2016, at 5:12 AM, Dirk Hohndel wrote:
>>>
>>> So I've played with this on my phone and I'm not super excited wi
With latest master of Kirigami we are observing an odd problem in
Subsurface-mobile.
This happens in landscape mode (at least I haven't been able to reproduce this
in portrait mode).
Our page stack has in position zero a vertical listview (dive list). If you
select one of the dives in this li
> On Apr 19, 2016, at 7:31 AM, Kai Uwe Broulik wrote:
>
>> 2.) On your Nexus 7, the whole thing indeed is way too small. This seems to
>> be a DPI scaling issue, though
>
> I've seen QScreen physical dots per inch reporting rubbish on some Android
> devices, I think Nexus 7 was even one of th
I finally figured out why Subsurface-mobile no longer shows multiple columns in
landscape mode on the devices that I usually test on...
In commit e73c014a0 ("simplify PageRow, fix currentItem calculation") the logic
for how many columns to show changed in a subtle but significant way:
-prop
> On Apr 19, 2016, at 12:32 PM, Kai Uwe Broulik wrote:
>
>> , or is this something I need to take to the Qt developers?
>
> Yes, please, the more they hear about it the more likely they are to start
> doing something about it...
Should I do this on your old bug report QTBUG-35701 which seems
e ListView.
A patch like this seems to fix the problem
From caf268d4378c9e365f13014e2240ada574c8487b Mon Sep 17 00:00:00 2001
From: Dirk Hohndel
Date: Tue, 19 Apr 2016 13:56:31 -0700
Subject: [PATCH] Don't overlap header and page when scrolling to top on header
tap
This seems fragile but
> On Apr 19, 2016, at 2:34 PM, Kai Uwe Broulik wrote:
>
> I don't know the code by heart but doesn't the ScrollView set a top margin?
> If so, contentY should be set to it rather than assuming it's based on the
> header height.
I searched for just that margin and couldn't find it. I don't thi
On Wed, Apr 20, 2016 at 05:52:48PM +0200, Marco Martin wrote:
> On Wednesday 20 April 2016, Sebastian Kügler wrote:
> > On Tuesday 19 April 2016 16:31:41 Kai Uwe Broulik wrote:
> > > > 2.) On your Nexus 7, the whole thing indeed is way too small. This
> > > > seems to be a DPI scaling issue, though
On Wed, Apr 20, 2016 at 10:36:05AM +0200, Marco Martin wrote:
> On Tuesday 19 April 2016, Dirk Hohndel wrote:
> > go). The latter always appears to have the top item aligned with the
> > header, but when I tap on the header and have scrollTopAnimation run to:
> > 0, then th
On Wed, Apr 20, 2016 at 07:32:04PM +0200, Marco Martin wrote:
> On Wednesday 20 April 2016 09:44:43 Dirk Hohndel wrote:
> > On Wed, Apr 20, 2016 at 10:36:05AM +0200, Marco Martin wrote:
> > > On Tuesday 19 April 2016, Dirk Hohndel wrote:
> > > > go). The latter alway
> On Apr 20, 2016, at 7:51 PM, Martin Klapetek
> wrote:
>
> Is it possible to either hide the blue titlebar when empty
> or add things like buttons and icons in there?
>
> In SpaceBar, the active conversation has this layout at
> the top of the Page:
>
> [Presence Icon] Username [Close Conver
On Thu, Apr 21, 2016 at 12:17:14PM +0200, Sebastian Kügler wrote:
> On Wednesday 20 April 2016 09:41:15 Dirk Hohndel wrote:
> > We set the font size based on preferences, IIRC - and we use the same
> > prefs for desktop and mobile (that's not just laziness - that allows me to
On Thu, Apr 21, 2016 at 06:42:59PM +0200, Marco Martin wrote:
>
> that's subsurface next to the gallery example app how they look on my laptop:
> http://imgur.com/Ni9fhkD
>
> note the size of the bottom action button and drawer handle.. that
> looks pretty weird
That's weird indeed. Any idea why
On Thu, Apr 21, 2016 at 05:28:28PM +0200, Marco Martin wrote:
>
> > (3) the ListView scrolling issue
> > When scrolling a ListView it's very easy to get into a state where QML
> > gets confused and part or all of the screen becomes background color
> > and trying to scroll makes things
On Thu, Apr 21, 2016 at 06:17:19PM +0200, Marco Martin wrote:
> On Thu, Apr 21, 2016 at 4:42 PM, Dirk Hohndel wrote:
> > (1) the keyboard issue on both iOS and (maybe less so) Android.
> > Sometimes the virtual keyboard opening is deteceted correctly and
> > correct b
Currently we do this:
Kirigami.ApplicationWindow {
id: rootItem
title: qsTr("Subsurface-mobile")
header.minimumHeight: 0
header.preferredHeight: Kirigami.Units.gridUnit * (Qt.platform.os ==
"ios" ? 2 : 1)
header.maximumHeight: Kirigami.Units.gridUnit * 2 p
On Thu, Apr 21, 2016 at 08:09:15PM +0200, Marco Martin wrote:
> On Thursday 21 April 2016 10:09:38 Dirk Hohndel wrote:
> > Currently we do this:
> >
> > Kirigami.ApplicationWindow {
> > id: rootItem
> > title: qsTr("Subsurface-mobile&
On Thu, Apr 21, 2016 at 08:33:19PM +0200, Marco Martin wrote:
> Hi all,
> i think my rewrite of PageRow is almost done
> here's a review request on phab: https://phabricator.kde.org/D1460
> some test would be welcome, it should be pretty easy, just to switch
> to the branch
> mart/PageRow5.6
> in t
On Fri, Apr 22, 2016 at 06:37:38PM +0200, Marco Martin wrote:
> On Thursday 21 April 2016 11:38:25 Dirk Hohndel wrote:
> > > from my tests on the gallery app it seems at least not to have
> > > regressions (hopefully should work a bit better)
> > > if from tests lo
On June 2, 2016 4:03:06 AM PDT, Thomas Pfeiffer wrote:
>
>On 02.06.2016 12:39, Alessandro Longo wrote:
>> Il 23-05-2016 22:52 Alessandro Longo ha scritto:
>>> (resent because apparently mailman rejected it)
>>> Hi,
>>> after a lot of iterations I found a simple idea for Plasma's logo
>that
>>> imh
> On Jun 13, 2016, at 6:20 AM, Sebastian Kügler wrote:
> notmart:
> * attending store meeting
> * systray gives applets a screen
> * Kirigami: better logic and explicit api for the "reachable" mode (all ui
> slides down)
> ** a new component for a toolbar in the header: to be used only in deskt
On Sun, Aug 14, 2016 at 09:38:27PM +0200, Thomas Pfeiffer wrote:
> On 14.08.2016 06:29, Dirk Hohndel wrote:
> > I still haven't managed to make the latest Kirigami work. And I don't think
> > I'll finish that today as I'm jet lagged and about to fall asleep on
On Mon, Aug 15, 2016 at 11:33:08AM +0200, Marco Martin wrote:
> On Monday 15 August 2016, Dirk Hohndel wrote:
> > Kirigami as is has a few oddities. It compiles neither with cmake nor with
> > qmake. Hmm.
> >
> > I have patches for that, but on iOS it still dies at st
> On Aug 15, 2016, at 7:10 AM, Marco Martin wrote:
>
> On Monday 15 August 2016, Dirk Hohndel wrote:
>> Do you have any idea, though, while this is crashing for me on iOS?
>> The crash is always in some Qt internal - and it's always that some
>> internal Qt man
> On Aug 15, 2016, at 7:50 AM, Marco Martin wrote:
>
> On Monday 15 August 2016, Dirk Hohndel wrote:
>> Line numbers in kirigamiplugin.cpp are slightly off since I have a few
>> lines of debug output in there; frame #9 is foreach (const QString &style,
>> m_styl
1 - 100 of 117 matches
Mail list logo
