On Tue, Jul 26, 2016 at 3:36 AM, Aleix Pol wrote:
>
> Hi Harish,
> What are you trying to do? What do you need it for?
Oh sorry, I should have mentioned it earlier. I'm trying to work on
porting plasma's publictransport applet to plasma5. The dataengine
downloads documents(serviceProviders) and pa
On Mon, Jul 25, 2016 at 11:37 PM, R.Harish Navnit
wrote:
> Hi,
>
> In Qt4, we had qtscriptgenerator which helped in generating Qt
> bindings, which are needed to import qt extensions to QScriptEngine
> etc. However, AFAIK this hasn't made it to Qt5 or at least there, is
> no official release yet.
Hi,
In Qt4, we had qtscriptgenerator which helped in generating Qt
bindings, which are needed to import qt extensions to QScriptEngine
etc. However, AFAIK this hasn't made it to Qt5 or at least there, is
no official release yet.
Can anyone point me to or show me how one can generate Qt script
bin
JavaScript.
>>
>
> very nice! is this using the QtScript bindings or the Lively engine directly,
> or?
>
The system is based directly to QtScript bindings. We're using a single
plasmoid (containing QtScript VM + bindings) that loads a predefined JS
script, which can then
, a plain old map application, and a map that is augmented
> with web camera feeds coming from different points of interests. All the
> plasmoids are nicely responsive and work pretty well. All application
> logic is implemented with JavaScript.
very nice! is this using the QtScript bindings or
> smoke based? have you looked into the qscript generator that Kent @ Qt
> has been working on (for a long time now ... i wonder why there isn't more
> news about it by now...)
Please check with Kent whether there has been any change on this but
last I looked
at the binding generator (shortly afte
Marco Martin wrote:
> the api of plasma widget is limited to protect the simple js bindings, in the
> full ones there could be the access to nativeWidget() i suppose, so they
> could
> have the full api of the underlying embedded qwidget
>
Doing this would result in an extremely powerful scri
On Tuesday 15 September 2009, Tommi Mikkonen wrote:
> Aaron J. Seigo wrote:
> > Frame is not a QFrame, it's a Plasma::Frame.
> > WebView is not a QWebView, it's a Plasma::WebView.
>
> Ok, accepted; the problem is that I'm aiming at porting
> from QtScript to Plasma, and this is one of the things wh
On Monday 14 September 2009, Tommi Mikkonen wrote:
> Aaron J. Seigo wrote:
> > On September 14, 2009, Tommi Mikkonen wrote:
> >> Having said that, what I would also like is a harmonized API; having
> >> finally spend some hours tonight (after traveling in conferences for
> >> some weeks!) on JS Pla
Aaron J. Seigo wrote:
> Frame is not a QFrame, it's a Plasma::Frame.
> WebView is not a QWebView, it's a Plasma::WebView.
>
Ok, accepted; the problem is that I'm aiming at porting
from QtScript to Plasma, and this is one of the things where
I constantly make mistakes. Can I create a QFrame insi
On September 14, 2009, Tommi Mikkonen wrote:
> > can you provide some concrete examples?
>
> QFrame vs. Frame and QWebView vs. Webview is QtScriptGenerator and
> Plasmoids,
Frame is not a QFrame, it's a Plasma::Frame.
WebView is not a QWebView, it's a Plasma::WebView.
> and at the same time Qt
Aaron J. Seigo wrote:
> On September 14, 2009, Tommi Mikkonen wrote:
>
>> Having said that, what I would also like is a harmonized API; having
>> finally spend some hours tonight (after traveling in conferences for
>> some weeks!) on JS Plasmoid development with Lively content, I
>> constantly s
On September 14, 2009, Tommi Mikkonen wrote:
> Having said that, what I would also like is a harmonized API; having
> finally spend some hours tonight (after traveling in conferences for
> some weeks!) on JS Plasmoid development with Lively content, I
> constantly seem to have problems on the names
Aaron J. Seigo wrote:
> On September 14, 2009, Tommi Mikkonen wrote:
>
>> What I'd personally like to do is to create the same stuff downloadable
>> at lively.cs.tut.fi/qt inside a plasmoid using plain JavaScript. In
>>
>
> once we have full qt/kdelibs bindings available to us, this should
On September 14, 2009, Tommi Mikkonen wrote:
> What I'd personally like to do is to create the same stuff downloadable
> at lively.cs.tut.fi/qt inside a plasmoid using plain JavaScript. In
once we have full qt/kdelibs bindings available to us, this should be trivial.
it would be really interestin
We already talked about this on IRC, so just recording for everyone else.
On Mon, Sep 14, 2009 at 12:14 PM, Aaron J. Seigo wrote:
> On September 14, 2009, Ian Monroe wrote:
>> Do you want bindings of the chunks of the Qt api + Plamsa API? Or just
>> a simplified subset of the Plasma API?
>
> both
onroe wrote:
> Mark said you were interested in QtScript bindings.
>
> Do you want bindings of the chunks of the Qt api + Plamsa API? Or just
> a simplified subset of the Plasma API?
>
> If its the former, we should talk. :) I've started the very beginnings
> of a Smoke-based
On September 14, 2009, Ian Monroe wrote:
> Do you want bindings of the chunks of the Qt api + Plamsa API? Or just
> a simplified subset of the Plasma API?
both, as separate entities; and we already have the latter in fairly decent
shape at this point.
> If its the former, we should talk. :) I've
Mark said you were interested in QtScript bindings.
Do you want bindings of the chunks of the Qt api + Plamsa API? Or just
a simplified subset of the Plasma API?
If its the former, we should talk. :) I've started the very beginnings
of a Smoke-based binding.
If its the latter, then you r
19 matches
Mail list logo
