Re: Possible issue in breeze 5.5 kstyle

[Sandro Andrade]

On Fri, Dec 11, 2015 at 5:18 AM, Kai Uwe Broulik  wrote:
> Hi,
>
> Perhaps that's the reason for QtCreator's welcome page being broken here when 
> running with Breeze.

Yes, removing /usr/lib/qt/plugins/styles/breeze.so fixes the problem
for QtCreator.

Sandro

>
>
> ___
> 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

Possible issue in breeze 5.5 kstyle

[Sandro Andrade]

Hi there,

After upgrading plasma to 5.5 I started to notice some weird behaviour
in using QQuickView to load a QML document:

Ex:

m_quickView->setSource(QUrl("qrc:/main.qml"));
...
setupGUI();
...
if (!m_initialGroup.exists())
runWizard();

The issue is that no QML content is shown if using breeze 5.5. It
works fine with breeze 5.4.3.

After doing some git bisect I've found that commit
6d852f30a1f2c1988359d4e0cdb21e2f1714a6bd in breeze repository added a
QTimer in kstyle/breezepalettehelper.cpp (line 65) to postpone the
update of widget's palette. The consequence is that the loading of QML
scene is probably running *before* the delayed palette update, which
causes the issue.

If something delays the ending of the aforementioned code (for
instance, it executes a wizard in the first run of the application,
when no app's rc setting file exists) then the QTimer has the chance
to has already been finished when showing the QQuickView and things
work properly. Commenting out the line 65 in
kstyle/breezepalettehelper.cpp fixes the issue but obviously should
make something else broken. Such commit fixed BUG 344425.

Any suggestions?

Thanks in advance,
--
Sandro
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: kdeobservatory seems to be missing a qwt min version check

[Sandro Andrade]

Hi there,

That's actually intended to be moved to unmaintained, sorry for
haven't done it yet, I'm in the last months of my thesis :( - or maybe
:)
Not sure if I can do that at this time in release schedule. I can fix
it to use Qwt 6.1 or fully move it to maintained.

What do you guys prefer ?
--
Sandro


On Mon, Jun 3, 2013 at 5:22 PM, Ben Cooksley bcooks...@kde.org wrote:
 On Tue, Jun 4, 2013 at 8:09 AM, Albert Astals Cid aa...@kde.org wrote:
 Hi guys, can anyone please have a look at
 kdeplasma-addons/applets/kdeobservatory and make sure it requires the qwt min
 version it needs?

 The build is currently failing at build.kde.org (probably a too old qwt
 installed) instead of just skipping the applet from being built.

 I suspect it is actually a case of a too new Qwt being installed.
 We recently upgraded from Qwt 6.0 to 6.1, which was necessary to allow
 the smokeqt bindings to compile successfully.


 http://build.kde.org/view/All/job/kdeplasma-addons_master/212/console

 Cheers,
   Albert

 Regards,
 Ben


 P.S: I'm *not* subscribed to plasma-devel so CC me if you want to keep me in
 the loop
 ___
 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

Moving KDE Observatory to unmaintained

[Sandro Andrade]

Hi there,

KDE Observatory is a simple widget and data engine I've developed in the last
days of KDE svn usage. It gathered projects data from svn logs and presented
info about most active KDE projects and contributors, but it's pretty
nonfunctional since
I haven't had enough time to migrate it to git infrastructure.

So, unless someone is willing to take over it I'd like to move it to
unmaintained
until I'm able to be hacking KDE again (next year, hopefully).

Any objections ?

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

Re: Plasmate: some files miss licenses

[Sandro Andrade]

Hi Sebas,

I'm ok ...
Thanks for reporting this,

Cheers,
Sandro

On Mon, Mar 14, 2011 at 10:25 AM, Sebastian Kügler se...@kde.org wrote:
 Hi all,

 [If you're in the CC: of this email explicitely, please reply to it in any
 case.]

 The short version:

        Are you OK with changing the license in the unlicensed files you have
        worked on in Plasmate to GPLV2+ and KDE e.V. approved licenses?

 Longer version:

 Over the weekend, I've had a closer look at Plasmate, to fix some bugs and
 improve it here and there. It struck me that the licensing is currently
 incomplete -- some files are missing a licensing header. If we want to release
 Plasmate at some point, that's something we'll need to work out.

 I started on this by streamlining the copyright headers (some used a short
 form to refer to the GPLv2+, I've replaced those with the advised text at
 http://techbase.kde.org/Policies/Licensing_Policy#GPL_Header

 There are still some files unlicensed at this point, though. I've asked Paul
 Adams to help me a bit to sort out the people who have written or contributed
 to these files, and thanks to grep, uniq, sort and svn log, I've compiled a
 list of people per file that are the copyright holders according to svn log.

 The list is:

  *snip* --

 packagemodel.h
    aseigo
    asouza
    casella
    sandroandrade
    shantanu
    yuenlim
 packagemodel.cpp
    aseigo
    asouza
    casella
    mart
    sandroandrade
    shantanu
    yuenlim
 sidebaritem.cpp
    aseigo
    casella
 sidebartablewidget.cpp
    casella
    mlaurent
 sidebartablewidget.h
    casella
    mlaurent
 editors/editpage.h
    asouza
    mlaurent
    shantanu
    yuenlim
 editors/editpage.cpp
    aseigo
    asouza
    mlaurent
    sandroandrade
    shantanu
    yuenlim
 savesystem/tabledelegate.cpp
    casella
 savesystem/tabledelegate.h
    casella
 savesystem/tablewidget.cpp
    casella
 savesystem/tablewidget.h
    casella
 savesystem/timeline.cpp
    aseigo
    casella
    coles
    ilic
    yuenlim
 savesystem/timeline.h
    aseigo
    casella
    yuenlim
 savesystem/timelineitem.cpp
    aseigo
    casella
 savesystem/timelineitem.h
    aseigo
    casella

  *snip* --

 (I've *NOT* looked at the commits themselves, because I'm not in the position
 to judge if a patch is too trivial or should include the author in the file's
 copyright. A las, if you think your contribution to some file is trivial, let
 me know and I'll not include your name in the copyright header. Otherwise,
 please let me know if you're OK with changing the files you have been working
 on to the GPLv2 or later, including the clausule

 In order to protect your copyright in the future, please also consider signing
 the KDE e.V.'s fiduciary licensing agreement, which is a safe construct to
 keep copyright of KDE code intact and workable in case you are not available
 for eventual licensing changes, should that ever become necessary. (Different
 topic though.)

 Please (ideally) send me an I am OK with the licensing changes you propose.,
 or in case you're not OK with it, let me know that as well and I'll see what
 we can do about it. I kind of expect this to be an administrative thing, but
 needs to happen nevertheless.

 Thanks for your attention on this boring topic. :-)

 Cheers,
 --
 sebas

 http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9

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

Re: Move KDEObservatory applet and dataengine to kde-apps

[Sandro Andrade]

On Tue, Jan 4, 2011 at 7:11 AM, Anne-Marie Mahfouf an...@kde.org wrote:
 On Tuesday 04 January 2011 03:32:05 Sandro Andrade wrote:
 On Mon, Jan 3, 2011 at 10:35 PM, Aaron J. Seigo ase...@kde.org wrote:
  On Monday, January 3, 2011, Sandro Andrade wrote:
  Hi there,
 
  Due to last changes in KDE repositories (git migration) and some
  dependencies on services provided by my personal website,
  I would like to move (as suggested by Anne-Marie) KDE Observatory
  applet and dataengine from kdeplasma-addons to kde-apps.
 
  Any particular considerations about that ?
 
  what is kde-apps? kde extragear? or are you suggesting moving it to kde-
  apps.org and out of KDE's svn/git altogether?

 The web service used by KDE Observatory is experiencing a very high
 load of SQL queries
 due to high commit traffic information. So, I need to make some
 changes in order to have it
 functional again and take the chance and provide git integration.
 Since it's usually getting no
 information from the service, Anna's suggested moving it somewhere
 else. Extragear is fine
 for me, or any other place just to have these things solved.

 Thanks,
 Sandro
 You totally misunderstood what I wrote: the KDE Observatory data engine uses
 Sandro own website and it seems down.
 It's not about moving the code, it's about the webservice.
 The applet displays nothing for me and in the konsole output I see
 plasma-desktop(22814) KdeObservatory::engineError: Source: allProjectsInfo
 Error: Unknown host sandroandrade.org
 I suggested to see if Sandro could use a KDE server or kde-files.org instead 
 of
 his own webspace (which is generally not our policy).


Sorry, it's clear now :) the website should be working fine, I'm
checking this now.

 Probably my mail was not clear enough that it was about web services hosting
 and not about the code itself which is fine in kdeplasma-addons.

 If you are hosting the service on your own space because KDE does not provide
 the server you need then we should address that. Unfortunately I'll be away
 for a couple of weeks (maybe more) without proper internet at my parents' home
 but when I am back I could start to initiate a work group on this and GHNS.

I'm using a mysql database to store consolidated data about KDE commits since
accessing them directly would imply in long access times. In addition,
a java servlet
provides the services for querying data about specific KDE projects.
Certainly wouldn't
be worthy to create this infrastructure in KDE server only for this
(not so important) applet.

I'll think in some other solution.

Thanks,
Sandro


 There's no urgency though.

 Best regards,

 Anne-Marie
 ___
 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

Move KDEObservatory applet and dataengine to kde-apps

[Sandro Andrade]

Hi there,

Due to last changes in KDE repositories (git migration) and some
dependencies on services provided by my personal website,
I would like to move (as suggested by Anne-Marie) KDE Observatory
applet and dataengine from kdeplasma-addons to kde-apps.

Any particular considerations about that ?

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

Re: Move KDEObservatory applet and dataengine to kde-apps

[Sandro Andrade]

On Mon, Jan 3, 2011 at 10:35 PM, Aaron J. Seigo ase...@kde.org wrote:
 On Monday, January 3, 2011, Sandro Andrade wrote:
 Hi there,

 Due to last changes in KDE repositories (git migration) and some
 dependencies on services provided by my personal website,
 I would like to move (as suggested by Anne-Marie) KDE Observatory
 applet and dataengine from kdeplasma-addons to kde-apps.

 Any particular considerations about that ?

 what is kde-apps? kde extragear? or are you suggesting moving it to kde-
 apps.org and out of KDE's svn/git altogether?

The web service used by KDE Observatory is experiencing a very high
load of SQL queries
due to high commit traffic information. So, I need to make some
changes in order to have it
functional again and take the chance and provide git integration.
Since it's usually getting no
information from the service, Anna's suggested moving it somewhere
else. Extragear is fine
for me, or any other place just to have these things solved.

Thanks,
Sandro


 --
 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

 ___
 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

KDE Observatory moved to kdeplasma-addons

[Sandro Andrade]

KDE Observatory applet and dataengine moved to
kdeplasma-addons/applets and kdeplasma-addons/dataengines,
respectively.

All suggestions from i18n team were done. I got no suggestions from
plasma team (I know you guys are busy with higher priorities tasks :)
but, because of trunk freeze, Aaron gave me a 'ship it'.

So, if there is someone idle, a quick look at engine source-code would
be nice, even though there are no known crashes/bugs :)

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

Re: KDE Observatory moved to kdereview

[Sandro Andrade]

Hey dude,

Remember the milk :)

Just give it a brief overview, looking for some weird stuff may be there ...

Thanks,
Sandro

On Wed, May 5, 2010 at 6:06 PM, Sandro Andrade sandroandr...@kde.org wrote:
 On Wed, May 5, 2010 at 5:01 PM, Artur Souza (MoRpHeUz)
 morph...@openbossa.org wrote:
 On Wednesday 05 May 2010, 16:30 Albert Astals Cid wrote:
 Agreed, the fact that you forgot about the freeze is not an excuse at all
 to bypass the kdereview stage.

 Just to clear the subject a little bit: I think the didn't forget about the
 freeze and is not using it as an excuse if I understood correctly. He is just
 *asking* how to proceed. :)

 Yes, it's clear for me now the reasons for announce. I'm doing this
 now in kde-core-devel
 and fixing the i18n issues.

 Thanks,
 Sandro


 Cheers,

 --
 Artur Duque de Souza
 openBossa
 INdT - Instituto Nokia de Tecnologia
 --
 Blog: http://blog.morpheuz.cc
 PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net
 --

 ___
 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

KDE Observatory moved to kdereview

[Sandro Andrade]

Hi there,

KDE Observatory applet and data engine were moved to kdereview.

What's new ?

- New data engine for acquiring data from commits and krazy reports.
- Performance improvements by getting consolidated data from a servlet
service instead of scan kde-commits archives.
- Filtering by any date range.

Any comments and suggestions are welcome !

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

Re: KDE Observatory moved to kdereview

[Sandro Andrade]

On Wed, May 5, 2010 at 12:55 PM, Aaron J. Seigo ase...@kde.org wrote:
 On May 5, 2010, Sandro Andrade wrote:
 Hi there,

 KDE Observatory applet and data engine were moved to kdereview.

 cool, i'll have to check it out...

Ok !


 Any comments and suggestions are welcome !

 you need to announce this on kde-core-devel as well. iwhat is your target
 destination? kdeplasma-addons? kdesdk? extragear?

KDE Observatory (first version, without a data engine) is already in
kdeplasma-addons,
so I'm considering keep things there.

What's the reason for announcing in kde-core-devel ? I didn't do that
for KDE Observatory in KDE SC 4.4.

Thanks,
Sandro


 --
 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

 ___
 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: KDE Observatory moved to kdereview

[Sandro Andrade]

On Wed, May 5, 2010 at 1:53 PM, Marco Martin notm...@gmail.com wrote:
 On Wednesday 05 May 2010, Sandro Andrade wrote:
 On Wed, May 5, 2010 at 12:55 PM, Aaron J. Seigo ase...@kde.org wrote:
  On May 5, 2010, Sandro Andrade wrote:
  Hi there,
 
  KDE Observatory applet and data engine were moved to kdereview.
 
  cool, i'll have to check it out...

 Ok !

  Any comments and suggestions are welcome !
 
  you need to announce this on kde-core-devel as well. iwhat is your target
  destination? kdeplasma-addons? kdesdk? extragear?

 KDE Observatory (first version, without a data engine) is already in
 kdeplasma-addons,
 so I'm considering keep things there.

 What's the reason for announcing in kde-core-devel ? I didn't do that
 for KDE Observatory in KDE SC 4.4.

 so translators can notice and move the translatio files where needed

Great, as soft message freeze occurs only at 19th May I suppose I should
do the review corrections first and then announce it in its final
location (kdeplasma-addons)
instead of in kdereview, right ?

Thanks,
Sandro


 --
 Marco Martin
 ___
 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: KDE Observatory moved to kdereview

[Sandro Andrade]

On Wed, May 5, 2010 at 5:01 PM, Artur Souza (MoRpHeUz)
morph...@openbossa.org wrote:
 On Wednesday 05 May 2010, 16:30 Albert Astals Cid wrote:
 Agreed, the fact that you forgot about the freeze is not an excuse at all
 to bypass the kdereview stage.

 Just to clear the subject a little bit: I think the didn't forget about the
 freeze and is not using it as an excuse if I understood correctly. He is just
 *asking* how to proceed. :)

Yes, it's clear for me now the reasons for announce. I'm doing this
now in kde-core-devel
and fixing the i18n issues.

Thanks,
Sandro


 Cheers,

 --
 Artur Duque de Souza
 openBossa
 INdT - Instituto Nokia de Tecnologia
 --
 Blog: http://blog.morpheuz.cc
 PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net
 --

 ___
 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

Plasmate hacking during Akademy-BR ?

[Sandro Andrade]

Hi folks,

As you may already know, we are going to have Akademy-BR in next
weekend and I was
wondering about taking some hours and two or three developers to work
on Plasmate.

So, you guys wanting to point out some required feature/improvement would be
great. Is the plasmate webpage up to date ? Could someone rank the to-do's or
select one or two most wanted task ? We'll have two or three artwork
guys also looking for
hacking activities.

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

Re: TokamakIV update

[Sandro Andrade]

Hi all,

Has the arrangement for working groups in T4 already begun ? Or is this
going to be defined in the beginning of sprint ? I'm trying the make a plan
for my contribution during T4 ...

See you,
Sandro

On Wed, Feb 3, 2010 at 11:06 PM, Lukas Appelhans l.appelh...@gmx.de wrote:

 Am Mittwoch 03 Februar 2010 23:50:55 schrieb Ivan Čukić:
  On Wednesday, 3. February 2010. 23.22.20 Lukas Appelhans wrote:
   Hey!
  
   Just to give an update from my side... I will arrive at 18:24 on Friday
   and will depart at 17:33 on sunday... anyone got the same times (and
   maybe the same train, it's some ICE)?
 
  You should fill that info to T4 page on techbase so that we all can
  organize in groups.
 Done, thanks for hinting...

 Lukas
 
  Cheerio
 
  --
  There are no such things as applied sciences, only applications of
 science.
-- Louis Pasteur
  ___
  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

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

Re: Need a couple of volunteers (was: Re: TokamakIV update)

[Sandro Andrade]

Hi Marco and Alexis,

I could help in such task although I'm not used to such mobile
devices. I'll receive an N900 in next weeks, so that would be a good
chance to begin some work in that direction.

See you,
Sandro Andrade

On Wed, Jan 13, 2010 at 10:45 AM, Alexis Ménard men...@kde.org wrote:
 On Wed, Jan 13, 2010 at 11:15 AM, Marco Martin notm...@gmail.com wrote:
 On Tuesday 12 January 2010, Marco Martin wrote:
 Hi all,
 Since a couple of days i had the occasion playing aroung with a neat mobile
 device by Intel. I think it's a good development platform to get
 plasma-mobile started since is basicaly a pc (tough only slightly bigger
 than an n810) so getting things to run on it is really easy.
 Now since i had green light to ask this, (i know that's a rethorical
 question since i know everybody here loves this stuff ;p) if i can get at
 least two people that will be interested working on them during Tokamak i
 think i can make them lending us two more devices, so there will be enough
 to experiment for some people.
 then of course they don't have to do that all the time, we just have to
 make sure they'll be put in good use.

 who raises hand? :)

 Would really need a couple more of yes, i'm interested :p
 also, it would make working with those things significantly easier if someody
 has laying around things like an usb ethernet adaptor (getting wifi to work 
 on
 them is too random:) and usb hubs, preferably powered and can share them just
 during the meeting ;)


 For me i do prefer working on the N900, the config is much more
 reliable and easy.
 I bring extra devices for other people.

 Cheers,
 Marco Martin
 ___
 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

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

Re: Restoring plasma activity and Giving credits

[Sandro Andrade]

On Wed, Dec 23, 2009 at 9:33 AM, Shantanu Tushar Jha
jhahon...@gmail.com wrote:


 On Wed, Dec 23, 2009 at 11:15 AM, Chani chan...@gmail.com wrote:

 On December 22, 2009 17:54:06 Sandro Andrade wrote:
  Ok, creating a new mouse action solved the problem. Is this expected
  to not be enabled by default ?

 no. I've heard of a few people not getting any default mouse actions...
 but
 they work for *me*. I guess I'll have to investigate after my vacation :/

 but you're supposed to always have a cashew...
 and I thought the SAL was a netbook-only thing. notmart, are people
 *supposed*
 to be able to choose it in the activity settings?

 I hope they are able to choose, because its very nice (and cool) to use even
 on the desktop. IMO it shouldn't be made a netbook-only thing.

Indeed :)

Any hint about how to give credits in a plasmoid ?

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

Restoring plasma activity and Giving credits

[Sandro Andrade]

Hi all,

When using Search and Launch Containment is there a way to restore
to Desktop Activity in Desktop Settings other than Alt+D, Alt+S ?
Right-clicking in desktop doesn't show anything. In addition, the
popup menu item's label Desktop Activity Setttings doesn't match the
caption of opened windows (Desktop Settings). I think some stuff other
than activitied can be set up there.

A second question: I would like to give credits for a contribution in
KDE Observatory, where should I include this ? Is there any credits
section in .desktop file or can I insert more than one author ?

Thanks in advance,
Sandro
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Restoring plasma activity and Giving credits

[Sandro Andrade]

Ok, creating a new mouse action solved the problem. Is this expected
to not be enabled by default ?

Sandro

On Wed, Dec 23, 2009 at 1:32 AM, Sandro Andrade sandroandr...@kde.org wrote:
 Hi all,

 When using Search and Launch Containment is there a way to restore
 to Desktop Activity in Desktop Settings other than Alt+D, Alt+S ?
 Right-clicking in desktop doesn't show anything. In addition, the
 popup menu item's label Desktop Activity Setttings doesn't match the
 caption of opened windows (Desktop Settings). I think some stuff other
 than activitied can be set up there.

 A second question: I would like to give credits for a contribution in
 KDE Observatory, where should I include this ? Is there any credits
 section in .desktop file or can I insert more than one author ?

 Thanks in advance,
 Sandro

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

KDE Observatory: new UI strings ?

[Sandro Andrade]

Hi all,

Since I'm not actually used to KDE release cycle I think it's better
to ask here :)

I'm planning to add simple messages in KDE Observatory to inform about
commit and krazy information gathering instead of having only the busy
animation running.

That would imply adding new translatable strings. Is this allowed at this time ?
This isn't a must-have feature, it would be just to give user better
information while applet is busy,
so it can be posponed to next release.

Thanks,
-- 
Sandro Santos Andrade

http://sandroandrade.wordpress.com
http://liveblue.wordpress.com
Distributed Systems Laboratory (LaSiD)
Computer Science Department (DCC)
Federal University of Bahia - Brazil
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: KDE Observatory: new UI strings ?

[Sandro Andrade]

Ok, no need to disturb their already hard work :)

See you,
Sandro

On Sun, Nov 29, 2009 at 4:24 PM, Artur Souza (MoRpHeUz)
morph...@openbossa.org wrote:
 Hey Sandro!

 On Sunday 29 November 2009, 13:09 Sandro Andrade wrote:
 That would imply adding new translatable strings. Is this allowed at this
  time ? This isn't a must-have feature, it would be just to give user
  better information while applet is busy,
 so it can be posponed to next release.

 Yep, I think we are already in string freeze and people are not allowed to
 change/create strings anymore, so the translators can do their work. If you
 *really* need it, you can talk to them and ask for an exception but if it's 
 not
 really necessary, let it for the next release...

 Cheers!

 --
 Artur Duque de Souza
 openBossa
 INdT - Instituto Nokia de Tecnologia
 --
 Blog: http://blog.morpheuz.cc
 PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net
 --




-- 
Sandro Santos Andrade

http://sandroandrade.wordpress.com
http://liveblue.wordpress.com
Distributed Systems Laboratory (LaSiD)
Computer Science Department (DCC)
Federal University of Bahia - Brazil
KDE developer - KDevelop / Gluon / Plasma
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Broken build kdeplasma-addons/applets/kdeobservatory/

[Sandro Andrade]

Investigating !

Sandro

On Wed, Nov 25, 2009 at 4:27 PM, Burkhard Lück lu...@hube-lueck.de wrote:
 Hi,

 the applet does not build here, CMakeCaxhe says:
 build/kdeplasma-
 addons/CMakeCache.txt:551:Qwt5_INCLUDE_DIR:PATH=/usr/include/qwt-qt4

 but include path seems to be hardcoded in this file:

 kdeobservatory/src/commithistoryview.cpp:27:#include qwt/qwt_plot.h

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




-- 
Sandro Santos Andrade

http://sandroandrade.wordpress.com
http://liveblue.wordpress.com
Distributed Systems Laboratory (LaSiD)
Computer Science Department (DCC)
Federal University of Bahia - Brazil
KDE developer - KDevelop project
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Review Request: KDE Observatory (new plasmoid)

[Sandro Andrade]

Hi Aaron,

All suggestions have been done ! See comments below.

Thanks,
Sandro

 * i see that it uses Qwt in one class. this is likely to diminish both the
 user base of it as well as it's plasma-ness. does Plasma::SignalPlotter give
 you something similar? if not, then a check in the CMakeLists.txt file for Qwt
 is required

I've tried the SignalPlotter but apparently its time-dependent
approach doesn't properly fit the needs in commit history. I need to
include data which are sparse in time and that would be harder to
achieve. So, I keep using Qwt, cmake module was included, and checked
in CMakeLists.txt.

 * the collectors really look like something that would be better as a
 DataEngine. putting data and visualization into one plugin is generally
 frowned upon in plasma. things like the periodic updates of the collectors are
 taken care of for you if you use a DataEngine, other widgets can more easily
 use the results, the data can be shared between multiple instances of the
 kdeobservatory widget and the widget would be more ready for remote widget
 use. perhaps not necessary for 4.4, but should definitely be considered for
 4.5.

Postponed to 4.5.

 * m_progressProxy should be a Plasma::Meter (i just made some relevant methods
 slots in Plasma::Meter to make that even easier)

Done !

 * collectFinished is probably getting called more often than needed as its
 connected to multiple collectors; that means views and what not will get
 updated for collectors that don't have new data?

Views are updated only when all collectors finish.

 * calling collection[something] as in if (pair.second 
 m_viewProviders[view]) will create an entry in the collection if it doesn't
 exist which is probably an unwanted (or at least unneeded) side effect; in
 these cases you probably want m_viewProviders.value(view)

Done !

 * passing in a rect and the code in IViewProvider::createView looks fishy and
 indeed doesn't quite work; when KdeObservator::m_viewContainer changes
 geometry, the views won't change their geometry. i'd suggest either using a
 QGraphicsLayout or else putting an event filter on the view container and
 adjusting the geometry of the views when the view container gets a resize or
 related events.

Done ! Applet was converted to a PopupApplet and all geometry
adjustments are done when resizing events occur.

 * calls like m_right-nativeWidget()-setIcon are generally unecessary. use
 m_right-setIcon() i'd look through all the nativeWidget() calls and see which
 can be removed.

Done !

 * on first update, it sat and spun for the better part of a minute writing to
 disk. subsequent starts up are good. i wonder if this is because each commit
 is added one at a time to the sqllite db instead of several at once? this is a
 show stopper for first use in any case. it also happens when adding more days
 to the context :/

Solved by initiating a transaction before adding commits in database
and committing when everything has finished. There are no delays after
this
change.

 * worse, it blocks the app while doing so. the db should either be updated
 incrementally with regular returns to the mainloop to prevent blocking the
 whole plasma application (e.g. plasma-desktop) or it should be done in a
 thread (probably preferred in this case)

Also solved by previous change. No blocking anymore.

 * the icon button in the Configure KDE Observatory page seems to have some
 layout issues; here it overlaps the divider line at the bottom?

Fixed !

 * sync'ing every minute might be a bit much for the default. 5 or 10 minutes
 should be plenty for a default?

Done !

 * speaking of defaults, is showing just one day of operations really enough to
 give a decent and moral boosting overview? would the last week's worth of data
 be better? a lot of projects see sporadic but regular commits and one day
 may not be a whole lot of progress. plasma is active daily as are some of the
 other big projects like kdepim ... but not all are so lucky. this does make
 the db building problem worse, of course.

Default value adjusted to 7 days. Although app blocking doesn't occur
anymore, some time (around 2.5 min) is required for the initial load
of seven-day commits. After that, updates occur very fast.

 * why is enable transition effects an option?

I've kept this as an option because disabling effects makes view
transition faster.

 * why are some view options in the global config options and others in the
 Views page?

All view configuration options were grouped in Views configuration page.

 * from a user's perspective, why is there a global config options? would
 another name be more useful?

Renamed to General.

 * the automatic transitions are nice, but when trying to page through them
 with the left/right buttons it really gets in the way. perhaps a play/pause
 button could be added to the interface and automatically set it to pause
 when one of the arrow buttons are manually pressed? perhaps the transition
 could also pause 

Re: Review Request: KDE Observatory (new plasmoid)

[Sandro Andrade]

 I've tried the SignalPlotter but apparently its time-dependent
 approach doesn't properly fit the needs in commit history. I need to
 include data which are sparse in time and that would be harder to
 achieve. So, I keep using Qwt, cmake module was included, and checked
 in CMakeLists.txt.

 i see; unfortunate since it really won't blend in with the rest of plasma at
 all. perhaps we need a proper graph widget in libplasma at some point. oh well
 ... not the end of the world in this case.

Ok, I can take this task to myself when KDE Observatory is in better shape.


  * why is enable transition effects an option?

 I've kept this as an option because disabling effects makes view
 transition faster.

 i really don't see the point of this at all. what benefit is there in making
 the view transitions faster? if they are too slow, speed them up, don't offer
 an option.

Removed :)

 iirc, it wasn't on configuration change, it was when new data arrived from the
 online sources

Yes, fixed ! Transitions are re-started only when views are created or removed.

 you should move this into kdeplasma-addons

Moving ...

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

Re: Review Request: KDE Observatory (new plasmoid)

[Sandro Andrade]

On Mon, Nov 16, 2009 at 9:44 AM, Marco Martin notm...@gmail.com wrote:
 On Monday 16 November 2009, Sandro Andrade wrote:
  This sounds like a really useful tool, however kdereview is closed for
  4.4, so would be 4.5 material...
  anyways, since is a developer tool would kdeplasma-addons and kdebase
  would be the proper place? maybe not?

 Aaron suggested kdeplasma-addons as the proper place. Is
 kdeplasma-addons also closed for 4.4 ? Anyway, any review is welcome.

 for me it would be fine to move it in even directly before the hard freeze.
 depends how many agree with that.
 if kdereview is still open, you should move it in really asap


Hi Marco,

I already moved it to kdereview last Saturday because I hadn't noticed
the closing announcement at kde-core-devel. Although the plasmoid is
somehow stable and with some minor enhancements to be done I think a
review it's quite necessary because this is my first plasmoid :)

Thanks,
Sandro

 --
 Marco Martin
 ___
 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: Review Request: KDE Observatory (new plasmoid)

[Sandro Andrade]

Hi Aaron, thanks for the review. I'm answering the questions below
while suggestions will be done asap.

 does Plasma::SignalPlotter give
 you something similar?

Apparently yes, investigating.

 * the collectors really look like something that would be better as a
 DataEngine. putting data and visualization into one plugin is generally
 frowned upon in plasma. things like the periodic updates of the collectors are
 taken care of for you if you use a DataEngine, other widgets can more easily
 use the results, the data can be shared between multiple instances of the
 kdeobservatory widget and the widget would be more ready for remote widget
 use. perhaps not necessary for 4.4, but should definitely be considered for
 4.5.

Yes, I was already considering the DataEngine. Since this should raise
a major impact I'll keep as a lower priority change for 4.4.

 * collectFinished is probably getting called more often than needed as its
 connected to multiple collectors; that means views and what not will get
 updated for collectors that don't have new data?

Although it's called by multiple collectors, views are updated only
when all collectors finish. Since collectors run in a asynchronous way
I don't know each one is going to finish sooner (and consequently
later).

 * calls like m_right-nativeWidget()-setIcon are generally unecessary. use
 m_right-setIcon() i'd look through all the nativeWidget() calls and see which
 can be removed.

I tried this and it's working when using plasmoidviewer. But when
adding the plasmoid in desktop the arrows icons didn't appear. This
was fixed by using nativeWidget()-setIcon. Note: I'm not running
plasma-desktop from trunk, instead I'm just using 4.3.3. I'll try this
in trunk.

 * the icon button in the Configure KDE Observatory page seems to have some
 layout issues; here it overlaps the divider line at the bottom?

Strange, I can't reproduce this here.

 * sync'ing every minute might be a bit much for the default. 5 or 10 minutes
 should be plenty for a default?

For sure :)


 * speaking of defaults, is showing just one day of operations really enough to
 give a decent and moral boosting overview? would the last week's worth of data
 be better? a lot of projects see sporadic but regular commits and one day
 may not be a whole lot of progress. plasma is active daily as are some of the
 other big projects like kdepim ... but not all are so lucky. this does make
 the db building problem worse, of course.

Yes, I agree a week would be a nice overview. I'll change this as soon
as database issues are fixed.


 * why is enable transition effects an option?

Just to disable sliding effect for those people with labyrinthitis :)


 * why are some view options in the global config options and others in the
 Views page?

Ok, in Views page you can select which projects should appear in each
view. Projects are globally created in Projects page and are
automatically inserted in all views. For example, you might want to
see Krazy Report for Plasma but not for Extragear. In Global Config
Options you can disable a given view (including *all* its projects)
and set their appearance order.


 * from a user's perspective, why is there a global config options? would
 another name be more useful?

General ?


 * the automatic transitions are nice, but when trying to page through them
 with the left/right buttons it really gets in the way. perhaps a play/pause
 button could be added to the interface and automatically set it to pause
 when one of the arrow buttons are manually pressed?

Yes, or just re-starting timers giving them a short pause.

 perhaps the transition
 could also pause when the mouse is placed over a graph; this would make the
 tooltips more easily reachable, as right now getting tooltips is a bit of a
 challenge when the animations are ongoing.

Deal :)

 * the scroll arrows feel backwards: the right arrow should take me to the
 next item, which means things should scroll to the left not the right.

Yes, I'm touchscreen influenced :)


 * it would be really nice if it were possible to aggregate some project data;
 e.g. plasma is really kdelibs/plasma + kdebase/runtime/plasma +
 kdebase/workspace/plasmas + kdeplasma-addons ... not a required feature for
 sure, but a nice one to have perhaps

It *was* working that way when I was using regular expressions for
catching commit subjects from QMaps. It was great but I can't query a
SQL database by using a regular expression. Any suggestions ?

 * it would make the widget much more immediately approachable if there were
 some project presets shipped, such as ones for kdelibs, kdepim, kdegames,
 plasma, etc. do you have thoughts on how that would be best achieved?

Yes, that's expected soon. Project information are stored in config
files. I just need to set up those presets as the default values for
new created config files. After that user can include/exclude/edit
project information.


 ok, that's probably more than enough for now :)

Re: Review Request: KDE Observatory (new plasmoid)

[Sandro Andrade]

Some yet missing tasks:

- Plasmoid icon: the initial idea is a keyhole having its inner area
filled with a blue gradient with the KDE logo. I'm trying this but I
wouldn't rely in my artistics skills :)
- Resize features: content isn't yet resized if plasmoid is resized.
- Make it work in a panel: PopupApplet ? I'm investigating.

Thanks,
Sandro

On Sun, Nov 15, 2009 at 3:19 PM, Sandro Andrade
sandro.andr...@gmail.com wrote:
 Just to inform you it's in kdereview for 4.4. This wasn't created in
 reviewboard, sorry for the misleading subject :).

 Sandro

 On Sun, Nov 15, 2009 at 4:26 AM, Sandro Andrade sandroandr...@kde.org wrote:
 Summary:

 Plasmoid for visualizing development activities in KDE projects. The
 motivation comes from the (now inactive) KDE Commit-Digest web site
 and the KDE Observatory aims at provide such information as up-to-date
 as possible in the plasma desktop. The designed architecture uses two
 main components for accomplishing this task: collector and views. A
 collector is responsible for acquiring data from a specific data
 source, such as lists.kde.org or ebn.org, and storing such information
 in a sqlite database. A view provides a visual representation of
 collected data. The plasmoid's configuration options allow for the
 specification of the watched projects (by means of their commit path
 and Krazy report path), selection of which projects should be depicted
 in each view, and some parameters for timers, view transition effects,
 and the extent of days to be analysed in commit history.

 Implemented features:

 - Commit Collector (acquiring data from lists.kde.org) - with incremental 
 update
 - Krazy Collector (acquiring data from www.englishbreakfastnetwork.org)
 - Top Active Projects view (more committed projects)
 - Top Developers view (more active developers - in terms of commits #)
 - Commit History view (graph showing commit # evolution through the
 specified commit extent)
 - Krazy Report view (showing a per project and per file type Krazy
 information)
 - Timed transition of views
 - Slide effect for view transition

 How to use it:

 1) Add the plasmoid (plasmoid name = plasma_applet_kdeobservatory)
 2) Open configurations
 3) The page Projects exhibits all created projects. By clicking the
 Add button a new project can be created (some pre-fabs would be good
 here - Plasma, Amarok, etc). Each project has a name, a commit subject
 (prefix used in subject field of lists.kde.org?l=kde-commits), a Krazy
 report path 
 (http://www.englishbreakfastnetwork.org/krazy/reports/krazy-report-path/index.html),
 and an icon.
 4) The page Views shows the enabled projects in each view (Top
 Active Projects, Top Developers, Commit History, and Krazy Report). By
 default, new created projects are enabled in all views.
 5) The page General provides configuration for the commit extent to
 be collected in lists.kde.org (be prepared for longer acquisition time
 when using higher values - limited to 30 days), the synchronization
 delay, some parameters for view transition, and a general
 enabling/disabling/re-ordering of all projects in a view.

 The Commit History view depends on Qwt (yes, I'm still changing
 CMakeLists.txt :).

 Thanks for any feedback,
 Sandro Andrade




 --
 Sandro Santos Andrade
 
 http://sandroandrade.wordpress.com
 http://liveblue.wordpress.com
 Distributed Systems Laboratory (LaSiD)
 Computer Science Department (DCC)
 Federal University of Bahia - Brazil
 KDE developer - KDevelop project




-- 
Sandro Santos Andrade

http://sandroandrade.wordpress.com
http://liveblue.wordpress.com
Distributed Systems Laboratory (LaSiD)
Computer Science Department (DCC)
Federal University of Bahia - Brazil
KDE developer - KDevelop project
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Review Request: KDE Observatory (new plasmoid)

[Sandro Andrade]

Just to inform you it's in kdereview for 4.4. This wasn't created in
reviewboard, sorry for the misleading subject :).

Sandro

On Sun, Nov 15, 2009 at 4:26 AM, Sandro Andrade sandroandr...@kde.org wrote:
 Summary:

 Plasmoid for visualizing development activities in KDE projects. The
 motivation comes from the (now inactive) KDE Commit-Digest web site
 and the KDE Observatory aims at provide such information as up-to-date
 as possible in the plasma desktop. The designed architecture uses two
 main components for accomplishing this task: collector and views. A
 collector is responsible for acquiring data from a specific data
 source, such as lists.kde.org or ebn.org, and storing such information
 in a sqlite database. A view provides a visual representation of
 collected data. The plasmoid's configuration options allow for the
 specification of the watched projects (by means of their commit path
 and Krazy report path), selection of which projects should be depicted
 in each view, and some parameters for timers, view transition effects,
 and the extent of days to be analysed in commit history.

 Implemented features:

 - Commit Collector (acquiring data from lists.kde.org) - with incremental 
 update
 - Krazy Collector (acquiring data from www.englishbreakfastnetwork.org)
 - Top Active Projects view (more committed projects)
 - Top Developers view (more active developers - in terms of commits #)
 - Commit History view (graph showing commit # evolution through the
 specified commit extent)
 - Krazy Report view (showing a per project and per file type Krazy
 information)
 - Timed transition of views
 - Slide effect for view transition

 How to use it:

 1) Add the plasmoid (plasmoid name = plasma_applet_kdeobservatory)
 2) Open configurations
 3) The page Projects exhibits all created projects. By clicking the
 Add button a new project can be created (some pre-fabs would be good
 here - Plasma, Amarok, etc). Each project has a name, a commit subject
 (prefix used in subject field of lists.kde.org?l=kde-commits), a Krazy
 report path 
 (http://www.englishbreakfastnetwork.org/krazy/reports/krazy-report-path/index.html),
 and an icon.
 4) The page Views shows the enabled projects in each view (Top
 Active Projects, Top Developers, Commit History, and Krazy Report). By
 default, new created projects are enabled in all views.
 5) The page General provides configuration for the commit extent to
 be collected in lists.kde.org (be prepared for longer acquisition time
 when using higher values - limited to 30 days), the synchronization
 delay, some parameters for view transition, and a general
 enabling/disabling/re-ordering of all projects in a view.

 The Commit History view depends on Qwt (yes, I'm still changing
 CMakeLists.txt :).

 Thanks for any feedback,
 Sandro Andrade




-- 
Sandro Santos Andrade

http://sandroandrade.wordpress.com
http://liveblue.wordpress.com
Distributed Systems Laboratory (LaSiD)
Computer Science Department (DCC)
Federal University of Bahia - Brazil
KDE developer - KDevelop project
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Review Request: KDE Observatory (new plasmoid)

[Sandro Andrade]

 This sounds like a really useful tool, however kdereview is closed for 4.4, so
 would be 4.5 material...
 anyways, since is a developer tool would kdeplasma-addons and kdebase would be
 the proper place? maybe not?

Aaron suggested kdeplasma-addons as the proper place. Is
kdeplasma-addons also closed for 4.4 ? Anyway, any review is welcome.

Thanks,
Sandro

 --
 Marco Martin
 ___
 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

Review Request: KDE Observatory (new plasmoid)

[Sandro Andrade]

Summary:

Plasmoid for visualizing development activities in KDE projects. The
motivation comes from the (now inactive) KDE Commit-Digest web site
and the KDE Observatory aims at provide such information as up-to-date
as possible in the plasma desktop. The designed architecture uses two
main components for accomplishing this task: collector and views. A
collector is responsible for acquiring data from a specific data
source, such as lists.kde.org or ebn.org, and storing such information
in a sqlite database. A view provides a visual representation of
collected data. The plasmoid's configuration options allow for the
specification of the watched projects (by means of their commit path
and Krazy report path), selection of which projects should be depicted
in each view, and some parameters for timers, view transition effects,
and the extent of days to be analysed in commit history.

Implemented features:

- Commit Collector (acquiring data from lists.kde.org) - with incremental update
- Krazy Collector (acquiring data from www.englishbreakfastnetwork.org)
- Top Active Projects view (more committed projects)
- Top Developers view (more active developers - in terms of commits #)
- Commit History view (graph showing commit # evolution through the
specified commit extent)
- Krazy Report view (showing a per project and per file type Krazy
information)
- Timed transition of views
- Slide effect for view transition

How to use it:

1) Add the plasmoid (plasmoid name = plasma_applet_kdeobservatory)
2) Open configurations
3) The page Projects exhibits all created projects. By clicking the
Add button a new project can be created (some pre-fabs would be good
here - Plasma, Amarok, etc). Each project has a name, a commit subject
(prefix used in subject field of lists.kde.org?l=kde-commits), a Krazy
report path 
(http://www.englishbreakfastnetwork.org/krazy/reports/krazy-report-path/index.html),
and an icon.
4) The page Views shows the enabled projects in each view (Top
Active Projects, Top Developers, Commit History, and Krazy Report). By
default, new created projects are enabled in all views.
5) The page General provides configuration for the commit extent to
be collected in lists.kde.org (be prepared for longer acquisition time
when using higher values - limited to 30 days), the synchronization
delay, some parameters for view transition, and a general
enabling/disabling/re-ordering of all projects in a view.

The Commit History view depends on Qwt (yes, I'm still changing
CMakeLists.txt :).

Thanks for any feedback,
Sandro Andrade
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

About releasing a new plasmoid

[Sandro Andrade]

Hi everyone,

I'm finishing a new plasmoid for visualizing KDE community activities
and I would like to know how to proceed
for a release. Can I have it in kdeplasma-addons ? Am I in time for
having it in KDE 4.4 ?

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