Review Request: Drop Xinerama related options in KWin
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103756/ --- Review request for kwin and Plasma. Description --- As discussed on the mailinglist: drop of the xinerama related options and the kcm. Given that the show unmanaged windows on option is in fact not used, I dropped the complete KCM. Diffs - kcontrol/CMakeLists.txt 8cd9a46 kcontrol/xinerama/CMakeLists.txt fe332e5 kcontrol/xinerama/Messages.sh f4aa134 kcontrol/xinerama/interface_util.h 8a4fcd1 kcontrol/xinerama/kcmxinerama.h 18b9241 kcontrol/xinerama/kcmxinerama.cpp a456b2c kcontrol/xinerama/test_kcm_xinerama.cpp a358a2c kcontrol/xinerama/xinerama.desktop e8ce525 kcontrol/xinerama/xineramawidget.h 2c446a2 kcontrol/xinerama/xineramawidget.cpp df9cb2f kcontrol/xinerama/xineramawidget.ui 90ec4d4 kwin/geometry.cpp a414e26 kwin/manage.cpp c551eac kwin/options.h 9dc29cf kwin/options.cpp d496569 kwin/tabbox/tabbox.cpp 3051316 kwin/toplevel.cpp ffe7f0c kwin/workspace.cpp 69b4ecb Diff: http://git.reviewboard.kde.org/r/103756/diff/diff Testing --- Fullscreen: works Maximize: works Movment: works Placement: works Thanks, Martin Gräßlin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Review Request: Make text color apply even when you go back to the first char of the notes, see bug 291791
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103758/ --- Review request for Plasma. Description --- Fixes 291791 This addresses bug 291791. http://bugs.kde.org/show_bug.cgi?id=291791 Diffs - applets/notes/notes.cpp e8ef779 Diff: http://git.reviewboard.kde.org/r/103758/diff/diff Testing --- Local tests following bug 291791 steps Thanks, Anne-Marie Mahfouf ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: prep'ing the QML screenlocker for a merge into master
On Saturday 21 January 2012 15:32:10 Aaron J. Seigo wrote: it uses QGraphicsLayouts because we need to embed QWidgets. Unfortunately we do not get to the underlying system. If we don't want anymore the QWidgets we would have to rewrite the complete authentication system :-( yes, i know. however, there are some things used in the QML that are probably not needed / should be replaced with the components work. right, I didn't like to have the keyboard switcher embedded as a QWidget for example. * related to the above, blanking the screen is now left up to powermanagement. fair enough. however, the defaults for powermanagement for systems that are plugged in tends to mean it won't happen for quite some time on most systems. it feels rather innelegant to have the lock screen just always showing. in the default theme, fading out at least the greater UI when there is no user interaction and back in when user interaction happens (independent of power management) might feel nicer. I would prefer to get this right and turn off the screen. Blanking the screen by painting black feels wrong to me. In fact I always thought that my screen turns off till I used the new locker ah, yes, i would like to do it with turning off the screen (rather than just painting black) good * the default wallpaper of the desktop theme is used when locking the screen. this doesn't feel right; looking at that default paper, i expect the wallpaper shown on my desktop that i've configured. This would require to pull in the complete Plasma Wallpaper stuff. And this becomes really difficult for things like multi screen. nah, it's pretty easy for multiscreen. still, i do prefer the idea of a lock- screen specific thing (perhaps something that is coordinated with the QML log in screen too?) I would like to have it coordinated with the log in screen. I think this would give a very pleasant experience especially if we go for not stopping at KDM but logging in the user directly (as done on PA). 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
Re: Connecting to Data Engine in QT Quick
On Sun, Jan 22, 2012 at 7:27 AM, Shaun Reich shaun.re...@kdemail.netwrote: On Sat, Jan 21, 2012 at 11:53 PM, Eric Mesa ericsbinarywo...@gmail.com wrote: Working with QT Quick in QT Creator. Using QML to do GUI design. Finally figured out my data engine issues that I emailed about about back in August. So now I want to connect to my data engine. I found this website: http://techbase.kde.org/Development/Tutorials/Plasma/QML/API#Data_Engines but when I put in import org.kde.plasma.core 0.1 as PlasmaCore (no quotes) I get the error module org.kde.plasma.core is not installed that import is only valid if you are making a plasmoid. through a raw QML thingy you can't use core components. core components is only meant as a plasmoid goodie bag. you can still use org.kde.plasmacomponents afik though. but if you're using a dataengine in the first place...and a QML applet..i have to ask why it isn't a plasmoid in the first place. probably make things a lot easier... as for 'packages', the imports are in kde-runtime/plasma/declarativeimports, so having that should be fine. I have to correct you there :) You can perfectly use the plasma imports of you let QML know about the path. Just add QML_IMPORT_PATH += /path/to/plasmacomponents (lookup the right path please, don't know it out of my head) and you can start using plasmacomponents in your qml app. It's that easy! ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Connecting to Data Engine in QT Quick
On Sunday 22 January 2012, Shaun Reich wrote: On Sat, Jan 21, 2012 at 11:53 PM, Eric Mesa ericsbinarywo...@gmail.com wrote: Working with QT Quick in QT Creator. Using QML to do GUI design. Finally figured out my data engine issues that I emailed about about back in August. So now I want to connect to my data engine. I found this website: http://techbase.kde.org/Development/Tutorials/Plasma/QML/API#Dat a_Engines but when I put in import org.kde.plasma.core 0.1 as PlasmaCore (no quotes) I get the error module org.kde.plasma.core is not installed that import is only valid if you are making a plasmoid. through a raw QML thingy you can't use core components. core components is only meant as a plasmoid goodie bag. nope, plasma components work just fine anywhere. here the problem is just about the right qml import path not being set Cheers, Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Connecting to Data Engine in QT Quick
nope, plasma components work just fine anywhere. here the problem is just about the right qml import path not being set i said plasmacore, not plasmacomponents. or does it also apply to that as well? -- Shaun Reich, KDE Software Developer (kde.org) ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Connecting to Data Engine in QT Quick
On Sunday 22 January 2012, Shaun Reich wrote: nope, plasma components work just fine anywhere. here the problem is just about the right qml import path not being set i said plasmacore, not plasmacomponents. or does it also apply to that as well? yep, just fine. -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Review Request: Drop Xinerama related options in KWin
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103756/#review1 --- Ship it! Tested and everything works as expected :) ! - Alex Fiestas On Jan. 22, 2012, 10:21 a.m., Martin Gräßlin wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103756/ --- (Updated Jan. 22, 2012, 10:21 a.m.) Review request for kwin and Plasma. Description --- As discussed on the mailinglist: drop of the xinerama related options and the kcm. Given that the show unmanaged windows on option is in fact not used, I dropped the complete KCM. Diffs - kcontrol/CMakeLists.txt 8cd9a46 kcontrol/xinerama/CMakeLists.txt fe332e5 kcontrol/xinerama/Messages.sh f4aa134 kcontrol/xinerama/interface_util.h 8a4fcd1 kcontrol/xinerama/kcmxinerama.h 18b9241 kcontrol/xinerama/kcmxinerama.cpp a456b2c kcontrol/xinerama/test_kcm_xinerama.cpp a358a2c kcontrol/xinerama/xinerama.desktop e8ce525 kcontrol/xinerama/xineramawidget.h 2c446a2 kcontrol/xinerama/xineramawidget.cpp df9cb2f kcontrol/xinerama/xineramawidget.ui 90ec4d4 kwin/geometry.cpp a414e26 kwin/manage.cpp c551eac kwin/options.h 9dc29cf kwin/options.cpp d496569 kwin/tabbox/tabbox.cpp 3051316 kwin/toplevel.cpp ffe7f0c kwin/workspace.cpp 69b4ecb Diff: http://git.reviewboard.kde.org/r/103756/diff/diff Testing --- Fullscreen: works Maximize: works Movment: works Placement: works Thanks, Martin Gräßlin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Review Request: Drop Xinerama related options in KWin
On Jan. 22, 2012, 6:09 p.m., Alex Fiestas wrote: Tested and everything works as expected :) ! just ftr: afaics there's no way for a desktop wall (ie. treating all screens as one) left, is it? personally i don't mind, but there might have been claims on this at kcd. - Thomas --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103756/#review1 --- On Jan. 22, 2012, 10:21 a.m., Martin Gräßlin wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103756/ --- (Updated Jan. 22, 2012, 10:21 a.m.) Review request for kwin and Plasma. Description --- As discussed on the mailinglist: drop of the xinerama related options and the kcm. Given that the show unmanaged windows on option is in fact not used, I dropped the complete KCM. Diffs - kcontrol/CMakeLists.txt 8cd9a46 kcontrol/xinerama/CMakeLists.txt fe332e5 kcontrol/xinerama/Messages.sh f4aa134 kcontrol/xinerama/interface_util.h 8a4fcd1 kcontrol/xinerama/kcmxinerama.h 18b9241 kcontrol/xinerama/kcmxinerama.cpp a456b2c kcontrol/xinerama/test_kcm_xinerama.cpp a358a2c kcontrol/xinerama/xinerama.desktop e8ce525 kcontrol/xinerama/xineramawidget.h 2c446a2 kcontrol/xinerama/xineramawidget.cpp df9cb2f kcontrol/xinerama/xineramawidget.ui 90ec4d4 kwin/geometry.cpp a414e26 kwin/manage.cpp c551eac kwin/options.h 9dc29cf kwin/options.cpp d496569 kwin/tabbox/tabbox.cpp 3051316 kwin/toplevel.cpp ffe7f0c kwin/workspace.cpp 69b4ecb Diff: http://git.reviewboard.kde.org/r/103756/diff/diff Testing --- Fullscreen: works Maximize: works Movment: works Placement: works Thanks, Martin Gräßlin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Review Request: Drop Xinerama related options in KWin
On Jan. 22, 2012, 6:09 p.m., Alex Fiestas wrote: Tested and everything works as expected :) ! Thomas Lübking wrote: just ftr: afaics there's no way for a desktop wall (ie. treating all screens as one) left, is it? personally i don't mind, but there might have been claims on this at kcd. As far as I understood you can disable xinerama to get just this, requires more digging but the option is still there. - Alex --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103756/#review1 --- On Jan. 22, 2012, 10:21 a.m., Martin Gräßlin wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103756/ --- (Updated Jan. 22, 2012, 10:21 a.m.) Review request for kwin and Plasma. Description --- As discussed on the mailinglist: drop of the xinerama related options and the kcm. Given that the show unmanaged windows on option is in fact not used, I dropped the complete KCM. Diffs - kcontrol/CMakeLists.txt 8cd9a46 kcontrol/xinerama/CMakeLists.txt fe332e5 kcontrol/xinerama/Messages.sh f4aa134 kcontrol/xinerama/interface_util.h 8a4fcd1 kcontrol/xinerama/kcmxinerama.h 18b9241 kcontrol/xinerama/kcmxinerama.cpp a456b2c kcontrol/xinerama/test_kcm_xinerama.cpp a358a2c kcontrol/xinerama/xinerama.desktop e8ce525 kcontrol/xinerama/xineramawidget.h 2c446a2 kcontrol/xinerama/xineramawidget.cpp df9cb2f kcontrol/xinerama/xineramawidget.ui 90ec4d4 kwin/geometry.cpp a414e26 kwin/manage.cpp c551eac kwin/options.h 9dc29cf kwin/options.cpp d496569 kwin/tabbox/tabbox.cpp 3051316 kwin/toplevel.cpp ffe7f0c kwin/workspace.cpp 69b4ecb Diff: http://git.reviewboard.kde.org/r/103756/diff/diff Testing --- Fullscreen: works Maximize: works Movment: works Placement: works Thanks, Martin Gräßlin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Just a little more help needed with QML and Data Engine
Ran things through the QT Creator debugger. Looks like it wasn't
connecting to my flickrviewsengine because the isvalid variable was false.
So I changed things up a bit. Decided to use the Time engine because
that's the one always used in examples. Still got the same error. Here's
my current code:
import Qt 4.7
import content
import QtWebKit 1.0
import org.kde.plasma.core 0.1 as PlasmaCore
Rectangle {
id: window
width: 360
height: 360
PlasmaCore.DataSource {
id: viewsSource
engine: flickrviewsengine
//connectedSources: [75] //may end up removing this line
and leaving in Component.line
interval: 0
Component.onCompleted: connectedSources = sources
onSourceAdded: connectSource(source)
}
PlasmaCore.DataSource {
id: timer
engine: time
interval: 0
Component.onCompleted: connectedSources = sources
onSourceAdded: connectSource(source)
}
property string currentGroup: timer.data[Local][Timezone]
///home/ermesa/bin/qml/plasmoids/flickrviews/testgrouprss
viewsSource.data[75][Group 75]
property bool loading: feedModel.status == XmlListModel.Loading
XmlListModel{
id:feedModel
source: window.currentGroup //viewsSource.data[75][Group 75]
query: /rsp/photos/photo
XmlRole { name: title; query: @title/string()}
}
Row {
width: 360
height: 43
Rectangle{
width: window.width; height: window.height
color: blue
Text {
id: testtext
text: qsTr(buttons will go here!)
}
}
}
Row {
x: 0
y: 43
width: 370
height: 317
Rectangle {
width: window.width/3+10; height: window.height
color: #efefef
ListView {
id: list
width: window.width/3; height: window.height
model: feedModel
delegate: ItemDelegate {}
highlight: Rectangle { color: lightgray }
highlightMoveSpeed: 999
}
}
Rectangle {
width: window.width/3*2
height: window.height
}
}
}
And here's the error:
KGlobal::locale::Warning your global KLocale is being recreated with a
valid main component instead of a fake component, this usually means you
tried to call i18n related functions before your main component was
created. You should not do that since it most likely will not work
TypeError: Result of expression 'timer.data[Local]' [undefined] is not an
object.
So I figure I need to solve the problem with the known working time engine
before I tackle what's wrong with mine. (I think it's because I added the
engine as root - it doesn't so up in my user's engine explorer - only in
root's)
--
Eric Mesa
http://www.ericsbinaryworld.com
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Re: train clock plasmoid fan
A Domingo, 22 de Janeiro de 2012 23:30:43 Marco você escreveu: On Thursday 17 September 2009 19:27:19 Riccardo Iaconelli wrote: hello,[...] I'll come back though. and will finish that damn train clock lies! Just to let you know that so many users are still waiting for your train clock :) Bye Marco Bye, -Riccardo hummm if some one wants to adapt the one i did for my silly timetogo app :D I will send the qml, the artwork is still based on the original artwork I did for the train clock _ oxygen guy, I make the pretty pictures ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
