Q: PlasmaDesktopScripting : Sizing widget PopUps in Panels, best methods of handling some tasks
(AFAICT, 'plasma-devel' is the only mailing list this
question might apply, but please let me know if i should
pursue assistance somewhere else)
I'm attempting to construct a default new-user setup via:
$(kde4-config --install data)/plasma-desktop/init/99-SITEDEFAULT.js
that loads a panel template from .../plasma/layout-templates/site-layout/...
(first wiping all existing panels&activities created by 00-Default.
This seems the best way to not conflict with my distribution's
(Debian Wheezy) ownership of files)
I'm not really wanting to use a "skel" homedir splatting technique
(populating ~/.kde/... with hardcoded setups) as this leads to
inconsistencies with screensizes, etc, so PlasmaDesktop Scripting
looked to be a great tool for managing user account configurations.
Q1: Is it possible in PlasmaDesktopScripting (PDS) to set the size
(HxW) of the Popup for a widget loaded in the panel?
e.g.
var clock = panel.addWidget("digital-clock")
clock.writeConfig("dateStyle", "4") // ISO date
I find the default Popup size displaying the calendar and
"events/holidays" to be too small (both height and width).
writeConfig() and writeGlobalConfig() create Group labels not used
for the PopUp group labels. (addition of [Configuration] and [AppletGlobals]'
that aren't in the '[PopupApplet]' label)
Any way to do that in the plasma-desktop/init/* + plasma/layout-templates/*
toolkit?
Q2: How best to handle situations where a PDS interface is only partially
managed, something like:
var pager = panel.addWidget("pager")
Where I want to set pager to 2x2. Even the info from the System
Adminstrator PDS document implies that:
pager.writeGlobalConfig("rows", "2")
Should set the rows to 2, but the default pager is only 1 desktop (1x1)
There seems to be no interface to change this, and what makes it
worse is that this seems to only be a visual interface to properties
managed by KWin (kwinrc [Desktops] keys 'Number' and 'Rows')
Also, for 'kickoff', i'd like to run through my ".desktop" locator function
(finding various apps by alternate names, to generalize our deployment
of laptops and desktops that find things in different places or
by install), building a Favorite_URLs and then stuff that into
'kickoff's Favorites listing. but PDS seems to only manage
groups/keys within 'plasma-desktop-appletsrc', and kickoff uses
a global .kickoffrc (ignoring what's set in p-d-appletsrc).
There seems to be no generalized "kwriteconfig/kreadconfig" type
interface in PDS (which would be great), so best i can guess i'd
have to script this stuff up some other way.
So, my question would be how best to leverage the existing PDS
layout-templates + plasma-desktop/init structure with some auxiliary
tools?
Thanks,
--stephen
--
Stephen Dowdy - Systems Administrator - NCAR/RAL
303.497.2869 - sdo...@ucar.edu- http://www.ral.ucar.edu/~sdowdy/
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Re: module not found with qtextracomponents
On Tuesday, 4. June 2013. 23.35.42 Heena Mahour wrote: > Hi, using plasmoidviewer on using import org.kde.qextracomponents 0.1 I am > getting error .:module org.kde.qextracomponents is not found Isn't it missing a 't' - org.kde.qtextracomponents Cheerio, Ivan -- Progress isn't made by early risers. It's made by lazy men trying to find easier ways to do something. -- Robert Heinlein ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
module not found with qtextracomponents
Hi, using plasmoidviewer on using import org.kde.qextracomponents 0.1 I am getting error .:module org.kde.qextracomponents is not found .Please suggest something -- -Heena Season of kde'12 participant Delhi College of Engineering(COE),India http://about.me/heena.mahour http://heenamahour.blogspot.in ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: kdeobservatory seems to be missing a qwt min version check
It used to work on the SVN, needs to be ported to Git. /me downloading it to see if I can revive it. On Tue, Jun 4, 2013 at 2:22 PM, Albert Astals Cid wrote: > El Dilluns, 3 de juny de 2013, a les 21:22:42, Sandro Andrade va escriure: > > Hi there, > > > > That's actually intended to be moved to unmaintained, sorry for > > haven't done it yet, I'm in the last months of my thesis :( - or maybe > > > > :) > > > > Not sure if I can do that at this time in release schedule. I can fix > > it to use Qwt 6.1 or fully move it to maintained. > > It's unmaintained, but does it work? We ship lots of unmaintained stuff > that > "works". So if fixing it for Qwt 6.1 makes it work I'd just keep it and > try to > find a new maintainer. > > Cheers, > Albert > > > > > What do you guys prefer ? > > -- > > Sandro > > > > On Mon, Jun 3, 2013 at 5:22 PM, Ben Cooksley wrote: > > > On Tue, Jun 4, 2013 at 8:09 AM, Albert Astals Cid > wrote: > > >> Hi guys, can anyone please have a look at > > >> kdeplasma-addons/applets/kdeobservatory and make sure it requires the > qwt > > >> min version it needs? > > >> > > >> The build is currently failing at build.kde.org (probably a too old > qwt > > >> installed) instead of just skipping the applet from being built. > > > > > > I suspect it is actually a case of a too new Qwt being installed. > > > We recently upgraded from Qwt 6.0 to 6.1, which was necessary to allow > > > the smokeqt bindings to compile successfully. > > > > > >> http://build.kde.org/view/All/job/kdeplasma-addons_master/212/console > > >> > > >> Cheers, > > >> > > >> Albert > > > > > > Regards, > > > Ben > > > > > >> P.S: I'm *not* subscribed to plasma-devel so CC me if you want to > keep me > > >> in the loop > > >> ___ > > >> Plasma-devel mailing list > > >> Plasma-devel@kde.org > > >> https://mail.kde.org/mailman/listinfo/plasma-devel > ___ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Fighting those Crash reports
On Tuesday, 2013-06-04, Martin Gräßlin wrote: > Hi all, > > over the last few days I worked through the crash reports from Plasma. As > discussed a large number got resolved as downstream and I tried to mark > quite a lot as duplicate. Now we have ~100 open reports left. I just remembered something related to duplicates of crash reports. On my flight back from FOSDEM I got to set next to a QA engineer from Mozilla. He told me that one thing they do with crash reports is to evalute their number of occurences and other statistical data in order to prioritize actual analysis. I.e. a crash that gets lots of duplicates happens a lot, thus fixing it has the highest impact on user happiness. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring 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: kdeobservatory seems to be missing a qwt min version check
El Dilluns, 3 de juny de 2013, a les 21:22:42, Sandro Andrade va escriure: > Hi there, > > That's actually intended to be moved to unmaintained, sorry for > haven't done it yet, I'm in the last months of my thesis :( - or maybe > > :) > > Not sure if I can do that at this time in release schedule. I can fix > it to use Qwt 6.1 or fully move it to maintained. It's unmaintained, but does it work? We ship lots of unmaintained stuff that "works". So if fixing it for Qwt 6.1 makes it work I'd just keep it and try to find a new maintainer. Cheers, Albert > > What do you guys prefer ? > -- > Sandro > > On Mon, Jun 3, 2013 at 5:22 PM, Ben Cooksley wrote: > > On Tue, Jun 4, 2013 at 8:09 AM, Albert Astals Cid wrote: > >> Hi guys, can anyone please have a look at > >> kdeplasma-addons/applets/kdeobservatory and make sure it requires the qwt > >> min version it needs? > >> > >> The build is currently failing at build.kde.org (probably a too old qwt > >> installed) instead of just skipping the applet from being built. > > > > I suspect it is actually a case of a too new Qwt being installed. > > We recently upgraded from Qwt 6.0 to 6.1, which was necessary to allow > > the smokeqt bindings to compile successfully. > > > >> http://build.kde.org/view/All/job/kdeplasma-addons_master/212/console > >> > >> Cheers, > >> > >> Albert > > > > Regards, > > Ben > > > >> P.S: I'm *not* subscribed to plasma-devel so CC me if you want to keep me > >> in the loop > >> ___ > >> Plasma-devel mailing list > >> Plasma-devel@kde.org > >> https://mail.kde.org/mailman/listinfo/plasma-devel ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Fighting those Crash reports
On Tuesday, June 4, 2013 17:01:38 Martin Gräßlin wrote: > A possibility would be to have a few bug days, but I would prefer if some > plasma devs would go through them and directly fix the reproducable crashes. > Or that we encourage new devs to come in but are around to help. > > What does the Plasma world think about that? Bug days would be great. It lets us schedule work that is more fun to do together and ensures that some of the core devs who can answer questions others may have to spend time researching are around. I'm in! -- Aaron J. Seigo 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
Fighting those Crash reports
Hi all, over the last few days I worked through the crash reports from Plasma. As discussed a large number got resolved as downstream and I tried to mark quite a lot as duplicate. Now we have ~100 open reports left. I think this is now a number where we could start looking properly into them. Trying to reproduce them, confirming them if they are reproducable, if not ask for steps how to reproduce. A possibility would be to have a few bug days, but I would prefer if some plasma devs would go through them and directly fix the reproducable crashes. Or that we encourage new devs to come in but are around to help. What does the Plasma world think about that? 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
