HIG and components API

[Thomas Pfeiffer]

On Wednesday 07 October 2015 11:24:36 Marco Martin wrote:
> On Wednesday 07 October 2015, Thomas Pfeiffer wrote:
> > You are right. Our original idea was to take our ideas to the
> > kde-guidelines mailing list before publishing them, but
> > a) I admittedly forgot
> > b) Maybe plasma-devel is better to reach all stakeholders (or maybe cross-
> > posting to both lists)
> 
> any is fine for me (admittedly i discovered the existence of such list just
> now :/)

Ok, we'll discuss and choose what we'll do.

> > > I fear in this case it may make harder to make the bottom of the
> > > content,
> > > whatever it is to not be covered by the buttons (ie whenever you have
> > > any
> > > flicking content, it should have padding at the bottom, to be able to
> > > scroll out of the way) that makes every single application to have to
> > > workaround and assume things on an external design factor that may even
> > > change any time
> > 
> > Since the floating buttons are more of a gimmick than something that is
> > actually relevant for the interaction, we're not hell-bent on them.
> > The idea for them came from the  big red round button in recent Android
> > applications for the main action. If you have only one button, a toolbar
> > is
> > a bit of a waste of space.
> 
> I'll try to do an experiment of full toolbar sliding in ond out, may be
> good, may look weird

I admit I can't really picture what you mean, but I'll see the results ;)
 
> > screen where it can be reached easily. Of course when the list is
> > displayed initially, the first item would be at the top of the screen, but
> > it wouldn't stop there if the user scrolled further up.
> > Would that be possible?
> 
> yep, i think so :) in ListView one can put arbitrary empty space in the
> header of footer

Great! :) Then let's try and see if it feels good or weird.