components components components

[Marco Martin]

On Friday 04 November 2011, Sebastian Kügler wrote:
> On Thursday, November 03, 2011 20:26:58 Marco Martin wrote:
> > the second solution seems more elegant, but much more error prone since
> > every  c++ app the uses qml will have to add the import paths in the
> > proper order or crazy problems will happen
> 
> We should factor out the C++ parts we duplicate in our apps and make a
> generic class from it, Plasma::ActiveApp, that one would be the toplevel
> view for our apps and do the importing accordingly.
> 
> I think there's enough "not entirely straight-forward" code in there that
> this would be a good idea. API can be pretty minimal, I think.

yep, i agree.

for plasmoids it doesn't matter, all can be enveloped in 
Plasma::DeclarativeWidgets, for applications, perhaps a class that gives you a 
view with a main qml component loaded from a package with all the right 
things(tm) done to the engine could be nice.

for the device specific components:
what about installing them in 
/usr/lib/kde4/platformimports/desktop
/usr/lib/kde4/platformimports/tablet

then /usr/lib/kde4/platformimports/tablet or 
/usr/lib/kde4/platformimports/desktop could be used depending to some 
configuration file

this means also a change in the standard cmake files to have a 
${PLATFORMIMPORTS_INSTALL_DIR} global variable

everybody ok with this?

Cheers,
Marco Martin