Well, still unable to get my view to display anything with my
dataengine's sources...I've tried all kinds of variations, too...and
loads of code examples, including kde and qt's. None nicely match my
scenario, from what I could tell. I've tried keysForSource, simply
model: mainEngineSource.sources
> First I wanted to ask why is it that c++ plasmoids are getting ported to
> QML, will plasma only support QML plasmoids in the future or something?
Not really, it's just the recommended way of doing so. In general it
eases maintainability, access for designers, and makes it easier to
craft a UI w
hi ml,
I'm working on a project in nepomuk (something called project integrator). I
wanted to make a plasmoid for that. I know that it can be done using either
c++ or python. Now I know that there is a gsoc project where most of the c++
plasmoids are being ported to QML.
First I wanted to ask why
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101585/
---
(Updated July 7, 2011, 9:35 p.m.)
Review request for Plasma.
Changes
---
Hi,
I am making plasma widgets to connect to a dataengine, which requests data
from a remote API. I use widgets to construct a URL, which I pass as a
source to the dataengine. When I use plasmaengineexplorer, I am able to
create the source, and view the desired data. I tried connecting the
dataeng
> On July 6, 2011, 1:31 p.m., Aaron J. Seigo wrote:
> > what is the use case for the checkbox? it is nicely implemented and all,
> > but i'm not sure what the real value of it is, versus the cost of having it
> > in the user interface and making it more complex?
> >
> > also, the set of button
On Thursday 07 July 2011, Shaun Reich wrote:
> I'm using the following code:
>
> model : PlasmaCore.DataModel {
> dataSource: mainEngineSource.keysForSource["name"]
> }
>
> Yet I keep receiving:
>
> main.qml:100: Unable to assign [undefined] to QObject* dataSource
>
> I thought perhaps this
