Kirigami: a feature needed for subsurface and api change feedback

[kainz.a]

Webbrowser: new tab, edit url, top page
Image viewer: export, edit,
Am 18.04.2016 19:34 schrieb "Kai Uwe Broulik" <kde at privat.broulik.de>:

> 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:notmart at gmail.com
> Gesendet:18. April 2016 7:30 nachm.
> An:plasma-devel at kde.org
> Antworten:plasma-devel at kde.org
> Cc:subsurface at subsurface-divelog.org
> Betreff:Kirigami: a feature needed for subsurface and api change feedback
>
> 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
> at most three buttons, and this of course influences the final API: there
> should then be 3 separate actions properties instead of a list of an
> arbitrary
> number of actions, like it happens for context menu actions
>
> In my first working approach, the API looks like this, leftAction and
> rightAction properties work just like mainAction controls the central
> button:
>
> Page {
> mainAction: Action {...}
> leftAction: Action {...}
> rightAction: Action {...}
>     contextualActions: [
>        Action {...},
> Action{...}
> ]
> }
>
> Now, since we are still at a prerelease state, I would like a little api
> change.
> In QML, is usually considered good manner to group together similar
> properties, to obtain code more tied together and less repeated words in
> property names (such as mainAction LeftAction whateverAction)
>
> for instance you define anchors like
> Item {
> anchors {
> left: parent.left
> right: parent.right
> ...
> }
> }
>
> following this, the api of Page would look like this:
>
> Page {
> actions {
> main: Action {...}
> left: Action {...}
> right: Action {...}
>     contextualActions: [
>        Action {...},
> Action{...}
> ]
> }
> }
>
> opinions? comments? (would be a problem for subsurface for eventually
> adapting
> existing stuff to new api?)
>
> --
> Marco Martin
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20160418/e518eea9/attachment.html>