Various KDE 1.-4. Improvements
Developers Apps
Graphic Apps
System Software
Video Apps
Thanks for the patch, I just applied it!
Regarding file operations: to me notifications and file progress information are different concepts, it just happens that Plasma by default group them.
One needs to be able to interact with the file progress view, so it does not make sense to me to add this to Colibri. I personally uses Colibri together with the Plasma file progress view. It works well. - Feb 04 2014
Regarding file operations: to me notifications and file progress information are different concepts, it just happens that Plasma by default group them.
One needs to be able to interact with the file progress view, so it does not make sense to me to add this to Colibri. I personally uses Colibri together with the Plasma file progress view. It works well. - Feb 04 2014
Colibri does not show file transfers. You can either:
- Remove Plasma notification applet from the systemtray. This way you get classic file transfer dialogs.
- Keep Plasma notification applet in the systemtray, but uncheck the "Application Notification" box. This way you get Plasma file transfer indications and Colibri notifications.
For more info, see:
http://agateau.com/projects/colibri/setup/ - Jun 03 2013
- Remove Plasma notification applet from the systemtray. This way you get classic file transfer dialogs.
- Keep Plasma notification applet in the systemtray, but uncheck the "Application Notification" box. This way you get Plasma file transfer indications and Colibri notifications.
For more info, see:
http://agateau.com/projects/colibri/setup/ - Jun 03 2013
It is not possible to do this. What you can do for Kopete is to use the message-indicator plugin [1] together with the message-indicator Plasma widget [2].
[1]: https://launchpad.net/kopete-message-indicator
[2]: https://launchpad.net/plasma-widget-message-indicator - Oct 14 2010
[1]: https://launchpad.net/kopete-message-indicator
[2]: https://launchpad.net/plasma-widget-message-indicator - Oct 14 2010
What you are seeing is not Colibri: it is Notification-daemon, the default GNOME notification display. You should be able to fix this by uninstalling notification-daemon.
Unfortunately there is no way right now for a DBus service like Colibri or Notification-daemon to specify it should only run on KDE or GNOME. - Jun 10 2010
Unfortunately there is no way right now for a DBus service like Colibri or Notification-daemon to specify it should only run on KDE or GNOME. - Jun 10 2010
Reasons for not using actions on notifications are:
- it avoids the "urge to respond": you are not stressed by having to click on a button before it goes away because there is no button
- it allows for click-through
As I said, you may or may not like this. If you don't it's totally fine, just use the default Plasma notifications. - Feb 23 2010
- it avoids the "urge to respond": you are not stressed by having to click on a button before it goes away because there is no button
- it allows for click-through
As I said, you may or may not like this. If you don't it's totally fine, just use the default Plasma notifications. - Feb 23 2010
The service file is a problematic indeed. You can rename it (dbus does not care about the name), but then you may end up with two implementations of the same service, and in this case dbus picks the first one it finds :/
I'll have a look at these CPack lines. - Feb 18 2010
I'll have a look at these CPack lines. - Feb 18 2010
That's weird. Anyway, the config file is .kde/share/config/colibrirc
For now it looks like this:
[General]
Alignment=68
Where 68 is the OR of the various Qt::Alignment flags:
Qt::AlignLeft 1
Qt::AlignRight 2
Qt::AlignHCenter 4
Qt::AlignTop 32
Qt::AlignBottom 64
Qt::AlignVCenter 128 - Feb 11 2010
For now it looks like this:
[General]
Alignment=68
Where 68 is the OR of the various Qt::Alignment flags:
Qt::AlignLeft 1
Qt::AlignRight 2
Qt::AlignHCenter 4
Qt::AlignTop 32
Qt::AlignBottom 64
Qt::AlignVCenter 128 - Feb 11 2010
Hi,
I guess you are the person I discussed with on #kde-devel about gmpc.
I did not understand you were using a custom script to send volume notifications, so could not reproduce your bug. Can you share how you configured the system to send volume info with notify-send? - Dec 22 2009
I guess you are the person I discussed with on #kde-devel about gmpc.
I did not understand you were using a custom script to send volume notifications, so could not reproduce your bug. Can you share how you configured the system to send volume info with notify-send? - Dec 22 2009
What do you have instead?
If notifications are represented as light grey rectangles with a black border, then probably the service file is not properly installed. Check that /usr/share/dbus-1/services/ contains a file named "org.freedesktop.Notifications.services" and that this file contains an Exec line pointing to the colibri binary.
If notifications are represented as Plasma notifications, open the systemtray settings: "Application notifications" should be unchecked. - Dec 20 2009
If notifications are represented as light grey rectangles with a black border, then probably the service file is not properly installed. Check that /usr/share/dbus-1/services/ contains a file named "org.freedesktop.Notifications.services" and that this file contains an Exec line pointing to the colibri binary.
If notifications are represented as Plasma notifications, open the systemtray settings: "Application notifications" should be unchecked. - Dec 20 2009
Nice to hear you like it!
Behind the scenes, file transfers are completely different than notifications. It may take quite some work to integrate them as well.
I am also not sure it would be very handy because you want to be able to interact with a file transfer but Colibri notifications are passive (no buttons)
To me file transfers belong to the application, not to the workspace: I personally disabled Plasma handling of file transfers, so I get classic file transfer windows.
- Dec 18 2009
Behind the scenes, file transfers are completely different than notifications. It may take quite some work to integrate them as well.
I am also not sure it would be very handy because you want to be able to interact with a file transfer but Colibri notifications are passive (no buttons)
To me file transfers belong to the application, not to the workspace: I personally disabled Plasma handling of file transfers, so I get classic file transfer windows.
- Dec 18 2009
I should probably add another excerpt from the README to the description:
---------
Passive notifications for Plasma first appeared as "Ayatana notifications", an
alternative notification system I implemented in Kubuntu Karmic as part of my
work for Canonical.
Ayatana notifications were implemented as a patch against the systemtray
applet. Colibri is based on this work, but does not require patching any
applet.
Colibri contains code I wrote for Canonical, but it is not a Canonical product.
--------- - Dec 16 2009
---------
Passive notifications for Plasma first appeared as "Ayatana notifications", an
alternative notification system I implemented in Kubuntu Karmic as part of my
work for Canonical.
Ayatana notifications were implemented as a patch against the systemtray
applet. Colibri is based on this work, but does not require patching any
applet.
Colibri contains code I wrote for Canonical, but it is not a Canonical product.
--------- - Dec 16 2009
Concerning the "location" rectangle: I can't reproduce it. Can you mail me these files:
- ~/.kde/share/config/gwenviewrc
- ~/.kde/share/apps/gwenview/gwenviewui.rc
Concerning the fullscreen start: For now, you need to modify the file association so that it starts with the "-f" option. - Jul 17 2006
- ~/.kde/share/config/gwenviewrc
- ~/.kde/share/apps/gwenview/gwenviewui.rc
Concerning the fullscreen start: For now, you need to modify the file association so that it starts with the "-f" option. - Jul 17 2006
It does support space in filenames. The ioslave (lexeo:) in however does not support very well space in keywords.
Also note that you must add a '/' after the ':' when using the ioslave. Example:
"lexeo:/keyword1 and keyword2" OK
"lexeo:keyword1 and keyword2" NOT OK - Oct 06 2005
Also note that you must add a '/' after the ':' when using the ioslave. Example:
"lexeo:/keyword1 and keyword2" OK
"lexeo:keyword1 and keyword2" NOT OK - Oct 06 2005
You can start lexeo_edit from within Gwenview via an external tool.
If everything has installed ok, when you right click an image in Gwenview and go in "External tools", you should see a "Lexeo - Edit Keywords" entry which will start lexeo_edit.
If it's not the case, you need to declare lexeo_edit as an external tool:
- Go to this menu: settings>Configure External Tools
- Click "Add"
- Enter a name for your tool
- Use "lexeo_edit %F" as a command (without the quotes)
- Select "All files"
- Click "Ok"
It should work now.
To browse images according to the keywords, you must use the ioslave. In either Gwenview or Konqueror, type "lexeo:/some_keyword" to get all images/files matching this keyword. With "lexeo:/keyword1 and keyword2" you will get only images matching keyword1 and keyword2. - Oct 04 2005
If everything has installed ok, when you right click an image in Gwenview and go in "External tools", you should see a "Lexeo - Edit Keywords" entry which will start lexeo_edit.
If it's not the case, you need to declare lexeo_edit as an external tool:
- Go to this menu: settings>Configure External Tools
- Click "Add"
- Enter a name for your tool
- Use "lexeo_edit %F" as a command (without the quotes)
- Select "All files"
- Click "Ok"
It should work now.
To browse images according to the keywords, you must use the ioslave. In either Gwenview or Konqueror, type "lexeo:/some_keyword" to get all images/files matching this keyword. With "lexeo:/keyword1 and keyword2" you will get only images matching keyword1 and keyword2. - Oct 04 2005