Ok thanks Aaron!
On Mon, Jan 21, 2013 at 11:28 AM, Aaron J. Seigo wrote:
> On Monday, January 21, 2013 11:00:58 Paulo Nogueira wrote:
>> Thanks for your reply, Do you guys have any examples about how to do
>> that ?
>
> i don't know how QML import plugins will be done in python, but there are
> d
On Monday, January 21, 2013 11:00:58 Paulo Nogueira wrote:
> Thanks for your reply, Do you guys have any examples about how to do
> that ?
i don't know how QML import plugins will be done in python, but there are
dataengine examples in python on techbase and in the kdeexamples repository
(plasm
Hi Aaron,
Thanks for your reply, Do you guys have any examples about how to do
that ? also, I wonder when you guys are planning to release plasma 2?
Cheers,
Paulo Nogueira
On Mon, Jan 21, 2013 at 2:50 AM, Aaron J. Seigo wrote:
> On Friday, January 18, 2013 17:11:52 Paulo Nogueira wrote:
>> In m
On Friday, January 18, 2013 17:11:52 Paulo Nogueira wrote:
> In my opinion it should be a developer decision, like if I want to
> keep all of my code in C++, why not ?
even with C++, all the UI is done with QML. there is no "UI done in C++" with
libplasma2. only business logic and custom QML comp
On 19 January 2013 03:11, Paulo Nogueira wrote:
> but I'm not quite convinced about the
> radical way where all widgets UI must be done using QML.
>
Can you tell me why we shouldn't put all the widgets UI in QML?
(This is a normal question, I can't thing 1 reason why we shouldn't)
just a few r
Hi Aaron,
Thanks for the quick reply, I can understand the reasons why the
widgets should not be made using python (opening one interpreter for
each widget for example), but I'm not quite convinced about the
radical way where all widgets UI must be done using QML.
In my opinion it should be a dev
On Fri, Jan 18, 2013 at 10:26 AM, Marco Martin wrote:
> On Friday 18 January 2013, Aleix Pol wrote:
>
> > If we can leverage the bindings to Qt, we reduce complexity and we get a
> > lot of stuff for free that will be also more re-usable in other
> > applications.
> >
> > ...no? :)
>
> no :p
>
>
On Friday 18 January 2013, Aleix Pol wrote:
> If we can leverage the bindings to Qt, we reduce complexity and we get a
> lot of stuff for free that will be also more re-usable in other
> applications.
>
> ...no? :)
no :p
as i already explainer there back in randa, there are tons of occasions an
On Mon, Jan 14, 2013 at 4:33 PM, Luca Beltrame wrote:
> In data lunedì 14 gennaio 2013 16:30:15, Aaron J. Seigo ha scritto:
>
> > the real fix, however, is not to do the UI in python. use QML.
>
> Speaking of that, how does Plasma (or the workspace in general) fit when
> using
> QML, according to
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
On Tuesday, January 15, 2013 13:47:32 Paulo Nogueira wrote:
> So the python support will be there, and if I don't want to write QML
> UI. Would it be possible to still writing the UI using python ?
this is a bit like asking "If I don't want to use QGraphicsView, can I still
write the UI using pyt
So the python support will be there, and if I don't want to write QML
UI. Would it be possible to still writing the UI using python ?
Cheers,
Paulo Nogueira
On Tue, Jan 15, 2013 at 11:59 AM, Simon Edwards wrote:
> Hello,
>
>
> On 01/15/2013 02:47 PM, Aaron J. Seigo wrote:
>>
>> so when it com
Hello,
On 01/15/2013 02:47 PM, Aaron J. Seigo wrote:
so when it comes to python support in future, there are 2 possibilities i can
see:
* python bindings for Applet, but all the UI still done in QML and python gets
used as we currently use C++ for hybrid applets
* we decide that all extensions
I can see that you guys are moving in favor of QML. I wonder if you
guys are going to drop the python support for widgets in Plasma 2 ?
Cheers,
Paulo Nogueira
On Tue, Jan 15, 2013 at 6:18 AM, Marco Martin wrote:
> On Tuesday 15 January 2013, Luca Beltrame wrote:
>> In data martedì 15 gennaio 201
On Tuesday 15 January 2013, Luca Beltrame wrote:
> In data martedì 15 gennaio 2013 14:47:31, Aaron J. Seigo ha scritto:
> > * we decide that all extensions to QML are done through Plasma plugins
> > (services, dataengines, etc.) or QML imports. this would mean there would
> > be
>
> To be honest,
In data martedì 15 gennaio 2013 14:47:31, Aaron J. Seigo ha scritto:
> * we decide that all extensions to QML are done through Plasma plugins
> (services, dataengines, etc.) or QML imports. this would mean there would be
To be honest, I would much prefer this strategy myself. On the long run, it
On Monday, January 14, 2013 17:50:00 Luca Beltrame wrote:
> The bindings are there because libplasma is in kdelibs, and as such they are
in libplasma2, all of the widget bits (QGraphicsView stuff currently) are moved
outside. there is literally no widget bits to bind to in libplasma2.
so when it
Hi Guys, thanks for your's replies.
Looks like even implementing the sizeHint for Plasma.WebView it does
not work. So I fixed it by replacing the Plasma.WebView for the
QtWebKit.QGraphicsWebView and now it works as expected.
More details can be found here:
http://pastebin.com/HhMwsD9R
Cheers,
Pa
In data lunedì 14 gennaio 2013 17:39:12, Aaron J. Seigo ha scritto:
(apologies if this comes doubled, wrong address in the "From" field)
[Plasma Python bindings]
> do we need python bindings?
The bindings are there because libplasma is in kdelibs, and as such they are
provided by PyKDE4 (which c
On Monday, January 14, 2013 16:33:48 Luca Beltrame wrote:
> In data lunedì 14 gennaio 2013 16:30:15, Aaron J. Seigo ha scritto:
> > the real fix, however, is not to do the UI in python. use QML.
>
> Speaking of that, how does Plasma (or the workspace in general) fit when
> using QML, according to
In data lunedì 14 gennaio 2013 16:30:15, Aaron J. Seigo ha scritto:
> the real fix, however, is not to do the UI in python. use QML.
Speaking of that, how does Plasma (or the workspace in general) fit when using
QML, according to these 3 definitions (taken from the PyQt docs):
1. Pure applicatio
On Sunday, January 13, 2013 21:16:16 Paulo Nogueira wrote:
> I'm writing a very basic plasma widget using PyQt and QWebKit, where
> I'm trying to set a custom size for my widget bellow of 128px.
could be due to this in the implementation of Plasma::WebView:
QSizeF WebView::sizeHint(Qt::SizeHint w
30 matches
Mail list logo
