Expose HomeWindow to QML

[giucam]

This allows to create an HomeWindow in a qml file and assign to it
a category and a child QQuickItem.

This is needed for nemomobile/lipstick-colorful-home#27

[rburchell]

@mikkoharju, mind taking a look?

[mikkoharju]

HomeWindow owns the root object. Setting the root object multiple times would leak here.

[giucam]

Indeed, I was not sure wether it should delete it there, since the object is created from outside. But it may well take the ownership, that's probably better than having a mixed behabior.

[mikkoharju]

LGTM if it takes the ownership

[mikkoharju]

I'm not 100% sure how ownership goes in

HomeWindow {
  rootObject: Item { .. }
}

Other options would be to have a Component property (so that HomeWindow creates and manages the root object):

HomeWindow {
  component: Component { Item { ... } } 
}

Or, expose the source property:

HomeWindow {
 source: "qml/LockScreen.qml"
}

[giucam]

I'm not 100% sure how ownership goes in

HomeWindow {
rootObject: Item { .. }
}

Are you saying it may have no parent()? I guess HomeWindow:.setRootObject could set that too. It is no different to http://qt-project.org/doc/qt-5.1/qtquick/qml-qtquick-window2-window.html#data-prop imho.

Other options would be to have a Component property (so that HomeWindow creates and manages the >root object):

HomeWindow {
component: Component { Item { ... } }
}

Maybe, but there is no need to create the item more than one time, so that seems a bit unefficient to me.

Or, expose the source property:

HomeWindow {
source: "qml/LockScreen.qml"
}

That's a good idea, but maybe it could work together with rootObject?

[mikkoharju]

Are you saying it may have no parent()?

I did a quick test and it would have the HomeWindow as parent. That's ok.

Maybe, but there is no need to create the item more than one time, so that seems a bit unefficient to me.

HomeWindow could create the object lazily on show() -- but I agree, does not make much sense.

[faenil]

@mikkoharju can this be merged?