On Wed, Jan 20, 2016 at 6:13 PM, Marco Martin <notm...@gmail.com> wrote: > https://notes.kde.org/p/plasma_mobile_components_breakout
Looking ionto the first issue, Action. I tought about just doing a simple QtObject in pure QML and be done with it, abut i see that in order to not lose features it needs to be something in c++ and in qt, to manage keyboard shortcuts. I know that purely on the phone keyboard shortcuts aren't really needed, but I would like to have things complete and not strictly for-factor specific. so my plan of action atm would be: * keep basing on Action on mobile components for the time being (just espanding it with a visible property and merging Action and ActionGroup) * try to submit a patch to QtGui by taking the code of the Action component and making it a public class usable from C++ as well (pretty much a QAction replacement for non qwidget apps) Probably there aren't huge chances of it being accepted, but at least worth a try. opinions/comments? -- Marco Martin _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
