Re: Review Request: Implement automatic scanning of source code for required data engines

2011-08-20 Thread Kevin Kofler

---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/102350/
---

(Updated Aug. 21, 2011, 1:47 a.m.)


Review request for Plasma.


Changes
---

The script engine API for Ruby is called "ruby-script", not "ruby" (for 
whatever reason).
(I also swapped the order of the Python and Ruby checks to put them into 
alphabetical order, which probably also happens to be the order of popularity.)


Summary
---

For packages in scripting languages and distributed through OCS, this is fully
automatic and triggered from Package::installPackage. If an
X-Plasma-RequiredDataEngines entry is present in the .desktop file (even if
empty), the dependency extraction is not run and the explicitly provided
information is trusted instead.

For native distribution packages, we ship a tool called
plasma-dataengine-depextractor which can be run at any time during the build
process and which adds the dependency information to the relevant .desktop file.

Authors of plasmoids are encouraged to run plasma-dataengine-depextractor and/or
fill in X-Plasma-RequiredDataEngines manually. (Please note that the list is
expected to be comma-separated.)

This is the final portion of my GSoC 2011 project.


Diffs (updated)
-

  plasma/CMakeLists.txt f929967 
  plasma/depextractor/depextractor.cpp PRE-CREATION 
  plasma/package.cpp 4c00d36 
  plasma/private/componentinstaller.cpp 870667f 
  plasma/private/componentinstaller_p.h f85cbb6 

Diff: http://git.reviewboard.kde.org/r/102350/diff


Testing
---

Compiles on Fedora 15.

Tested plasma-dataengine-depextractor on the weather plasmoid, it detected the 
dependency on the weather dataengine correctly and wrote a valid 
X-Plasma-RequiredDataEngines entry into the .desktop file.


Thanks,

Kevin

___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


R: Re: Plasma QML API - module is not installed

2011-08-20 Thread ag...@tiscali.it
I don't know "select allimport", what's it?I wrote a QML file and I imported it 
 in a widget with this code:
[...]m_qmlCategoryListView = new 
QDeclarativeView();[...]m_qmlCategoryListView->setSource(QUrl("qrc:/Qml/CategoryListView.qml"));






Messaggio originale
Da: notm...@gmail.com
Data: 20/08/2011 17.12
A: , "ag...@tiscali.it"
Ogg: Re: Plasma QML API - module is not installed

On Saturday 20 August 2011, ag...@tiscali.it wrote:
> Hi all.
> I have a problem with the Plasma QML API: when in qml file I write this:
> Code: Select allimport org.kde.plasma.graphicswidgets 0.1 as PlasmaWidgets
> in the output I find:
> Code: Select allqrc:/Qml/CategoryListView.qml:3:1: module
> "org.kde.plasma.graphicswidgets" is not installed Why?

Select allimport   ?

also, are you doing a qml plasmoid, using that qml code for something else 
or.. ?

-- 
Marco Martin





Tutto Incluso 20 Mega light: telefono + ADSL a soli 17,95 € al mese per 12 
mesi. Passa a Tiscali:  
http://abbonati.tiscali.it/rd/rd2.html?u=http%3A%2F%2Fabbonati.tiscali.it%2Ftelefono-adsl%2Fprodotti%2Ftc%2Ftuttoincluso_light%2F%3FWT.mc_id%3D01fw%26r=TS0A2%26dm=DM_03%26p=footer

___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: Plasma QML API - module is not installed

2011-08-20 Thread Marco Martin
On Saturday 20 August 2011, ag...@tiscali.it wrote:
> Hi all.
> I have a problem with the Plasma QML API: when in qml file I write this:
> Code: Select allimport org.kde.plasma.graphicswidgets 0.1 as PlasmaWidgets
> in the output I find:
> Code: Select allqrc:/Qml/CategoryListView.qml:3:1: module
> "org.kde.plasma.graphicswidgets" is not installed Why?

Select allimport   ?

also, are you doing a qml plasmoid, using that qml code for something else 
or.. ?

-- 
Marco Martin
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Plasma QML API - module is not installed

2011-08-20 Thread ag...@tiscali.it
Hi all.
I have a problem with the Plasma QML API: when in qml file I write this:
Code: Select allimport org.kde.plasma.graphicswidgets 0.1 as PlasmaWidgets
in the output I find:
Code: Select allqrc:/Qml/CategoryListView.qml:3:1: module 
"org.kde.plasma.graphicswidgets" is not installed
Why?

In the folder "/usr/lib/kde4/imports/org/kde/plasma/graphicswidgets/" there is 
libgraphicswidgetsbindingsplugin.so file.

In CMakeLists.txt there is: 
target_link_libraries(aaa
${QT_LIBRARIES}
${QT_QTDECLARATIVE_LIBRARY}
${KDE4_KDEUI_LIBS}
${KDE4_KPARTS_LIBS} 
${KDE4_PLASMA_LIBS}
${PACKAGEKIT_QT_LIBS})

Why does the module "org.kde.plasma.graphicswidgets" is not installed?
MpMp
I have Fedora 15

Tutto Incluso 20 Mega light: telefono + ADSL a soli 17,95 € al mese per 12 
mesi. Passa a Tiscali:  
http://abbonati.tiscali.it/rd/rd2.html?u=http%3A%2F%2Fabbonati.tiscali.it%2Ftelefono-adsl%2Fprodotti%2Ftc%2Ftuttoincluso_light%2F%3FWT.mc_id%3D01fw%26r=TS0A2%26dm=DM_03%26p=footer

___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: Review Request: Rework KMix DBus API and add KMix plasma dataengine

2011-08-20 Thread Mark Gaiser


> On Aug. 20, 2011, 1:22 a.m., Mark Gaiser wrote:
> > Hi,
> > 
> > I was just trying to do the same thing with kmix and wasted ~6 hours on 
> > that (or even more) just to find that is was already here but never 
> > committed. So how are we on this? Can this be committed?
> > 
> > Regards,
> > Mark

Sorry, it is already committed. I was looking for a commit hook message or a 
"Ship it!" message.. Guess it was "silently" committed. It can already be found 
in the current 4.7 codebase.
Sorry for the noise.


- Mark


---
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/6587/#review10358
---


On April 7, 2011, 8:40 a.m., Igor Poboiko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://svn.reviewboard.kde.org/r/6587/
> ---
> 
> (Updated April 7, 2011, 8:40 a.m.)
> 
> 
> Review request for Plasma and Diego Casella.
> 
> 
> Summary
> ---
> 
> This patch reworks KMix DBus API and adds a plasma dataengine+service as a 
> frontend to information provided by DBus.
> New DBus structure is:
>  - /Mixers
> used to get some global information, such as available mixers list and global 
> master mixer
>  - /Mixers/MIXER_ID
> used to get information about mixer with id=MIXER_ID. It provides such 
> information as list of available controls, name of this mixer, id, etc
>  - /Mixers/MIXER_ID/CONTROL_ID
> used to get and set information about control. Such information as volume 
> level, mute, name of control, etc.
> It also adds a DBus signals which are emitted when new mixer/control appears, 
> or volume level changes.
> It also splits all dbus-related code to separate class, 
> DBus{KMix,Mixer,Control}Wrapper.
> 
> The Plasma Dataengine:
> By default, the only available source is "KMix". It provides information 
> global information about KMix: is KMix running, and list of available mixers. 
> (its IDs)
> Source for every mixer is called by it's ID (for example, 
> "ALSA::HDA_Intel:1"). This source provides such information about current 
> Mixer as: it's readable name, is it opened, its balance and list of available 
> controls. It also adds basic sources for every control, which provides only 
> information about its readable name
> Sources for controls are called by 'MIXER_ID/CONTROL_ID' (for example, 
> "ALSA::HDA_Intel:1/Master:0"). If you request this source, it will provide 
> such information as its readable name, is it muted and its volume level 
> (which are updates automatically, using DBus signals).
> There is a service available for controls sources. It provides such methods 
> as setVolume() and setMute().
> 
> It doesn't close bug 171287, but it becomes one step closer to its solving :)
> 
> And, I'm not very familiar with CMake, but it would be great idea to make 
> plasma part optional.
> 
> 
> This addresses bug 171287.
> https://bugs.kde.org/show_bug.cgi?id=171287
> 
> 
> Diffs
> -
> 
>   /trunk/KDE/kdemultimedia/kmix/core/mixdevice.h 1225808 
>   /trunk/KDE/kdemultimedia/kmix/apps/kmix.cpp 1225808 
>   /trunk/KDE/kdemultimedia/kmix/CMakeLists.txt 1225808 
>   /trunk/KDE/kdemultimedia/kmix/core/mixdevice.cpp 1225808 
>   /trunk/KDE/kdemultimedia/kmix/core/mixer.h 1225808 
>   /trunk/KDE/kdemultimedia/kmix/core/mixer.cpp 1225808 
>   /trunk/KDE/kdemultimedia/kmix/dbus/dbuscontrolwrapper.h PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/dbus/dbuscontrolwrapper.cpp PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/dbus/dbusmixerwrapper.h PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/dbus/dbusmixerwrapper.cpp PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/dbus/dbusmixsetwrapper.h PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/dbus/dbusmixsetwrapper.cpp PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/dbus/org.kde.kmix.control.xml PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/dbus/org.kde.kmix.mixer.xml PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/dbus/org.kde.kmix.mixset.xml PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/gui/kmixdockwidget.cpp 1225808 
>   /trunk/KDE/kdemultimedia/kmix/plasma/CMakeLists.txt PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/plasma/engine/CMakeLists.txt PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/plasma/engine/mixer.operations PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/plasma/engine/mixerengine.h PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/plasma/engine/mixerengine.cpp PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/plasma/engine/mixerservice.h PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/plasma/engine/mixerservice.cpp PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/plasma/engine/plasma-engine-mixer.desktop 
> PRE-CREATION 
>   /trunk/KDE/kdemultimedia/kmix/tests/CMakeLists.txt 1225808 
> 
> Diff: http://svn.reviewboard.kde.org/r/6587/diff
> 

Re: ServiceJob binding in javascript not working in KDE 4.7?

2011-08-20 Thread Weng Xuetian
在 2011年8月20日 Saturday 10:14:41,Aaron J. Seigo 写道:
> On Saturday, August 20, 2011 13:47:21 Weng Xuetian wrote:
> > Hi Plasma World,
> > I'm trying to run this
>
> example:https://projects.kde.org/projects/kde/kdeexamples/repository/revisio
> ns/maste
> > r/entry/plasma/javascript/plasmoids/usingServices/
> > In spite of connectSource missing a time interval,
>
> the time interval is optional, and in this case it would even be incorrect
> to include a time interval. it is updated when the data in the DataEngine
> updates, which happens when the state of the media player changes. so there
> is no reason to have a time interval there.
>
Yes, I know it dataengine can push the value, but as far as I test this
example, without a time interval it will not get date update.

When I write my own dataengine and javascript plasmoid, I find the javascript
plasmoid get update only if I call checkForUpdates(), should I call this
function in data engine after setData()? I'm little confused here, because for
the previous QML test one, without checkForUpdates() the data will also get
updated immediately after dataengine updates it, I think setData() already can
trigger the update. Am I wrong or there is another bug in javascript binding?
>
> yes, this got broken (i think in 4.7). i'm not sure if this breakage was in
> our code or some change in Qt, but it no longer works, indeed. i've just
> fixed it for 4.7.1 and 4.8. sorry for the inconvenience :/
>
> we really need a comprehensive unit test set for the JS (and QML) bindings.
Thank you!

signature.asc
Description: This is a digitally signed message part.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: ServiceJob binding in javascript not working in KDE 4.7?

2011-08-20 Thread Aaron J. Seigo
On Saturday, August 20, 2011 13:47:21 Weng Xuetian wrote:
> Hi Plasma World,
> I'm trying to run this 
example:https://projects.kde.org/projects/kde/kdeexamples/repository/revisions/maste
> r/entry/plasma/javascript/plasmoids/usingServices/
> In spite of connectSource missing a time interval, 

the time interval is optional, and in this case it would even be incorrect to 
include a time interval. it is updated when the data in the DataEngine 
updates, which happens when the state of the media player changes. so there is 
no reason to have a time interval there.

> but the service job seems also not works.

yes, this got broken (i think in 4.7). i'm not sure if this breakage was in 
our code or some change in Qt, but it no longer works, indeed. i've just fixed 
it for 4.7.1 and 4.8. sorry for the inconvenience :/

we really need a comprehensive unit test set for the JS (and QML) bindings.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks


signature.asc
Description: This is a digitally signed message part.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel