Re: Re: kill the systray?

2013-09-26 Thread Matthias Klumpp
2013/9/25 Martin Gräßlin mgraess...@kde.org:
 On Thursday 26 September 2013 01:27:54 Aaron J. Seigo wrote:
 On Tuesday, September 24, 2013 17:06:14 Sebastian Kügler wrote:
  When I asked Martin if he knew a way to do the xembed, he replied (being
  Martin ;)) asking if we can just kill it and quoted starwars. I wonder:
  Can
  we kill it yet?

 I just had a discussion on G+ with a couple of our friends with GNOME about
 this matter[1]. Apparently they are thinking of just dropping support for
 system tray icons altogether, and deprecating the API in Gtk+. If that does
 indeed happen, then that is a major step towards being able to kill support
 for it.
 the bad part of the discussion is that it looks like they want to reinvent the
 wheel and given some statements lately (e.g. GTK+ is just for developing for
 GNOME Shell) I'm not every optimistic that they will even hardly think about
 anything than their system.
I also fear that, but this was a statement by single developers, which
I don't think is true.
It would make sense to at least try to discuss stuff and try to find a
consent, and I am willing to try that (there would be no harm done if
this attempt fails).
There are some things which GNOME does great at time (notifications,
IMHO) and which might be worth looking at and working on a common
spec.
The problem with GNOME is that it is now design-driven, and everyone
and everything has to accept a subordinate role to that. So, in order
to convince the GNOME folks, you have to give them a usecase which
matches their design goals.

 The only remaining problem then becomes Qt5. QSystemTrayIcon does not
 support the DBus protocol .. it should, really, since the two largest Linux
 desktop envs built on Qt use it ;)
 looks like we need to fix that for 5.3 :-)
Indeed :-)
Cheers,
Matthias
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: pot files not being generated anymore

2013-09-26 Thread Bhushan Shah
Hello,

I went through list and this is result... I have pushed missing files
to the repo with commit
http://commits.kde.org/kde-workspace/09aae2d121896d8d065291285aacd53a1596418d

+2013-05-08 templates/messages/kde-workspace/plasma_applet_clock.pot
It should related Messages.sh are there..
bshah@kubuntu:~/src/kde/kde-workspace$ cat
plasma/generic/applets/analog-clock/Messages.sh
#! /usr/bin/env bash
$EXTRACTRC *.ui  rc.cpp
$XGETTEXT *.cpp -o $podir/plasma_applet_clock.pot
rm -f rc.cpp

No i18n calls = +2013-05-08
templates/messages/kde-workspace/plasma_applet_dig_clock.pot
No i18n calls = +2013-05-08
templates/messages/kde-workspace/plasma_applet_icon.pot
Corrected = +2013-05-08 templates/messages/kde-workspace/plasma_applet_panel.pot
Corrected = +2013-05-08 templates/messages/kde-workspace/plasma_applet_trash.pot
Corrected = +2013-05-08
templates/messages/kde-workspace/plasma_applet_windowlist.pot

+2013-05-08 
templates/messages/kde-workspace/plasma_containmentactions_switchdesktop.pot
It should related Messages.sh are there..
bshah@kubuntu:~/src/kde/kde-workspace$ cat
plasma/generic/containmentactions/switchdesktop/Messages.sh
#! /usr/bin/env bash
$XGETTEXT *.cpp -o $podir/plasma_containmentactions_switchdesktop.pot

Corrected = +2013-05-08
templates/messages/kde-workspace/plasma_toolbox_desktoptoolbox.pot

No i18n calls = +2013-05-08
templates/messages/kde-workspace/plasma_toolbox_paneltoolbox.pot
No i18n calls = +2013-05-08
templates/messages/kde-workspace/plasma_wallpaper_color.pot

Delete it, renamed to plasma_applet_kickoff.pot
+2013-06-06 templates/messages/kde-workspace/plasma_applet_launcher.pot

Corrected = +2013-08-27 templates/messages/kde-workspace/plasma_applet_tasks.pot

Thanks!

On Thu, Sep 26, 2013 at 5:57 AM, Sebastian Kügler se...@kde.org wrote:
 On Thursday, September 26, 2013 02:05:12 Albert Astals Cid wrote:
  They're all very much alive and kicking. Question: are those files not
  generated anymore because no i18n calls are found, or is the Messages.sh
  simply missing?

 Either of the cases can be the reason, you'll have to look at why for each
 of  them.

 OK, thanks. I'll fix. :)
 --
 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
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: QML-using app developers: use private.* imports

2013-09-26 Thread Marco Martin
On Thursday 26 September 2013 02:23:31 Aleix Pol wrote:

 The question would be then, why is it that there's some API that's only
 needed for internal usage? If it's needed internally, it will be most
 likely needed externally, at some point. The fact that you decide to label
 it as private makes frustrated developers.
 
 Either way, I have no idea of what we're talking about here. :D

is the fact that the most feasible way to bridge the c++ of an app and the qml 
part is trough imports.
you once told me you did some imports for use in muon for instance, 
and while there may be some parts of those that does have an use outside that 
application for everybody to use, all of it surely isn't, being its use just 
bridge functionality of that particular application, and that's fine.

However, i would like everything in org.kde.* to be considered a library, with 
all the requirements of api stability for the entire lifecycle, and requiring 
this kind of discipline from all random developers is simply not realistic.

then, of course if an app developer decides that a part of his private.foo may 
make sense for everybody to use can always move it, but by accepting all the 
social contract that maintaining a library means

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


Re: pot files not being generated anymore

2013-09-26 Thread Marco Martin
On Wednesday 25 September 2013 23:32:18 Sebastian Kügler wrote:
  Shall I delete them or are they going to make a come back anytime soon?
 
 They're all very much alive and kicking. Question: are those files not
 generated anymore because no i18n calls are found, or is the Messages.sh
 simply missing?
 
 In any case, it needs fixing, not deleting.

probably many of the new ported plasmoids don't have a messages.so (also, they 
may have changed plugin name)

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


Re: kill the systray?

2013-09-26 Thread Marco Martin
On Thursday 26 September 2013 01:27:54 Aaron J. Seigo wrote:
 
 The only remaining problem then becomes Qt5. QSystemTrayIcon does not
 support the DBus protocol .. it should, really, since the two largest Linux
 desktop envs built on Qt use it ;)

back in the days i remember a big blocker was that qtgui must not depend from 
qtdbus

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


Re: Re: kill the systray?

2013-09-26 Thread Martin Gräßlin
On Thursday 26 September 2013 11:35:02 Marco Martin wrote:
 On Thursday 26 September 2013 01:27:54 Aaron J. Seigo wrote:
  The only remaining problem then becomes Qt5. QSystemTrayIcon does not
  support the DBus protocol .. it should, really, since the two largest
  Linux
  desktop envs built on Qt use it ;)
 
 back in the days i remember a big blocker was that qtgui must not depend
 from qtdbus
That's probably still the case and I also thought that this might be the case. 
But maybe we can do something with a plugin like the DBusMenu stuff? Really 
awesome would be if we could enforce status notifiers through our QPA plugin.

Cheers
Martin

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


Plasma-framework cmake issue

2013-09-26 Thread Antonis Tsiapaliokas
Hello,

I was trying to build plasma-framework but cmake fails.
The installation was with a clean install/build dir of everything.

If you need more info, please let me know...

P.S. I have attached the cmake error.

Regards,
Antonis


error-cmake
Description: Binary data
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: Plasma-framework cmake issue

2013-09-26 Thread Sebastian Kügler
Hi Antonis,

On Thursday, September 26, 2013 16:10:21 Antonis Tsiapaliokas wrote:
 I was trying to build plasma-framework but cmake fails.
 The installation was with a clean install/build dir of everything.
 
 If you need more info, please let me know...
 
 P.S. I have attached the cmake error.

I've sent an email to kde-frameworks-devel pointing out this issue.

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: Plasma-framework cmake issue

2013-09-26 Thread Sebastian Kügler
On Thursday, September 26, 2013 15:24:46 Sebastian Kügler wrote:
 Hi Antonis,
 
 On Thursday, September 26, 2013 16:10:21 Antonis Tsiapaliokas wrote:
  I was trying to build plasma-framework but cmake fails.
  The installation was with a clean install/build dir of everything.
  
  If you need more info, please let me know...
  
  P.S. I have attached the cmake error.
 
 I've sent an email to kde-frameworks-devel pointing out this issue.
 
 Cheers,

It's fixed now, update e-c-m and kdelibs.
-- 
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: kill the systray?

2013-09-26 Thread Aaron J. Seigo
On Wednesday, September 25, 2013 23:06:42 Matthias Klumpp wrote:
 I also fear that, but this was a statement by single developers, which
 I don't think is true.

it is the developer responsible for the component in question, and apparently 
he’s already doing work to create new incompatibilities in the messaging spec.

if that is indeed what happens and it becomes a GNOME Shell specific thing, i 
don’t think we should implement support for it for all the same reasons we’re 
not implementing support for Mir.

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


Re: Review Request 112959: Add color picker in plasmaextracomponents

2013-09-26 Thread Bhushan Shah

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

(Updated Sept. 26, 2013, 4:36 p.m.)


Review request for Plasma and Marco Martin.


Description
---

Add color picker in PlasmaExtras


Diffs (updated)
-

  src/declarativeimports/plasmaextracomponents/qml/ColorPicker.qml PRE-CREATION 
  src/declarativeimports/plasmaextracomponents/qml/qmldir c59e62f 

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


Testing
---


Thanks,

Bhushan Shah

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


Re: pot files not being generated anymore

2013-09-26 Thread Albert Astals Cid
El Dijous, 26 de setembre de 2013, a les 12:06:44, Bhushan Shah va escriure:
 Hello,
 
 I went through list and this is result... I have pushed missing files
 to the repo with commit
 http://commits.kde.org/kde-workspace/09aae2d121896d8d065291285aacd53a1596418
 d
 
 +2013-05-08 templates/messages/kde-workspace/plasma_applet_clock.pot
 It should related Messages.sh are there..
 bshah@kubuntu:~/src/kde/kde-workspace$ cat
 plasma/generic/applets/analog-clock/Messages.sh
 #! /usr/bin/env bash
 $EXTRACTRC *.ui  rc.cpp
 $XGETTEXT *.cpp -o $podir/plasma_applet_clock.pot
 rm -f rc.cpp

And it's wrong, no?

Cheers,
  Albert

 
 No i18n calls = +2013-05-08
 templates/messages/kde-workspace/plasma_applet_dig_clock.pot
 No i18n calls = +2013-05-08
 templates/messages/kde-workspace/plasma_applet_icon.pot
 Corrected = +2013-05-08
 templates/messages/kde-workspace/plasma_applet_panel.pot Corrected =
 +2013-05-08 templates/messages/kde-workspace/plasma_applet_trash.pot
 Corrected = +2013-05-08
 templates/messages/kde-workspace/plasma_applet_windowlist.pot
 
 +2013-05-08
 templates/messages/kde-workspace/plasma_containmentactions_switchdesktop.po
 t It should related Messages.sh are there..
 bshah@kubuntu:~/src/kde/kde-workspace$ cat
 plasma/generic/containmentactions/switchdesktop/Messages.sh
 #! /usr/bin/env bash
 $XGETTEXT *.cpp -o $podir/plasma_containmentactions_switchdesktop.pot
 
 Corrected = +2013-05-08
 templates/messages/kde-workspace/plasma_toolbox_desktoptoolbox.pot
 
 No i18n calls = +2013-05-08
 templates/messages/kde-workspace/plasma_toolbox_paneltoolbox.pot
 No i18n calls = +2013-05-08
 templates/messages/kde-workspace/plasma_wallpaper_color.pot
 
 Delete it, renamed to plasma_applet_kickoff.pot
 +2013-06-06 templates/messages/kde-workspace/plasma_applet_launcher.pot
 
 Corrected = +2013-08-27
 templates/messages/kde-workspace/plasma_applet_tasks.pot
 
 Thanks!
 
 On Thu, Sep 26, 2013 at 5:57 AM, Sebastian Kügler se...@kde.org wrote:
  On Thursday, September 26, 2013 02:05:12 Albert Astals Cid wrote:
   They're all very much alive and kicking. Question: are those files not
   generated anymore because no i18n calls are found, or is the
   Messages.sh
   simply missing?
  
  Either of the cases can be the reason, you'll have to look at why for
  each
  of  them.
  
  OK, thanks. I'll fix. :)
  --
  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

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


Re: kill the systray?

2013-09-26 Thread Matthias Klumpp
2013/9/26 Aaron J. Seigo ase...@kde.org:
 On Wednesday, September 25, 2013 23:06:42 Matthias Klumpp wrote:
 I also fear that, but this was a statement by single developers, which
 I don't think is true.

 it is the developer responsible for the component in question, and apparently
 he’s already doing work to create new incompatibilities in the messaging spec.
That is indeed bad if it comes from the person responsible for the
feature. Incompatibilities are okay, IMHO, as long as they really
provide improvements and are not just bikeshed about e.g. function
naming or wheel-reinventing of working specs.
So let's see what will be proposed at XDG.

 if that is indeed what happens and it becomes a GNOME Shell specific thing, i
 don’t think we should implement support for it for all the same reasons we’re
 not implementing support for Mir.
Jup, we shouldn't do that then. But I can't see what is GNOME-specific
about it (yet).
Maybe the persistent-notifications-after-reboot thing will be a
(solvable) issue.

We would still have a problem with applications which only provide a
tray icon for interaction... It would be nice to solve that.
Unfortunately, I am busy with AppStream and Listaller stuff, but I
would love to help with the
notification/tray/GNOME-KDE-XDG-communication issues. I think I will
have some time in mid-October.
Meanwhile I will ask some people at GNOME about placing the tray
data at different positions and implementing a tray XDG spec in line
with GNOME design principles. But I don't expect much success there -
it's worth a try anyway ;-)
Cheers,
Matthias


-- 
Debian Developer | Freedesktop-Developer
KDE-Developer| GNOME-Contributor
I welcome VSRE emails. See http://vsre.info/
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel