On Thu, Oct 22, 2015 at 7:15 PM, Thomas Pfeiffer
wrote:
>
> If you're looking also for input on the HIG compliance, screenshots are
> helpful :)
sorry it taken a long time:
https://www.youtube.com/watch?v=WfhcWRHCEtA
(ignore the fixed scrollbars, that's because is on a laptop, and the
white rect
On Thu, Oct 22, 2015 at 7:19 PM, Thomas Pfeiffer
wrote:
> Sorry for replying only now.
> The actions are always supposed to be for the most narrow context available.
> So if individual items are selected in a list or on a page, then the context
> actions change to those for those specific items.
>
On Friday 16 October 2015 10:38:55 Marco Martin wrote:
> On Thursday 08 October 2015 18:18:24 Thomas Pfeiffer wrote:
> > Another thing about the context drawer:
> > Would it be possible to center the list of actions vertically so that it's
> > easier to reach with the thumb (at least if it has only
On Thursday 15 October 2015 11:00:28 Marco Martin wrote:
> On Wed, Oct 14, 2015 at 2:22 PM, Marco Martin wrote:
> > ok, so a version is here, it's just few components but want to keep it
> > minimal https://phabricator.kde.org/D409
>
> I invite people to get a look at it and review.
> Phabricator
On Thursday 08 October 2015 18:18:24 Thomas Pfeiffer wrote:
> Another thing about the context drawer:
> Would it be possible to center the list of actions vertically so that it's
> easier to reach with the thumb (at least if it has only a few actions)?
Another question about the context view:
do y
On Wed, Oct 14, 2015 at 2:22 PM, Marco Martin wrote:
> ok, so a version is here, it's just few components but want to keep it minimal
> https://phabricator.kde.org/D409
I invite people to get a look at it and review.
Phabricator reviews are useful only if somebody well, reviews.
--
Marco Martin
ok, so a version is here, it's just few components but want to keep it minimal
https://phabricator.kde.org/D409
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
On Monday 12 October 2015, Thomas Pfeiffer wrote:
> We've been talking to Michael Spencer, one of the main driving forces
> behind those components, about how we can collaborate (he seems quite
> positive about the idea!).
> If you see any areas where direct collaboration could make sense, speak up
On Friday 09 October 2015 18:00:18 Marco Martin wrote:
> On Thursday 08 October 2015, Aleix Pol wrote:
> > > * could some content for the global drawer be there by default? do we
> > > leave a blank slate? even the hig examples are very heterogeneous
> > > https://techbase.kde.org/Projects/Usabilit
On Monday 12 October 2015 11:33:07 Marco Martin wrote:
> That's another reason why I think our higs and components shouldn't be that
> different from something that could work on Android, because either
> developers will use them for one app port that will work on both plasma
> mobile and android,
On Wednesday 07 October 2015, Alex L. wrote:
> In data mercoledì 7 ottobre 2015 14:53:32, Marco Martin ha scritto:
> > which looks like this, i kindof like
> > https://www.youtube.com/watch?v=qHHWG_Qm2ks
>
> If I understand well, technically the toolbar like that it's OK but
> "floating buttons" n
On Friday 09 October 2015, Aleix Pol wrote:
>
> One thing I really like about the Material ones is that even if they
> provide a Button.qml component, they also provide the style for it and
> base their button on the one in QtQuick.Controls. This way, one can
> have code using QtQuick.Controls and
In data mercoledì 7 ottobre 2015 14:53:32, Marco Martin ha scritto:
> which looks like this, i kindof like
> https://www.youtube.com/watch?v=qHHWG_Qm2ks
If I understand well, technically the toolbar like that it's OK but "floating
buttons" not. To be sure we have the same concept of "floating but
On Fri, Oct 9, 2015 at 6:28 PM, Marco Martin wrote:
> On Thursday 08 October 2015, Aleix Pol wrote:
>> > Possible problems:
>> > * the two panels may be always instantiated, even if empty this may be
>> > not optimal memory and loading time wise
>> > * toolbar api still no defined
>> > * could som
On Thursday 08 October 2015, Aleix Pol wrote:
> > Possible problems:
> > * the two panels may be always instantiated, even if empty this may be
> > not optimal memory and loading time wise
> > * toolbar api still no defined
> > * could some content for the global drawer be there by default? do we
>
On Thursday 08 October 2015, Aleix Pol wrote:
> > * could some content for the global drawer be there by default? do we
> > leave a blank slate? even the hig examples are very heterogeneous
> > https://techbase.kde.org/Projects/Usability/HIG/GlobalDrawer
>
> Maybe you'd like to take a look at the
On Mon, Oct 5, 2015 at 4:50 PM, Marco Martin wrote:
> Hi all,
>
> Wall of text ahead, but please, don't just "mark as read" :p
> I want to have a proper discussion on components for the API of mobile
> components since via email looks a bit messy, maybe an etherpad document may
> be created that m
ListView's preferredHighlightBegin should do the trick.
Gesendet von meinem BlackBerry 10-Smartphone.
Originalnachricht
Von: Thomas Pfeiffer
Gesendet: Donnerstag, 8. Oktober 2015 18:18
An: plasma-devel@kde.org
Antwort an: plasma-devel@kde.org
Betreff: Re: HIG and components API
Another
Another thing about the context drawer:
Would it be possible to center the list of actions vertically so that it's
easier to reach with the thumb (at least if it has only a few actions)?
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kd
On Thursday 08 October 2015 14:51:35 Marco Martin wrote:
> On Thursday 08 October 2015, Thomas Pfeiffer wrote:
> > > 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 ;)
On Wednesday 07 October 2015 10:40:46 Marco Martin wrote:
> > > Moreover, I'm feeling that the api and the usage of the components will
> > > be quite intertwined with what will be the hig in the end.
> >
> > What exactly do you mean by that?
>
> that is very important that things are defined and
On Thursday 08 October 2015, Thomas Pfeiffer wrote:
> >
> > 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 ;)
https://www.youtube.com/watch?v=qHHWG_Qm2ks
(blackberry does
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 bett
On Wed, Oct 7, 2015 at 11:24 AM, Marco Martin wrote:
>> 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
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 list
On Wednesday 07 October 2015, Thomas Pfeiffer wrote:
> Yes, components are crucial both for consistency and for the adoption of
> the HIG. A HIG is supposed to make people's lives easier, not harder, and
> components that "automatically" comply with the HIG are an integral part
> of that.
>
> > Mo
On Tuesday 06 October 2015 17:09:25 Marco Martin wrote:
> On Tuesday 06 October 2015, Alex wrote:
> > > * could some content for the global drawer be there by default? do we
> > > leave a blank slate? even the hig examples are very heterogeneous
> > > https://techbase.kde.org/Projects/Usability/HIG
Hi Marco,
first of all: Thank you for starting this discussion. I know we should have
done that already, and I promise we'll make more use of the mailing list from
now on.
I will not go into too much detail about the reasoning/basic assumptions
behind our decisions, as that will be covered in a
On Tuesday 06 October 2015, Alex wrote:
> > * could some content for the global drawer be there by default? do we
> > leave a blank slate? even the hig examples are very heterogeneous
> > https://techbase.kde.org/Projects/Usability/HIG/GlobalDrawer
>
> Hi,
> thanks for you work. I discuss about th
In data lunedì 5 ottobre 2015 16:50:40, Marco Martin ha scritto:
> UI wise, things that i'm still not sure/not completely agree are:
> * side panels: i have as well one slightly semantically different kind of
> panel in which you slide out the app content to uncover the panel content
> instead (lik
Hi all,
Wall of text ahead, but please, don't just "mark as read" :p
I want to have a proper discussion on components for the API of mobile
components since via email looks a bit messy, maybe an etherpad document may
be created that may make things a bit easier with some formatting goodness
som
31 matches
Mail list logo
