On Thu, Apr 21, 2016 at 12:59 PM, Dirk Hohndel wrote:
> 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 h
On Thursday 21 April 2016 09:59:32 Dirk Hohndel wrote:
> 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.
On Thursday 21 April 2016 10:02:32 Dirk Hohndel wrote:
> > I found a way to more or less fix it on Android:
> >
> > 1) disable any margin calculation for the case of android in
> > ApplicationWindow.qml
>
> Is there anything I need to do there besides what you've already committed
> to master?
n
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 bottom margin is added,
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: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 Wed, Apr 20, 2016 at 6:41 PM, 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
> set up the proxy with the desktop version and then have the mobile version
> built on the same
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 bottom margin is added, sometimes it isn't. So either we
> compensate for the bug in Kiri
On Thursday 21 April 2016 07:42:52 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 bottom margin is added, sometimes it isn't. So either we
> compensate for the bug in Kir
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
> > set up the proxy w
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
> set up the proxy with the desktop version and then have the mobile version
> built on the sa
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 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
> >
> > I've seen QScreen physical dots per inch reporting rubbish o
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
> I've seen QScreen physical dots per inch reporting rubbish on some Android
> devices, I think Nexus 7 was even one of them. S
On Tuesday 19 April 2016 05:03:01 Dirk Hohndel wrote:
> > Since it's not something that Kirigami was made for, I fear that at some
> > point, it will just break, and it would neither be good if Kirigami had
> > to
> > adapt to Subsurface-mobile's specialties, nor if you had to work
> > "against"
> 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
> 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 them. See my comment in QTBUG-35701
for a workaround (basically aski
> 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 with how
>>> close the actions are together. Can y
> 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 button, but boy does that feel "
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 button, but boy does that feel "tight".
very tiny indeed :)
--
Marco Martin
_
> 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
>> bit of "learning by doing" and at least
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 Dienstag, 19. April 2016 04:39:34 CEST Dirk Hohndel wrote:
> > 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 cu
> 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 because we do weird things with
>> pages that have mu
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 because we do weird things with
> pages that have multiple states). That isn't to say that I suddenly no
> longer
> 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
>>> indeed is a bit cramped making side buttons dif
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
> > indeed is a bit cramped making side buttons difficult to hit
>
> I take this to mean that you'd like me
> 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
>> bit of "learning by doing" and at least
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
> bit of "learning by doing" and at least initially being a moving target.
>
> I guess I was confused
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.
> >
> > Switching to a new API isn't rea
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.
>
> Switching to a new API isn't really a big deal for us. I build all the
> binaries and we already have th
On Montag, 18. April 2016 11:28:04 CEST Dirk Hohndel wrote:
> 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
> > bot
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.
Webbrowser: new tab, edit url, top page
Image viewer: export, edit,
Am 18.04.2016 19:34 schrieb "Kai Uwe Broulik" :
> I like that, also the compact look.
>
> In an Email app when reading a mail for example the main button would be
> "reply" , the right one "forward" and the left one "reply all" or
I like that, also the compact look.
In an Email app when reading a mail for example the main button would be
"reply" , the right one "forward" and the left one "reply all" or "archive".
The less important action would be in the context drawer.
Ursprüngliche Nachricht
Von:notm...@gmail.com
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
From discussions with the designers, it seems it should be always limited to
36 matches
Mail list logo
