Re: Write to AppletGlobals in plasma-desktop-appletsrc with Javascript
On April 25, 2010, Antony Loebs wrote:
> On Sun, Apr 25, 2010 at 3:08 PM, Aaron J. Seigo wrote:
> > currently there isn't any way to do this in 4.4. in 4.5 you will be able
> >
> > to use read/writeGlobalConfig to do so.
> >
> > in any case, the # of rows of the pager is being moved to the window
> > manager where it really belongs (to follow the internal layout of virtual
> > desktops / viewports according to the WM), so even in this case it
> > probably won't work for very much longer.
>
> Pity. Would it be possible to brute-force it some other way? For example,
> at the beginning of the script, to do something like:
> ---
> var fh = fopen("~/.kde/share/config/plasma-desktop-appletsrc", 3)
> fwrite(fh, "[AppletGlobals][plasma_applet_pager]\nrows=1");
> fclose(fh);
> ---
> (This doesn't work, btw, since plasma-desktop complains about fopen, but
> it's just to make my meaning clear.)
the scripting API does not allow opening of random files. all the access goes
through existing plasma API to ensure that it's always correct and in sync
with what the plasma based application expects. one of the requirements of the
scripting API is that it produces results that work, and so there are some
constraints such as this one.
> Also, on a somewhat related note, I've discovered that some applets start
> too quickly. :)
it's not that they are starting too quickly, it's that they haven't
implemented Plasmsa::Applet::configChanged(). we've gone through and fixed the
ones in svn for 4.5 (with a few outstanding ones left, e.g. folderview.. but
those will also get done..)
--
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
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [Kde-pim] New application: Videocatcher
> > Yes. What Videocatcher does is not the same but very similar to > > Akregator and since it doesn't even have it's own media playback > > functionality I considered it to be more kde-pim than kde-plasma. If > > people disagree I can move it to plasma... > > ... or kdenetwork. True, kdenetwork might be best. Jonas ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [Kde-pim] New application: Videocatcher
On Sunday 25 April 2010, Jonas Müller wrote: > > Why did you send your mail to kde-pim? Because of Akregator? Yeah, that was also my first thought. Even Akregator does not really belong into kdepim IMO, but as long as Kontact does not have a stable public interface for adding components it will have to stay there. > Yes. What Videocatcher does is not the same but very similar to > Akregator and since it doesn't even have it's own media playback > functionality I considered it to be more kde-pim than kde-plasma. If > people disagree I can move it to plasma... ... or kdenetwork. Regards, Ingo 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: Review Request: Expose KStatusNotifierItem menus on DBus
> On 2010-04-23 18:34:28, Marco Martin wrote: > > is still a work in progress, but as soon the dependency from qtdbusmenu is > > sorted out i think it should go in I discussed moving dbusmenu-qt to kdesupport on IRC with Aaron and a few others. In the end it we agreed it was simpler to leave it on gitorious, since we already have dependencies hosted there (phonon for example). - Aurélien --- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/3787/#review5191 --- On 2010-04-23 16:15:06, Aurélien Gâteau wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > http://reviewboard.kde.org/r/3787/ > --- > > (Updated 2010-04-23 16:15:06) > > > Review request for kdelibs and Plasma. > > > Summary > --- > > This patch makes KStatusNotifierItem expose its menu on DBus, making it > possible for the StatusNotifierItem visualization to control the rendering of > the menu. It adds a dependency on dbusmenu-qt, which can be found here: > > http://people.canonical.com/~agateau/dbusmenu/index.html > > For now icon names are not exposed because it needs QIcon::name(). This > method should be in Qt 4.7, but was not included in the beta. > > > Diffs > - > > trunk/KDE/kdelibs/CMakeLists.txt 1115427 > trunk/KDE/kdelibs/cmake/modules/CMakeLists.txt 1115427 > trunk/KDE/kdelibs/cmake/modules/FindDBusMenuQt.cmake PRE-CREATION > trunk/KDE/kdelibs/kdeui/CMakeLists.txt 1115427 > trunk/KDE/kdelibs/kdeui/notifications/kstatusnotifieritem.cpp 1115427 > trunk/KDE/kdelibs/kdeui/notifications/kstatusnotifieritemdbus_p.h 1115427 > trunk/KDE/kdelibs/kdeui/notifications/kstatusnotifieritemdbus_p.cpp 1115427 > trunk/KDE/kdelibs/kdeui/notifications/kstatusnotifieritemprivate_p.h > 1115427 > trunk/KDE/kdelibs/kdeui/notifications/org.ayatana.dbusmenu.xml PRE-CREATION > trunk/KDE/kdelibs/kdeui/notifications/org.kde.StatusNotifierItem.xml > 1115427 > > Diff: http://reviewboard.kde.org/r/3787/diff > > > Testing > --- > > After applying the patch you should be able to list the menu of a > KSNI-enabled application from DBus. This can be checked with this command: > > dbus-send --print-reply --dest=org.kde.StatusNotifierItem-$PID-$N /MenuBar > org.ayatana.dbusmenu.GetChildren int32:0 array:string: > > > Thanks, > > Aurélien > > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Review Request: [Quicklaunch] Refactoring of the Quicklaunch applet
--- This is an automatically generated e-mail. To reply, visit: http://reviewboard.kde.org/r/3786/#review5225 --- - Lukas On 2010-04-23 19:08:34, Ingomar Wesp wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > http://reviewboard.kde.org/r/3786/ > --- > > (Updated 2010-04-23 19:08:34) > > > Review request for Plasma. > > > Summary > --- > > This is my proposed patch for the refactored quicklaunch applet as discussed > in review request http://reviewboard.kde.org/r/3358/ and on the ML a while > ago. Sorry that it took so long... > > Summary of changes: > - Refactored the quicklaunch applet, so that the applet, > icon grid widget and icon grid layout are split into > separate classes all living in a newly created namespace. > > - Improved drag & drop behaviour (it is not possible to drop items > in the popup dialog) and drag & drop markers. > > - Icons are now moved to/from the dialog explicitly instead of > asking the user to specify the number of the icons that are > shown in the primary area. > > - Icon size is now determined automatically based on the > available space, hard-coded minimum and maximum bounds and > the number of rows (or columns) set by the user. This is done > in a custom layout that is no longer based on > QGraphicsGridLayout. > > - When all icons are removed from an icon area, a placeholder > icon is displayed. > > As this patch changes the configuration keys used, it also incorporates code > for migrating older config keys. > > Unfortunately, using svn diff with files that have been "svn move"d appears > to yield broken diffs, so the patch here does not reflect the history for > files that are based on renamed files (quicklaunch.*, quicklaunchicon.*), but > I'll make sure that the history is preserved when committing (if this gets a > "ship it", that is). > > Please give it a spin and tell me what you think. > > > This addresses bugs 206382, 206912, 214463, 225011, and 233914. > https://bugs.kde.org/show_bug.cgi?id=206382 > https://bugs.kde.org/show_bug.cgi?id=206912 > https://bugs.kde.org/show_bug.cgi?id=214463 > https://bugs.kde.org/show_bug.cgi?id=225011 > https://bugs.kde.org/show_bug.cgi?id=233914 > > > Diffs > - > > > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/CMakeLists.txt > 1117710 > > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/QuicklaunchLayout.h > 1117710 > > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/QuicklaunchLayout.cpp > 1117710 > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/icongrid.h > PRE-CREATION > > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/icongrid.cpp > PRE-CREATION > > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/icongridlayout.h > PRE-CREATION > > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/icongridlayout.cpp > PRE-CREATION > > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/quicklaunch.h > PRE-CREATION > > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/quicklaunch.cpp > PRE-CREATION > > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/quicklaunchApplet.h > 1117710 > > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/quicklaunchApplet.cpp > 1117710 > > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/quicklaunchConfig.ui > 1117710 > > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/quicklaunchIcon.h > 1117710 > > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/quicklaunchIcon.cpp > 1117710 > > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/quicklaunchicon.h > PRE-CREATION > > /trunk/KDE/kdebase/workspace/plasma/generic/applets/quicklaunch/quicklaunchicon.cpp > PRE-CREATION > > Diff: http://reviewboard.kde.org/r/3786/diff > > > Testing > --- > > > Thanks, > > Ingomar > > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Write to AppletGlobals in plasma-desktop-appletsrc with Javascript
On Sun, Apr 25, 2010 at 3:08 PM, Aaron J. Seigo wrote:
> currently there isn't any way to do this in 4.4. in 4.5 you will be able
> to use read/writeGlobalConfig to do so.
>
> in any case, the # of rows of the pager is being moved to the window
> manager where it really belongs (to follow the internal layout of virtual
> desktops / viewports according to the WM), so even in this case it probably
> won't work for very much longer.
>
Pity. Would it be possible to brute-force it some other way? For example, at
the beginning of the script, to do something like:
---
var fh = fopen("~/.kde/share/config/plasma-desktop-appletsrc", 3)
fwrite(fh, "[AppletGlobals][plasma_applet_pager]\nrows=1");
fclose(fh);
---
(This doesn't work, btw, since plasma-desktop complains about fopen, but
it's just to make my meaning clear.)
Also, on a somewhat related note, I've discovered that some applets start
too quickly. :) For example, take the example of the quicklaunch applet. In
the script, I have:
---
qlaunch = panel.addWidget("quicklaunch");
qlaunch.writeConfig("iconSize", "24");
qlaunch.writeConfig("iconUrls",
"file:///usr/share/applications/firefox.desktop");
---
However, when quicklaunch starts, it displays the default Konqueror,
Dolphin, and Kopete icons at size 16. If I go back and insert the lines into
plasma-desktop-appletsrc, it works. Additionally, for some applets
(Lancelot, yaWP), I don't have to even edit anything; if I just restart
plasma-desktop, they then display correctly. From this I conclude that it's
a matter of the applets trying to read the configuration file before their
configurations are written. Any suggestions on how to overcome this; perhaps
a way to write the configuration first, and then start the applet?
Thanks!
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Re: New application: Videocatcher
> What about an akonadi-based system to handle podcasts and video > podcasts? Then dataengines could be provided to allow plasma to make > use of it, and other applications (like Amarok, as an example) could > also integrate it. That way we don't need a bunch of different > implementations doing the same basic thing. There was a Google Summer of Code project that tried to do that for normal RSS feeds but it never was completely finished: http://techbase.kde.org/Projects/PIM/RSS_framework_for_Akonadi Unfortunately I know nothing about programming in Akonadi but I hope that Videocatcher will be able to use a "KRSS extended for pod/videocasts" at some point. Jonas ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: New application: Videocatcher
> I think that this might be something useful inside Plasma Media Center > project.. Anyway it's a bit early probably, but i'd like to see what we can > take from your project. Would be great if it can be used in Plasma Media Center. Please tell me if and how I can help with that. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Write to AppletGlobals in plasma-desktop-appletsrc with Javascript
On April 25, 2010, Antony Loebs wrote: > So what would the command be to write that to plasma-desktop-appletsrc? > Thanks! currently there isn't any way to do this in 4.4. in 4.5 you will be able to use read/writeGlobalConfig to do so. in any case, the # of rows of the pager is being moved to the window manager where it really belongs (to follow the internal layout of virtual desktops / viewports according to the WM), so even in this case it probably won't work for very much longer. -- 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 ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Write to AppletGlobals in plasma-desktop-appletsrc with Javascript
I've been messing around with ways to script the appearance of KDE and found
Kubuntu's
01-kubuntu-default-setup.js script, which (quite nicely) shows me how to do
what I want. However, I've run into a problem with the pager; I would like
the default to be one row, instead of two. I dutifully added:
---
pager = panel.addWidget("pager");
pager.writeConfig("rows", "1");
---
to the script, but this didn't work. On closer inspection, I found that the
pager looks for something like this:
---
[AppletGlobals][plasma_applet_pager]
rows=1
---
So what would the command be to write that to plasma-desktop-appletsrc?
Thanks!
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Re: New application: Videocatcher
On Sun, Apr 25, 2010 at 1:15 PM, Alessandro Diaferia wrote: > > > 2010/4/25 Jonas Müller >> >> > A Diumenge, 25 d'abril de 2010, Jonas Müller va escriure: >> > > Hi all >> > > I have recently committed a new application to playground/pim. >> > >> > Why pim? >> >> Because Videocatcher does very similar things to Akregator. Basically it's >> a >> feedreader with download capabilities. I only play back media by calling >> external programs so it has no multimedia functionality at all. it seems >> to me >> it should be in PIM, but maybe it shouldn't? >> >> > Basically my mail is just to tell you, keep working on it and why pim? >> > Seems more like multimedia. >> >> Thanks for the feedback. >> >> Jonas >> >> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to >> >> unsubscribe << > > I think that this might be something useful inside Plasma Media Center > project.. Anyway it's a bit early probably, but i'd like to see what we can > take from your project. What about an akonadi-based system to handle podcasts and video podcasts? Then dataengines could be provided to allow plasma to make use of it, and other applications (like Amarok, as an example) could also integrate it. That way we don't need a bunch of different implementations doing the same basic thing. -Todd ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: New application: Videocatcher
2010/4/25 Jonas Müller > > A Diumenge, 25 d'abril de 2010, Jonas Müller va escriure: > > > Hi all > > > I have recently committed a new application to playground/pim. > > > > Why pim? > > Because Videocatcher does very similar things to Akregator. Basically it's > a > feedreader with download capabilities. I only play back media by calling > external programs so it has no multimedia functionality at all. it seems to > me > it should be in PIM, but maybe it shouldn't? > > > Basically my mail is just to tell you, keep working on it and why pim? > > Seems more like multimedia. > > Thanks for the feedback. > > Jonas > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to > unsubscribe << > I think that this might be something useful inside Plasma Media Center project.. Anyway it's a bit early probably, but i'd like to see what we can take from your project. Cheers -- Alessandro Diaferia KDE Developer KDE e.V. member ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [Kde-pim] New application: Videocatcher
> Why did you send your mail to kde-pim? Because of Akregator? Yes. What Videocatcher does is not the same but very similar to Akregator and since it doesn't even have it's own media playback functionality I considered it to be more kde-pim than kde-plasma. If people disagree I can move it to plasma... > Personally, I think you should turn you app into a Plasma applet that > integrates well into plasma-mediacenter and also into "normal" Plasma > panels as icon (eg. by forking QuickAccess with its nice popup-based > navigation). As vodcasts are often quite big in size (esp. if they are HD) > a proper vodcast client has to be persistent anyway. Thats a great idea. Personally I thought I would add different ways of accessing the data (such as through plasma applets) once KRSS might be done. But first I wanted to make a plain videocast client that works (tm). > Markus > > PS: I took the liberty to add plasma-devel as recipient. Thanks! Jonas ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [Kde-pim] New application: Videocatcher
Why did you send your mail to kde-pim? Because of Akregator? Personally, I think you should turn you app into a Plasma applet that integrates well into plasma-mediacenter and also into "normal" Plasma panels as icon (eg. by forking QuickAccess with its nice popup-based navigation). As vodcasts are often quite big in size (esp. if they are HD) a proper vodcast client has to be persistent anyway. Markus PS: I took the liberty to add plasma-devel as recipient. Am Sonntag 25 April 2010 15:40:19 schrieb Jonas Müller: > Hi all > I have recently committed a new application to playground/pim. It's called > Videocatcher and is an Internet TV application (like a podcast client but > for videos). It is still far from done but should be in a usable state. > > Currently Videocatcher makes it possible to subscribe to video RSS/ATOM > feeds and easily download and watch the videos. It works as a podcast > client as well, but I am only really focusing on video since Amarok has > podcast functionality. If anyone would like to see a standalone podcast > client feel free to tell me. > > The idea is to create a videocast client which is lightweight and > integrated into KDE. Lightweight in the sense of responsive and using few > resources, but also that it does not try to do things that other programs > can do better. For example by using external media players. > > I am wondering if there is anyone here who might be interested a videocast > client for KDE or have any ideas about the direction it should be going. Is > it a waste of time? Should it be a podcast client as well? Should it be > called VideoKatcher? > > Any ideas or feedback are greatly appreciated! > > Videocatcher is also available from kde-apps.org: http://kde- > apps.org/content/show.php/Videocatcher?content=121556 > > Regards, > Jonas > ___ > KDE PIM mailing list kde-...@kde.org > https://mail.kde.org/mailman/listinfo/kde-pim > KDE PIM home page at http://pim.kde.org/ ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
