Re: RFC: Remove Opacity from Alt+F3 menu
On Thursday, August 18, 2011 19:20:08 Martin Gräßlin wrote: just an idea I had today: do we really need the opacity menu in the Alt+F3 menu? That menu is really hard to use, because it's too long, yes. Also the submenus aren't great, because they require quite some patience to navigate, especially with touchpads. IMO the submenu could go, for peaking under the current window (the one usecase I can see) a titlebar wheelevent, even if a bit hidden, is way more ergonomic. 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: RFC: Remove Opacity from Alt+F3 menu
On Friday 19 August 2011 10:08:40 Sebastian Kügler wrote: a titlebar wheelevent, even if a bit hidden, is way more ergonomic. Not every input device has a wheel. My stylus has all three mouse buttons, but no wheel. If you remove the menu entries, at least make sure you have global shortcuts for changing transparency quickly (+/- by 20%, set to opaque), so that I can assign gestures to those operations. Otherwise, I would be unable to temporarily (and quickly) change the opacity. As a user with limited screen space, I pretty often use transparency to see through windows, which avoids the need to switch between them constantly. Christoph Feck (kdepepo) ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
analog clock widget
hi,i have problem with analog clock in opensuse kde 4.4.4 release 2.when i put it on desktop it desnt appear,but when i right click where i put it on desktop i can change the setting and... myloptop is vaio F116FG and my graphic card is Nvidia GT330M what should i do??thanks so much___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: RFC: Remove Opacity from Alt+F3 menu
Am Fri, 19 Aug 2011 10:19:24 +0200 schrieb Christoph Feck christ...@maxiom.de: If you remove the menu entries, at least make sure you have global shortcuts for changing transparency quickly (+/- by 20%, set to opaque), so that I can assign gestures to those operations. Leaving the generally valid shortcut demand aside: what about adding it to the Alt+l/m/rmb actions (not only wheel) (ie. react to mouse/pen up/down, left/right moves) Should be superior to your current situation and maybe even shortcuts? Cheers, Thomas ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: analog clock widget
On Thursday, August 18, 2011 16:00:38 arash a wrote: hi,i have problem with analog clock in opensuse kde 4.4.4 release 2.when i put it on desktop it desnt appear,but when i right click where i put it on desktop i can change the setting and... myloptop is vaio F116FG and my graphic card is Nvidia GT330M what should i do??thanks so much upgrade to a newer version of Plasma Desktop :) 4.4.4 is quite old and this issue has been fixed in later releases. also, you may find better user support on e.g. forums.kde.org. this is a development mailing list. while we don't mind some user level questions now and again on this list, the focus is not user support and so you may not get the best answers or response times. i recommend things like the forums for that. cheers :) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks 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: RFC: Remove Opacity from Alt+F3 menu
A Sexta, 19 de Agosto de 2011 01:15:29 David você escreveu: I don't know why do you want to break every single thing. Even the most little ones. Is converting user's experience into a nightmare your passion? Nope but we tend to abuse on the amount of things we present to a user at a glance, wen we do this we pass an image of steep learning curve, and we make our software less atractive, specialy on this new world of 145 caracter atention span. Im not saying we should go the gnome way and simple remove the features. but we should hide the 1% use features into a place were peoplethst do care will find it...in this case to me I would put an option to activate this feature or teach a shortcut to it in kwin configure options... as for converting user's experience into a nightmare your passion? I like to belive we try the oposite making it simpler for 90% of our users Me notes we can put yeat more options/features at the root level of any menu and I'm sure we will find users for them (that the holle point of the feature any way) but we will end up with uterly unusable UI's like that. Some rules of thumb any list should not have more items than our brains short memory list aka (7 +- 2) depends on mother language aka 5. this is not valid for any app ofcourse if you want to send a message that your app is powerfull and can do many things maybe showing a bit clutered with features UI is a good thing... For everything else simple is better. and since kwin basic options is for everyone simple is defenitivly better. PS sory for typos -- Nuno Pinheiro | nuno.pinhe...@kdab.com | UI Designer Klarälvdalens Datakonsult AB, a KDAB Group company KDAB - Qt Experts - Platform-independent software solutions ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Review Request: Plasmate:migrate timeline.cpp from Q classes to K classes
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/102027/#review5827 --- Ship it! - Aaron J. On Aug. 18, 2011, 6:09 p.m., Giorgos Tsiapaliwkas wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/102027/ --- (Updated Aug. 18, 2011, 6:09 p.m.) Review request for Plasma. Summary --- hello, the patch migrates the timeline.cpp from the Q classes to K classes. Also adds a KMessageBox::information in the newsavepoint(),in order to inform the user that he can't create a new save point without any changes being made Diffs - savesystem/timeline.cpp 2ed3ac2 Diff: http://git.reviewboard.kde.org/r/102027/diff Testing --- no issues. Thanks, Giorgos ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: analog clock widget
This is a known bug in that kde version. The bug has been fixed with kde 4.6 Have a nice day Beat Wolf Am Donnerstag, 18. August 2011, 17:00:38 schrieb arash a: hi,i have problem with analog clock in opensuse kde 4.4.4 release 2.when i put it on desktop it desnt appear,but when i right click where i put it on desktop i can change the setting and... myloptop is vaio F116FG and my graphic card is Nvidia GT330M what should i do??thanks so much ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: RFC: Remove Opacity from Alt+F3 menu
On Thursday, August 18, 2011 18:51:30 Eric Mesa wrote: I use it daily for my Konversation window can you set a window rule instead and achieve the same thing? -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks 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: RFC: Remove Opacity from Alt+F3 menu
On Friday, August 19, 2011 02:15:29 David wrote: I don't know why do you want to break every single thing. Even the most little ones. Is converting user's experience into a nightmareyour passion? i won't repeat what Martin already said, though what he said is 100% correct. i just want to add this: if i see another email like this from you on this list, you will be unsubscribed from the list and your email put on the moderation list. when i say an email like this i mean one that is: * free of useful content * uses insults * does not approach the issue in a constructive manner this is a constructive innovation zone, and i have no compunctions removing those who would turn it into something less. i do hope you continue to participate, but on more positive terms. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks 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: Re: GLES again
On Thursday 18 August 2011 14:38:49 Sebastian Kügler wrote: On Wednesday, August 17, 2011 17:29:28 Martin Gräßlin wrote: On Wednesday 17 August 2011 16:56:36 Sebastian Kügler wrote: Is there a workaround for this, or do hardware or driver simply not allow using GLES on this machine? try the attached patch - it should disable the check for GLES. Making shaders work for limited GLSL is the top item on my TODO list :-) Packages from master are being built, so we can test this at runtime. This patch seems to help, kwin runs happily on the ExoPC using OpenGL-ES. I'm still working on getting it properly packaged, but the bigger roadblocks seem to be behind us. :) I'll let you know once the packages are ready. Right now, KDE:Active is kinda broken due to this transition. Patch pushed to 4.7 and master 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: GLES again - Nailed.
On Friday, August 19, 2011 21:33:38 Martin Gräßlin wrote: I'll let you know once the packages are ready. Right now, KDE:Active is kinda broken due to this transition. Patch pushed to 4.7 and master Muchos gracias! Master packages are updated in the KDE:Active:Devel repository, KDE:Active uses 4.7, until we decide to switch over to it by default in Active. http://vizzzion.org/blog/2011/08/plasma-active-on-opengl-es/ http://vizzzion.org/blog/2011/08/kdeactivedevel-introduced/ Since I've just written this down, and it constitutes related information. :) Thanks, -- 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: Review Request: Rework KMix DBus API and add KMix plasma dataengine
---
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/6587/#review10358
---
Hi,
I was just trying to do the same thing with kmix and wasted ~6 hours on that
(or even more) just to find that is was already here but never committed. So
how are we on this? Can this be committed?
Regards,
Mark
- Mark
On April 7, 2011, 8:40 a.m., Igor Poboiko wrote:
---
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/6587/
---
(Updated April 7, 2011, 8:40 a.m.)
Review request for Plasma and Diego Casella.
Summary
---
This patch reworks KMix DBus API and adds a plasma dataengine+service as a
frontend to information provided by DBus.
New DBus structure is:
- /Mixers
used to get some global information, such as available mixers list and global
master mixer
- /Mixers/MIXER_ID
used to get information about mixer with id=MIXER_ID. It provides such
information as list of available controls, name of this mixer, id, etc
- /Mixers/MIXER_ID/CONTROL_ID
used to get and set information about control. Such information as volume
level, mute, name of control, etc.
It also adds a DBus signals which are emitted when new mixer/control appears,
or volume level changes.
It also splits all dbus-related code to separate class,
DBus{KMix,Mixer,Control}Wrapper.
The Plasma Dataengine:
By default, the only available source is KMix. It provides information
global information about KMix: is KMix running, and list of available mixers.
(its IDs)
Source for every mixer is called by it's ID (for example,
ALSA::HDA_Intel:1). This source provides such information about current
Mixer as: it's readable name, is it opened, its balance and list of available
controls. It also adds basic sources for every control, which provides only
information about its readable name
Sources for controls are called by 'MIXER_ID/CONTROL_ID' (for example,
ALSA::HDA_Intel:1/Master:0). If you request this source, it will provide
such information as its readable name, is it muted and its volume level
(which are updates automatically, using DBus signals).
There is a service available for controls sources. It provides such methods
as setVolume() and setMute().
It doesn't close bug 171287, but it becomes one step closer to its solving :)
And, I'm not very familiar with CMake, but it would be great idea to make
plasma part optional.
This addresses bug 171287.
https://bugs.kde.org/show_bug.cgi?id=171287
Diffs
-
/trunk/KDE/kdemultimedia/kmix/core/mixdevice.h 1225808
/trunk/KDE/kdemultimedia/kmix/apps/kmix.cpp 1225808
/trunk/KDE/kdemultimedia/kmix/CMakeLists.txt 1225808
/trunk/KDE/kdemultimedia/kmix/core/mixdevice.cpp 1225808
/trunk/KDE/kdemultimedia/kmix/core/mixer.h 1225808
/trunk/KDE/kdemultimedia/kmix/core/mixer.cpp 1225808
/trunk/KDE/kdemultimedia/kmix/dbus/dbuscontrolwrapper.h PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/dbus/dbuscontrolwrapper.cpp PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/dbus/dbusmixerwrapper.h PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/dbus/dbusmixerwrapper.cpp PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/dbus/dbusmixsetwrapper.h PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/dbus/dbusmixsetwrapper.cpp PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/dbus/org.kde.kmix.control.xml PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/dbus/org.kde.kmix.mixer.xml PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/dbus/org.kde.kmix.mixset.xml PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/gui/kmixdockwidget.cpp 1225808
/trunk/KDE/kdemultimedia/kmix/plasma/CMakeLists.txt PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/plasma/engine/CMakeLists.txt PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/plasma/engine/mixer.operations PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/plasma/engine/mixerengine.h PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/plasma/engine/mixerengine.cpp PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/plasma/engine/mixerservice.h PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/plasma/engine/mixerservice.cpp PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/plasma/engine/plasma-engine-mixer.desktop
PRE-CREATION
/trunk/KDE/kdemultimedia/kmix/tests/CMakeLists.txt 1225808
Diff: http://svn.reviewboard.kde.org/r/6587/diff
Testing
---
KMix from KDE SC 4.6.0 compiles ok with this patch, and patch applies to
current trunk.
Tested on system with one card and with ALSA backend, so I don't know is
plasma dataengine works correctly with plugging/unplugging mixers (but it
should).
All DBus methods/properties works fine, signals are emitted, volume can be
set using DBus methods.
Plasma
ServiceJob binding in javascript not working in KDE 4.7?
Hi Plasma World, I'm trying to run this example: https://projects.kde.org/projects/kde/kdeexamples/repository/revisions/master/entry/plasma/javascript/plasmoids/usingServices/ In spite of connectSource missing a time interval, but the service job seems also not works. It complains about Cannot call startOperationCall() unknown return type ServiceJob* register the type with qScriptRegisterMetaType()) Is this example outdated? What should I do if I want to use ServiceJob in javascript plasmoid? Regards, Xuetian 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
