Notifications ugly in qtcurve without compositing

[jleclanche]

http://i.imgur.com/YiRsg.png

[luis-pereira]

I'm interested in collaborating to develop better notifications.

[jleclanche]

we'll probably go with something close to the ubuntu design. Color should be themable too.

[btaczala]

I'm still having troubles with detecting if composting is on or off.
@luis-pereira do you have any idea about this?

[luis-pereira]

Yes, I do have some ideas. I started writing a new WidgetNotification class. Unfortunately it's not yet complete.

[luis-pereira]

http://imgur.com/IZRhX Running with qtcurve
http://imgur.com/gVSNj Running with cleanlooks

That's what I get..... and it's not beautiful
They were created with the testerapp present in the notification module. I'm fixing the testerapp. We need a simple way to test notifications.

[amoskvin]

You can use notify-send command for testing (It should be part of the libnotify package)

[luis-pereira]

I'm using both. Thanks

[mckaygerhard]

revising code i note changes to improve ui are using xml patterns, thats mean that build of report a dependency of libtq4-xml and libqt4-xmlpatters, that's only present in qt4 4.7.2 and go... excluding many users from stable and old systems to able have razor notification builds

i prefer a less dependency due its suppose a light and simple desktop, how could be light and simplke if with more lines of code generates more dependencies..

now razorqt are not able to build razor notification daemon on old systems (like squeeze and lenny with qt4 4.6.3 framework library, that i backported for many users in Venezuela) excluding a lof ot users

[rburchell]

From memory, QtXmlPatterns has existed since Qt 4.4, which was released in 2008. I'm not sure where you're getting the 4.7.2 idea from. I'm also pretty sure QtXml predates it.

Both of these are in squeeze (and lenny), anyway. Take a look at the package archives for libqt4-xmlpatterns and libqt4-xml.

[mckaygerhard]

i'confirm in recent night build from my laptop, installing libqt4-xmlpatterns in lenny the deb shlibs generations now exits sussesfuly..

thanks.. it's not enought installing libqt4-dev, u must have instaled libqt4-xmlpatterns for shlibs dependency generation on deb build.. either lenny or squeeze..

[mckaygerhard]

now in new compilation from clean env with default qt4 from debian repositories not working..

QtQML are only from 4.7 ai.. broken notification build on debian stable and other distributions...

[mckaygerhard]

QtDeclarative was featured only in 4.7 api too.. more broken build for notification in debian stable and others stable releases distribution, umm i think this affect some fedora and winbuntu releases

theres no fun in the new code if not compile in current distribution

[pvanek]

QtXML is there for ages for sure. QtDeclarative is the other case (unfortunately).

W0land, how is it de4signed, please? I thought that when no QML is found the pure qwidget solution is used. But it's hardcoded into cmakelists.txt to use QML now...

[mckaygerhard]

due this issue, i update the wiki Dependencies of razorqt git.. and must be wait for session hadler CmakeInstall fixed in XDG autostart , to repare and fixed debian related issue.

[luis-pereira]

I've been away for some time. What's the bug with cmake install ?

[mckaygerhard]

Dependence of QML its not reflected in cmakefile, and QML usaghe are no funny for stable current distributions like slackware, some funtoo and debian..

its better does that in a no-qt4 spoecific release, and more compatible with more stable and light linuxes like slitaz, and debian.. there's no light dekstop if i must use more heaviweith api (qt4.7 and 4.8 are more greater and heavy thant 4.5 and 4.6)

[pvanek]

Luis, I expect (quickly looking into the sources) that when there is no QML support found, the QWidget based implementation should be used. Am I right? Then it would be fine to implement some check for qt version/qml presence in cmakelists.txt. I can do it quite easily. But only if my expectations are correct...

[luis-pereira]

The qml backend can only be run by passing --no-daemon --qml to razor-notificationd.
Just take a look at razorqt-notify/src/main.cpp.

The QT_USE_QTDECLARATIVE and the QT_USE_QTDBUS aren't actually used.

What (I think) PICCORO Lenz McKAY is talking is the missing is the CMakeLists code to skip building the qmlnotifications when qt-declarative isn't present.

[mckaygerhard]

yah, thats i taking about..

On Tue, May 22, 2012 at 6:05 PM, Luís Pereira <
reply@reply.github.com

wrote:

The qml backend can only be run by passing --no-daemon --qml to
razor-notificationd.
Just take a look at razorqt-notify/src/main.cpp.

The QT_USE_QTDECLARATIVE and the QT_USE_QTDBUS aren't actually used.

What (I think) PICCORO Lenz McKAY is talking is the missing is the
CMakeLists code to skip building the qmlnotifications when qt-declarative
isn't present.

---

Reply to this email directly or view it on GitHub:
#272 (comment)

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Cofundador de Venenux; debian based multimedia alike free only zealots
users (oh well, i try but..too many free guidelines buahhh)
http://shutendouji.net
creador de massenkoh linux; debian enhanchements for better up to date
support on stable brand, including non-free soft.

[pvanek]

OK, because we have new notifications now (qwidget based only now) I'm closing this issue. Please test new stuff.

[mckaygerhard]

oohhh thanks many many thanks... working perectly, some minor issues: 2280494#commitcomment-1441316 please see, thanks.. some other issues with qt 4.6 in others.. here: https://groups.google.com/group/razor-qt/browse_thread/thread/36cec5da83ff6291

Thanks.-