On Wednesday, January 16, 2013 20:48:35 Simon Edwards wrote:
> On 01/16/2013 02:44 PM, Marco Martin wrote:
> > On Wednesday 16 January 2013, Sebastian Kügler wrote:
> >> So you'd write a set of QObject deriven classes in Python (you can use
> >> various existing third party libraries for that, if y
On 01/16/2013 02:44 PM, Marco Martin wrote:
On Wednesday 16 January 2013, Sebastian Kügler wrote:
So you'd write a set of QObject deriven classes in Python (you can use
various existing third party libraries for that, if you wish so), but they
don't have any UI in them, they just offer non-visua
On Wednesday, January 16, 2013 14:52:41 Luca Beltrame wrote:
> In data mercoledì 16 gennaio 2013 14:44:24, Marco Martin ha scritto:
> > slots defined in those python classes would not visible from qml, due to
> > how it internally works (they are not in the static metadata object that
> > can't be
On Wednesday 16 January 2013, Sebastian Kügler wrote:
> On Wednesday, January 16, 2013 15:29:08 Aaron J. Seigo wrote:
> > On Wednesday, January 16, 2013 14:38:28 Sebastian Kügler wrote:
> > > So you'd write a set of QObject deriven classes in Python (you can use
> >
> > ..
> >
> > > These python
On Wednesday, January 16, 2013 15:29:08 Aaron J. Seigo wrote:
> On Wednesday, January 16, 2013 14:38:28 Sebastian Kügler wrote:
> > So you'd write a set of QObject deriven classes in Python (you can use
>
> ..
>
> > These python extensions would then be imported into the context of the
> > (QML)
On Wednesday, January 16, 2013 14:38:28 Sebastian Kügler wrote:
> So you'd write a set of QObject deriven classes in Python (you can use
..
> These python extensions would then be imported into the context of the (QML)
this should be done via qml imports or libplasma plugins. is there any case
whe
In data mercoledì 16 gennaio 2013 14:44:24, Marco Martin ha scritto:
> slots defined in those python classes would not visible from qml, due to how
> it internally works (they are not in the static metadata object that can't
> be touched at runtime, at least not outside of Qt)
You are correct (se
On Wednesday 16 January 2013, Sebastian Kügler wrote:
> On Wednesday, January 16, 2013 11:41:05 Aaron J. Seigo wrote:
> > the possibility exists for us to support Applets which are written in
> > python but which use QML for the user visible parts. you'd still need to
> > write and ship QML, but m
On Wednesday, January 16, 2013 11:41:05 Aaron J. Seigo wrote:
> the possibility exists for us to support Applets which are written in
> python but which use QML for the user visible parts. you'd still need to
> write and ship QML, but maybe you could do some behind-the-scenes parts in
> python. th
