Re: dictionary widget QML

2012-02-05 Thread Shaun Reich 
bit of a snag...how can i create a model/listview from
plasmasource.data["list-dictionaries"] ?

there's 1 source which has many keys and values, as you'll see by
requesting that source from plasmaengineexplorer.

thought of a model of a model, but that's not possible ;-p

got to be an easy way...

-- 
Shaun Reich,
KDE Software Developer (kde.org)
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Review Request: Plasma HDD Activity/IO system monitor applet creation

2012-02-05 Thread Shaun Reich 

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

Review request for Plasma, Aaron J. Seigo and Marco Martin.


Description
---

Made a plasma applet that monitors hard disk I/O, aka throughput/activity.

Planning on merging it into master workspace, as the other sysmon applets are 
there, and hdd activity is actually a really common request.

it should be Most Probably Totally Bug Free™ as well. though i'm having 
difficulties testing the case for when it's in the panel, but i can test & fix 
once it gets merged easily.

I apologize for how nasty the diff looks...i'm surprised reviewboard doesn't 
have an ability to just upload a file and diff it against nothing.

a lot of the bugs related to this applet and the other applets, are due to the 
main base class that all of them derive from, so i will fix more of that/those 
soon as well (i've already fixed quite a few of them).


Diffs
-

  plasma/generic/applets/system-monitor/CMakeLists.txt 0f74eb6 
  plasma/generic/applets/system-monitor/hdd-activity-config.ui e641c8a 
  plasma/generic/applets/system-monitor/hdd_activity-config.ui PRE-CREATION 
  plasma/generic/applets/system-monitor/hdd_activity.h f74af85 
  plasma/generic/applets/system-monitor/hdd_activity.cpp 5762d6d 
  plasma/generic/applets/system-monitor/plasma-applet-sm_hdd_activity.desktop 
d3bb6b6 

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


Testing
---

42


Thanks,

Shaun Reich

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

Re: Review Request: Less repainting on mousePressEvent(), moseReleaseEvent() and mouseDoubleClickEvent() in FolderView::IconView

2012-02-05 Thread Ignat Semenov 


> On Feb. 5, 2012, 6:46 p.m., Fredrik Höglund wrote:
> > Aside from some minor nitpicks, it looks good.

I forgot to add that I couldn't optimize the right click path in 
mousePressEvent(). The problem is that in order to get the containment context 
menu, the RMB press event is propagated to the parent and triggers an 
unconditional repaint. I confirmed this behavior by removing all the 
markAreaDirty() calls in that path - then view still repainted fine. Thus, a 
right click repaints the whole view, voiding the optimization of that code 
path. Any ideas?

The optimization in that branch is there just for the sake completeness - the 
view will repaint fully anyway.


> On Feb. 5, 2012, 6:46 p.m., Fredrik Höglund wrote:
> > plasma/applets/folderview/iconview.cpp, line 1803
> > 
> >
> > Make these const. There is also a whitespace error on this line.

Sorry, my fault. I will make a big poster "const correctness and git diff 
--check" and place it on the wall above the desk  ;)


> On Feb. 5, 2012, 6:46 p.m., Fredrik Höglund wrote:
> > plasma/applets/folderview/iconview.cpp, line 2605
> > 
> >
> > Change the name of this variable to 'rect'.

Indeed, it is not necessarily dirty. Copy-paste :)


- Ignat


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


On Jan. 29, 2012, 3:54 p.m., Ignat Semenov wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/103822/
> ---
> 
> (Updated Jan. 29, 2012, 3:54 p.m.)
> 
> 
> Review request for Plasma, Aaron J. Seigo and Marco Martin.
> 
> 
> Description
> ---
> 
> This patch aims to save some repaints in FolderView::IconView on the various 
> mouseEvent()'s by choosing what to repaint in a bit smarter way.
> 
> 
> Diffs
> -
> 
>   plasma/applets/folderview/iconview.h 66ccb98 
>   plasma/applets/folderview/iconview.cpp 5b0cd98 
> 
> Diff: http://git.reviewboard.kde.org/r/103822/diff/diff
> 
> 
> Testing
> ---
> 
> Testing done against master, seems to behave indentically.
> 
> 
> Thanks,
> 
> Ignat Semenov
> 
>

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

Fwd: GSOC Mentor

2012-02-05 Thread heathmatlock 
-- Forwarded message --
From: heathmatlock 
Date: Sat, Feb 4, 2012 at 12:08 PM
Subject: GSOC Mentor
To: kde-...@kde.org


Eike Hein has been mentoring me through the process of becoming a KDE
developer, and I'm working on a project dubbed Qanda which adds
natural language processing to krunner. I'm in need of someone
reviewing my proposal and a willing mentor for this year's GSOC.

Any takers?

--
Heath Matlock
+1 256 274 4225


-- 
Heath Matlock
+1 256 274 4225
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: QML global plasmoid callback problem

2012-02-05 Thread uomonero 
2012/2/5 uomonero :
> 2012/2/5 Marco Martin :
>> On Sun, Feb 5, 2012 at 3:39 PM, uomonero  wrote:
>>> Hi,
>>> I'm new to plasmoid development. I'm trying to learn how to write a
>>> QML plasmoid, but I encountered a little difficulty with the use of
>>> global plasmoid object.
>>>
>>> This is my simple test code:
>>>
>>> import QtQuick 1.0
>>> import org.kde.plasma.core 0.1 as PlasmaCore
>>> import org.kde.plasma.components 0.1 as PlasmaComponents
>>>
>>> PlasmaComponents.Label{
>>>        id: labelTest
>>>        text:"Test"
>>>
>>>        Component.onCompleted:{
>>>                plasmoid.addEventListener("sizeChanged", sizeChanged);
>>>        }
>>>        function sizeChanged(){
>>>                print("sizeChanged listener");
>>>        }
>>> }
>>>
>>> Running with plasmoidviewer, when I resize the plasmoid nothing is printed.
>>> What's wrong?
>>
>>
>> uhm, apart that sizeChanged in particular isn't really necessary since
>> the size is the size of the root item, if that label is the plasmoid
>> main script it should work fine
>>
>
> Thanks, Marco.
> Yes, the Label is the plasmoid main script, but the callback just don't work.
> I tryed also with "userConfiguring" callbacks with same result. The
> sizeChanged function does not seem to be invoked when expected.
>
> Any suggestion for event debugging?

A little update:
Callback on ConfigChanged worked.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Review Request: Less repainting on mousePressEvent(), moseReleaseEvent() and mouseDoubleClickEvent() in FolderView::IconView

2012-02-05 Thread Fredrik Höglund 

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

Ship it!


Aside from some minor nitpicks, it looks good.


plasma/applets/folderview/iconview.cpp


Make these const. There is also a whitespace error on this line.



plasma/applets/folderview/iconview.cpp


Change the name of this variable to 'rect'.


- Fredrik Höglund


On Jan. 29, 2012, 3:54 p.m., Ignat Semenov wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/103822/
> ---
> 
> (Updated Jan. 29, 2012, 3:54 p.m.)
> 
> 
> Review request for Plasma, Aaron J. Seigo and Marco Martin.
> 
> 
> Description
> ---
> 
> This patch aims to save some repaints in FolderView::IconView on the various 
> mouseEvent()'s by choosing what to repaint in a bit smarter way.
> 
> 
> Diffs
> -
> 
>   plasma/applets/folderview/iconview.h 66ccb98 
>   plasma/applets/folderview/iconview.cpp 5b0cd98 
> 
> Diff: http://git.reviewboard.kde.org/r/103822/diff/diff
> 
> 
> Testing
> ---
> 
> Testing done against master, seems to behave indentically.
> 
> 
> Thanks,
> 
> Ignat Semenov
> 
>

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

Re: Python plasmoid and configChanged()

2012-02-05 Thread Simone Gaiarin 
Connecting configChanged() explicitly was the cause of the problem
apparently (I need to test it a little bit more). In many forum I've
found that the people suggest to do this connection, maybe it's old
stuff.

Another strange thing I noticed is that when I click OK in the config
dialog it does not close immediatly itself but it waits the end of the
function configChanged() and since in my case this function takes
about 10 seconds to complete the config dialog remain frozen for 10
seconds before closing.

I tried a workaround to avoid this behaviour trying to emit a custom
signal at the end of configChanged that activate the slow function,
but even in this case the config dialog waits. Any idea on how to
solve this?

2012/2/5 Aaron J. Seigo :
> On Sunday, February 5, 2012 15:16:03 Simone Gaiarin wrote:
>> I call configChanged() once in the init function and then I connect it
>> to the configChanged() signal.
>
> you don't need to connect it to any signal. i'm not sure if that's the cause
> of your problem, but it is unecessary in any case.
>
> and just in case something odd is going on .. the init function is indeed only
> being called once, correct?
>
> --
> Aaron J. Seigo
> ___
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Python plasmoid and configChanged()

2012-02-05 Thread Aaron J. Seigo 
On Sunday, February 5, 2012 15:16:03 Simone Gaiarin wrote:
> I call configChanged() once in the init function and then I connect it
> to the configChanged() signal.

you don't need to connect it to any signal. i'm not sure if that's the cause 
of your problem, but it is unecessary in any case.

and just in case something odd is going on .. the init function is indeed only 
being called once, correct?

-- 
Aaron J. Seigo

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: dictionary widget QML

2012-02-05 Thread Marco Martin 
On Sun, Feb 5, 2012 at 4:47 PM, Shaun Reich  wrote:
>> anyways having 100% of the default applets in pure qml is a very long
>> term plan, since on the desktop plasma2 would continue to use a legacy
>> compatible version with qgraphicsview for a (probably) long time
>
> sure, but i'm trying to change that 1% at a time ;-)

and for that, you're a hero (and i'm completely serious right now :p)
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: QML global plasmoid callback problem

2012-02-05 Thread uomonero 
2012/2/5 Marco Martin :
> On Sun, Feb 5, 2012 at 3:39 PM, uomonero  wrote:
>> Hi,
>> I'm new to plasmoid development. I'm trying to learn how to write a
>> QML plasmoid, but I encountered a little difficulty with the use of
>> global plasmoid object.
>>
>> This is my simple test code:
>>
>> import QtQuick 1.0
>> import org.kde.plasma.core 0.1 as PlasmaCore
>> import org.kde.plasma.components 0.1 as PlasmaComponents
>>
>> PlasmaComponents.Label{
>>        id: labelTest
>>        text:"Test"
>>
>>        Component.onCompleted:{
>>                plasmoid.addEventListener("sizeChanged", sizeChanged);
>>        }
>>        function sizeChanged(){
>>                print("sizeChanged listener");
>>        }
>> }
>>
>> Running with plasmoidviewer, when I resize the plasmoid nothing is printed.
>> What's wrong?
>
>
> uhm, apart that sizeChanged in particular isn't really necessary since
> the size is the size of the root item, if that label is the plasmoid
> main script it should work fine
>

Thanks, Marco.
Yes, the Label is the plasmoid main script, but the callback just don't work.
I tryed also with "userConfiguring" callbacks with same result. The
sizeChanged function does not seem to be invoked when expected.

Any suggestion for event debugging?
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: dictionary widget QML

2012-02-05 Thread Shaun Reich 
> anyways having 100% of the default applets in pure qml is a very long
> term plan, since on the desktop plasma2 would continue to use a legacy
> compatible version with qgraphicsview for a (probably) long time

sure, but i'm trying to change that 1% at a time ;-)


-- 
Shaun Reich,
KDE Software Developer (kde.org)
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: dictionary widget QML

2012-02-05 Thread Marco Martin 
On Sun, Feb 5, 2012 at 3:49 PM, Shaun Reich  wrote:
> On Sun, Feb 5, 2012 at 8:58 AM, Marco Martin  wrote:
>> On Sun, Feb 5, 2012 at 2:46 PM, Aaron J. Seigo  wrote:
 if you want to make this choseable by the kcm it would have to become
 a (partly) c++ plasmoid
>>>
>>> assuming that it is unnecessary, even unwanted (different instances of the
>>> plasmoid -> different dicts?), this could in theory be done straight from 
>>> the
>>> plasmoid. but this is where (again) the KConfigXt+Qt Designer pair let us 
>>> down;
>>
>> uh, and forgotted to add: in this case yes, doing it directly from the
>> plamoid would be a sensible enough workflow:
>> * click the dict icon (that right now doesn't do anything)
>> * in the results area it shows the list of available dicts
>> * select one
>
> what widget should it use to select the thingies? you want iti to be
> clear that they -can- be choosen.

just a listview, with the usual highlight item on mouse over to show
it can be selected.

> i can't believe the kconfig/qtdesigner "let us down". does it not
> allow bidirectional communication, like populating a listview and
> choosing it; it would only allow e.g. selecting buttons. man, we
> really need a goof fiix for that.

it's by design almost useless without c++.

with kconfigxt is possible to map some simple things, like booleans to
checkboxes and strings to text fields, but nothing more complex.
for instance pupulating lists you really can't get away with
qtdesigner without dedicated imperative code.

so while it's good for what it is, i don't think we want here not even
a temporary fix for it. (while it theory is possible to write qwidget
qml bindings that don't involve qgraphicsview or proxy widgets at all,
would be batshit crazy to even attempt a monstrosity like that :p)

>
> i suppose it could look even better for plasmoids to have as much
> config as possible inside them. if it's at all feasible. though you
> get the issue with popup applets doing their thing.

popupapplet just work.
the problem is when you need a popup applet that doesn't have an icon
but draws its own thing.
in this case a Dialog has to be managed by hand.

looking at the current set of plasmoids, some of them will be possible
some not, some only as in part C++, and that's fine.
anyways having 100% of the default applets in pure qml is a very long
term plan, since on the desktop plasma2 would continue to use a legacy
compatible version with qgraphicsview for a (probably) long time


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

Re: QML global plasmoid callback problem

2012-02-05 Thread Marco Martin 
On Sun, Feb 5, 2012 at 3:39 PM, uomonero  wrote:
> Hi,
> I'm new to plasmoid development. I'm trying to learn how to write a
> QML plasmoid, but I encountered a little difficulty with the use of
> global plasmoid object.
>
> This is my simple test code:
>
> import QtQuick 1.0
> import org.kde.plasma.core 0.1 as PlasmaCore
> import org.kde.plasma.components 0.1 as PlasmaComponents
>
> PlasmaComponents.Label{
>        id: labelTest
>        text:"Test"
>
>        Component.onCompleted:{
>                plasmoid.addEventListener("sizeChanged", sizeChanged);
>        }
>        function sizeChanged(){
>                print("sizeChanged listener");
>        }
> }
>
> Running with plasmoidviewer, when I resize the plasmoid nothing is printed.
> What's wrong?


uhm, apart that sizeChanged in particular isn't really necessary since
the size is the size of the root item, if that label is the plasmoid
main script it should work fine

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

Re: dictionary widget QML

2012-02-05 Thread Shaun Reich 
On Sun, Feb 5, 2012 at 8:58 AM, Marco Martin  wrote:
> On Sun, Feb 5, 2012 at 2:46 PM, Aaron J. Seigo  wrote:
>>> if you want to make this choseable by the kcm it would have to become
>>> a (partly) c++ plasmoid
>>
>> assuming that it is unnecessary, even unwanted (different instances of the
>> plasmoid -> different dicts?), this could in theory be done straight from the
>> plasmoid. but this is where (again) the KConfigXt+Qt Designer pair let us 
>> down;
>
> uh, and forgotted to add: in this case yes, doing it directly from the
> plamoid would be a sensible enough workflow:
> * click the dict icon (that right now doesn't do anything)
> * in the results area it shows the list of available dicts
> * select one

what widget should it use to select the thingies? you want iti to be
clear that they -can- be choosen.

i can't believe the kconfig/qtdesigner "let us down". does it not
allow bidirectional communication, like populating a listview and
choosing it; it would only allow e.g. selecting buttons. man, we
really need a goof fiix for that.

i suppose it could look even better for plasmoids to have as much
config as possible inside them. if it's at all feasible. though you
get the issue with popup applets doing their thing.

/me would definitely want a libplasma2 meeting, even though i'm not
(yet?) involved in the libplasma2 happenings.

-- 
Shaun Reich,
KDE Software Developer (kde.org)
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: KConfigXT default value code evaluation

2012-02-05 Thread Simone Gaiarin 
I've solved in this way: I set as default value latitude=0 and
longitude=0 in main.xml , then in init I call configChanged and after
it I check if lat and lon are both zero. In this case I get their
default values in init and write these values to the rc file. In this
way when the dialog in opened the correct values are shown.

2012/2/5 Simone Gaiarin :
> So there is no way to compute the default value in the init function
> and set it to the configuration dialog? Or I have to write the default
> value to the rc file so that when the configuration dialog is showed
> it reads this value?
>
> 2012/2/5 Aaron J. Seigo :
>> On Sunday, February 5, 2012 00:44:47 Simone Gaiarin wrote:
>>> I'm writing a python plasmoid and I want to initialize a field with a
>>> default value from this function KSystemTimeZones::local().latitude()
>>> but it doesn't work.
>>> If I put a number in the default value it is taken correctly. I've
>>> also tried to add another include tag with KTimeZone.  I've tried even
>>> with the point insted of ::  KSystemTimeZones.local().latitude() . But
>>> it still doesn't work. Any idea?
>>
>> code is not supported in configxt loaded by plasmoids, as that requires
>> generation, compilation and execution of C++ code. obviously, this is a "no-
>> go". it may be possible to run it in the runtime of the plasmoid (meaning it
>> would become python in a python plasmoid, JS in a JS plasmoid, etc) but that
>> would require a fair amount more work on the configxt support for plasmoids.
>>
>> --
>> Aaron J. Seigo
>> ___
>> Plasma-devel mailing list
>> Plasma-devel@kde.org
>> https://mail.kde.org/mailman/listinfo/plasma-devel
>>
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

QML global plasmoid callback problem

2012-02-05 Thread uomonero 
Hi,
I'm new to plasmoid development. I'm trying to learn how to write a
QML plasmoid, but I encountered a little difficulty with the use of
global plasmoid object.

This is my simple test code:

import QtQuick 1.0
import org.kde.plasma.core 0.1 as PlasmaCore
import org.kde.plasma.components 0.1 as PlasmaComponents

PlasmaComponents.Label{
id: labelTest
text:"Test"

Component.onCompleted:{
plasmoid.addEventListener("sizeChanged", sizeChanged);
}
function sizeChanged(){
print("sizeChanged listener");
}
}

Running with plasmoidviewer, when I resize the plasmoid nothing is printed.
What's wrong?



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

Re: KConfigXT default value code evaluation

2012-02-05 Thread Simone Gaiarin 
So there is no way to compute the default value in the init function
and set it to the configuration dialog? Or I have to write the default
value to the rc file so that when the configuration dialog is showed
it reads this value?

2012/2/5 Aaron J. Seigo :
> On Sunday, February 5, 2012 00:44:47 Simone Gaiarin wrote:
>> I'm writing a python plasmoid and I want to initialize a field with a
>> default value from this function KSystemTimeZones::local().latitude()
>> but it doesn't work.
>> If I put a number in the default value it is taken correctly. I've
>> also tried to add another include tag with KTimeZone.  I've tried even
>> with the point insted of ::  KSystemTimeZones.local().latitude() . But
>> it still doesn't work. Any idea?
>
> code is not supported in configxt loaded by plasmoids, as that requires
> generation, compilation and execution of C++ code. obviously, this is a "no-
> go". it may be possible to run it in the runtime of the plasmoid (meaning it
> would become python in a python plasmoid, JS in a JS plasmoid, etc) but that
> would require a fair amount more work on the configxt support for plasmoids.
>
> --
> Aaron J. Seigo
> ___
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Python plasmoid and configChanged()

2012-02-05 Thread Simone Gaiarin 
I call configChanged() once in the init function and then I connect it
to the configChanged() signal.

Here you can find the code:

https://github.com/simgunz/redshift-plasmoid/blob/master/contents/code/main.py


2012/2/5 Aaron J. Seigo :
> On Sunday, February 5, 2012 11:44:02 Simone Gaiarin wrote:
>> Hi,
>> I wrote a python plasmoid that needs to restart a program (redshift)
>> everytime that the configuration is changed by the user (the plasmoid
>> configChanged() function reacts to the signal). When the program is
>> restarted the user is aware of it, because the screen color become
>> white and than red again. But this is not a problem because the
>> configuration is likely changed only few times.
>> Although I've noticed that the signal configChanged() is emitted every
>> time every part of the desktop is changed. So everytime I add a
>> widget, lock/unlock widgets and so on, my plasmoid restarts the
>> program. Is this the normal behaviour? Shouldn't the signal be emitted
>> only when the configuration of my plasmoid is changed?
>
> yes, and that's how it should be working. do you call configChanged() from
> anywhere else in the plasmoid code?
>
> i tried just now with a C++ plasmoid, and it is not happening.
>
> tried again with a JS plasmoid, also not happening there either.
>
> so it seems this is something in your plasmoid or in the python bindings?
>
> --
> Aaron J. Seigo
> ___
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: dictionary widget QML

2012-02-05 Thread Marco Martin 
On Sun, Feb 5, 2012 at 2:46 PM, Aaron J. Seigo  wrote:
>> if you want to make this choseable by the kcm it would have to become
>> a (partly) c++ plasmoid
>
> assuming that it is unnecessary, even unwanted (different instances of the
> plasmoid -> different dicts?), this could in theory be done straight from the
> plasmoid. but this is where (again) the KConfigXt+Qt Designer pair let us 
> down;

uh, and forgotted to add: in this case yes, doing it directly from the
plamoid would be a sensible enough workflow:
* click the dict icon (that right now doesn't do anything)
* in the results area it shows the list of available dicts
* select one
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: dictionary widget QML

2012-02-05 Thread Marco Martin 
On Sun, Feb 5, 2012 at 2:46 PM, Aaron J. Seigo  wrote:
>
> can we do better in libplasma2? i hope so :)
>

apart from the fact that it requires either config forms using plasma
widgets or complete and functional desktop qtcomponents, i think the
solution is quite easy ;)
(and makes easy also writing platform specific configuration dialogs)

speaking of liplasma2 I wanted to do something like a week long
meeting (looking at our crazy schedules would means probaly not before
may or something like that) specifically and *only* about it.
does it look desiderable/feasible?

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

Re: dictionary widget QML

2012-02-05 Thread Aaron J. Seigo 
On Sunday, February 5, 2012 14:29:13 Marco Martin wrote:
> On Sun, Feb 5, 2012 at 2:55 AM, Shaun Reich  wrote:
> > is the dict widget supposed to have a kcm?
> > 
> > i could have sworn it had one, and on my 4.8 system it has one but the
> > populated list view is...unpopulated.
> > 
> > so should the qml one have a populated listview that enables you to
> > select which dicts you can have?
> 
> as far i know dict.org provides more than one dictionary. the
> dataengine supports query to different doctionaries than the default
> one, a gui has never been implemented for it.
> 
> if you want to make this choseable by the kcm it would have to become
> a (partly) c++ plasmoid

assuming that it is unnecessary, even unwanted (different instances of the 
plasmoid -> different dicts?), this could in theory be done straight from the 
plasmoid. but this is where (again) the KConfigXt+Qt Designer pair let us down; 
they just aren't flexible enough in their current state.

can we do better in libplasma2? i hope so :)

-- 
Aaron J. Seigo

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: Python plasmoid and configChanged()

2012-02-05 Thread Aaron J. Seigo 
On Sunday, February 5, 2012 11:44:02 Simone Gaiarin wrote:
> Hi,
> I wrote a python plasmoid that needs to restart a program (redshift)
> everytime that the configuration is changed by the user (the plasmoid
> configChanged() function reacts to the signal). When the program is
> restarted the user is aware of it, because the screen color become
> white and than red again. But this is not a problem because the
> configuration is likely changed only few times.
> Although I've noticed that the signal configChanged() is emitted every
> time every part of the desktop is changed. So everytime I add a
> widget, lock/unlock widgets and so on, my plasmoid restarts the
> program. Is this the normal behaviour? Shouldn't the signal be emitted
> only when the configuration of my plasmoid is changed?

yes, and that's how it should be working. do you call configChanged() from 
anywhere else in the plasmoid code?

i tried just now with a C++ plasmoid, and it is not happening.

tried again with a JS plasmoid, also not happening there either.

so it seems this is something in your plasmoid or in the python bindings?

-- 
Aaron J. Seigo

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: dictionary widget QML

2012-02-05 Thread Marco Martin 
On Sun, Feb 5, 2012 at 2:55 AM, Shaun Reich  wrote:
> is the dict widget supposed to have a kcm?
>
> i could have sworn it had one, and on my 4.8 system it has one but the
> populated list view is...unpopulated.
>
> so should the qml one have a populated listview that enables you to
> select which dicts you can have?
>

as far i know dict.org provides more than one dictionary. the
dataengine supports query to different doctionaries than the default
one, a gui has never been implemented for it.

if you want to make this choseable by the kcm it would have to become
a (partly) c++ plasmoid
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: dictionary widget QML

2012-02-05 Thread Aaron J. Seigo 
On Saturday, February 4, 2012 20:55:24 Shaun Reich wrote:
> so should the qml one have a populated listview that enables you to
> select which dicts you can have?

if there is any value to that, sure. i suppose the primary purpose would be to 
allow one to define different dict servers?

-- 
Aaron J. Seigo

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: KConfigXT default value code evaluation

2012-02-05 Thread Aaron J. Seigo 
On Sunday, February 5, 2012 00:44:47 Simone Gaiarin wrote:
> I'm writing a python plasmoid and I want to initialize a field with a
> default value from this function KSystemTimeZones::local().latitude()
> but it doesn't work.
> If I put a number in the default value it is taken correctly. I've
> also tried to add another include tag with KTimeZone.  I've tried even
> with the point insted of ::  KSystemTimeZones.local().latitude() . But
> it still doesn't work. Any idea?

code is not supported in configxt loaded by plasmoids, as that requires 
generation, compilation and execution of C++ code. obviously, this is a "no-
go". it may be possible to run it in the runtime of the plasmoid (meaning it 
would become python in a python plasmoid, JS in a JS plasmoid, etc) but that 
would require a fair amount more work on the configxt support for plasmoids.

-- 
Aaron J. Seigo

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

Python plasmoid and configChanged()

2012-02-05 Thread Simone Gaiarin 
Hi,
I wrote a python plasmoid that needs to restart a program (redshift)
everytime that the configuration is changed by the user (the plasmoid
configChanged() function reacts to the signal). When the program is
restarted the user is aware of it, because the screen color become
white and than red again. But this is not a problem because the
configuration is likely changed only few times.
Although I've noticed that the signal configChanged() is emitted every
time every part of the desktop is changed. So everytime I add a
widget, lock/unlock widgets and so on, my plasmoid restarts the
program. Is this the normal behaviour? Shouldn't the signal be emitted
only when the configuration of my plasmoid is changed?
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel