HIG and components API

[Marco Martin]

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
> > 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 qml-material components [1].
> I've looked into them, they seem high quality and have some
> interesting concepts.

also (as an author of an application with an android port)
what do you think our components should have over those or something self-made 
in order for somebody to chose ours when considering porting a KDE application 
to mobile?
what would you look for?

-- 
Marco Martin