Registered Member
|
The notification area is really usefull, but sometimes notification take a good part of the screen.
E.G: if i am reading an hardware review on firefox, the popup hide firefox window and i can't read text so, i have to wait or close the notification. Why not add an option to hide notification? If you choose to hide notification, the i ( the icon from which "appear" all notification ) blink each time there is one new notification, so it won't disturb your work.. |
Global Moderator
|
I seem to remember this a while back - where there would be a "work mode" where all notifications would not pop up on your screen depending on which activity you were in. Not yet implemented yet, of course and I don't see it in the 4.4 roadmap either, but then again that roadmap is incomplete and unreliable.
Moult, proud to be a member of KDE forums since 2008-Oct.
thinkMoult - source for tech, art, and animation: hilarity and interest ensured! WIPUP.org - a unique system to share, critique and track your works-in-progress projects. |
Moderator
|
So what approve it, or wait? I'd approve it, as I don't know that anything like that was proposed, and you said it's not in roadmap either. I'll wait a bit. Then I'll approve it.
Primoz, proud to be a member of KDE forums since 2008-Nov.
|
Registered Member
|
We can make a patch..
I looked at the code, and i could find something about notification tray.. We can solve our problem like this: 1) Find the ui settings of the systray to add the option "work mode" 2) make this settings available to be saved or read 3) Find the function which get the dbus signal and call the function to open the popup 4) Block the calling of this function, so we won't see any notification! I'll try to build trunk today, i hope to find something..however the main problem is finding the code which handle dbus signals =(. If anyone has knowledge of kde sources is welcome |
Registered Member
|
hi! is there any new information about that? maybe this could help. this class catches the dbus signal:
i think this function gets called to create a new notification:
does anybody know how can i get the "i" to blink? |
Registered Member
|
Good news, i've done some changes and the busy status is working
http://rapidshare.com/files/344027746/s ... ar.gz.html How to use it: Download and extract enter in the extracted dir. mkdir build cd build cmake -DCMAKE_INSTALL_PREFIX="my kde path" .. sudo make install kbuildsycoca4 kquitapp plasma-desktop plasma-desktop Now add the applet called: System Tray Right click on the " i " and select busy!, notification won't appear until you'll re-click on it The code was taken from here: http://www.kde-look.org/content/show.ph ... b1bf38d72e Tested on 4.4, dunno if it's working on 4.3, i think no. TODO: Make the " i " blinking when you are in busy status. Bettere looking:) The changes are in Applet.cpp (from line 672 ): SetBusyStatus(); CreateMenu(); contextualAction(); I need an help with the blinking " i ". Thanks If you want to help me please write me at : bebebe2 at virgilio dot it |
KDE Developer
|
1. There is a new notification system in development (for 4.5) where notifications don't tend to cover the whole screen and IMO looks much nicer. (Marco is making it)
2. The second thing that is under development are the activities (not plasmoid groups as they are now, but real KDE-wide) which will allow applications to adapt to the current activity. For example, if you are in "Surfing" activity, you'll can all notifications to be shown, but when in "Work" activity, they will be switched off. |
Registered Member
|
I think that kde 4.4 user will be glad to use the busy status, so we can continue our "development" and post it on kde-look
|
KDE Developer
|
Don't get me wrong, I'm not against this patch or anything, I just wanted to let you know what is in the works
|
Registered Member
|
I am sorry , i was a bit angry before for homework :S Sorry
However, i've done some changes to the patch, now it has a better behavior in the context menu. I am waiting to someone which can help me to make the " i " blinking.. I can't understand where is the " i " svg located =( http://rapidshare.com/files/344423863/b ... ar.gz.html |
Registered Member
|
Making the " i " blinking it's not an easy task, just because the code which load the " i " icon is in extendertask.cpp and it's one of the first thing that it's called when the applet start. It would complicate too much the code for my knowledge, but if someone is interested in more detail, please ask
How ever, the final one is here: http://rapidshare.com/files/344976657/b ... ar.gz.html |
Registered Member
|
Hi, I got an error while compiling this plasmoid:
lu@lu-laptop:~/bettere_systray/build$ make Scanning dependencies of target plasma_applet_systemtrayAlt_automoc Generating dbussystemtrayprotocol.moc Generating dbusnotificationprotocol.moc Generating fdotask.moc Generating fdoprotocol.moc Generating notification.moc Generating notificationwidget.moc Generating plasmoidtaskprotocol.moc Generating dbusjobprotocol.moc Generating manager.moc Generating x11embeddelegate.moc Generating jobwidget.moc Generating job.moc Generating dbussystemtraytask.moc Generating plasmoidtask.moc Generating x11embedpainter.moc Generating extendertask.moc Generating jobtotalswidget.moc Generating taskarea.moc Generating task.moc Generating applet.moc Generating x11embedcontainer.moc Generating protocol.moc Generating fdographicswidget.moc Generating moc_fdonotification.cpp Generating moc_dbusnotification.cpp Generating moc_dbusjob.cpp Generating moc_dbussystemtraywidget.cpp Generating moc_fdoselectionmanager.cpp [ 0%] Built target plasma_applet_systemtrayAlt_automoc make[2]: *** Nessuna regola per creare l'obiettivo ??/usr/share/dbus-1/interfaces/org.kde.StatusNotifierItem.xml??, necessario a ??statusnotifieritem_interface.cpp??. Arresto. make[1]: *** [CMakeFiles/plasma_applet_systemtrayAlt.dir/all] Errore 2 make: *** [all] Errore 2 |
Registered Member
|
Are you running on kde 4.4 ? if not you must use it, i don't think it will run on 4.3
|
Registered Member
|
|
Registered Member
|
I dunno, maybe you are missing some devel libs..look if you have workspace devel..etc
ask on #kde maybe:) |
Registered users: Bing [Bot], Evergrowing, Google [Bot]