plasma search and launch javasscripting
i am trying to scripting plasma to be like gnome2 gnome3 chrome os unity ,
i know that this could be sound bad but... i think that plasma can be what
unity is not ... anyway
:) i was trying to write chromeOS activity better
and i tried to do that with Search and Launch desktop layout
i was able to customize it but not the stripwidget
i tried to use the array but it did not work :S
///CHROMEOS ACTIVITY
var screenrect = screenGeometry(0) // get information about your screen h w
function chromeos(){
var activity = new Activity(sal)
activity.name = i18n(ChromeOs Activity)
activity.writeConfig(EnabledEntries,plasma-sal-bookmarks.desktop,plasma-sal-contacts.desktop,plasma-sal-multimedia.desktop,plasma-sal-internet.desktop,plasma-sal-graphics.desktop,plasma-sal-games.desktop,plasma-sal-office.desktop)
activity.wallpaperPlugin = image
activity.wallpaperMode = SingleImage
activity.currentConfigGroup = Array(Wallpaper, image)
activity.writeConfig(wallpaper, nowardev-chromeos)
activity.writeConfig(previewPlugins,imagethumbnail,jpegthumbnail,kffmpegthumbnailer)
activity.reloadConfig()
activity.currentConfigGroup = new Array('stripwidget')
activity.currentConfigGroup = new Array('favourite-0')
activity.writeConfig(url,/usr/share/applications/kde4/dolphin.desktop)
}
chromeos()
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Re: plasma search and launch javasscripting
On Friday, February 1, 2013 12:48:17 Nowardev-Team wrote:
activity.currentConfigGroup = new Array('stripwidget')
activity.currentConfigGroup = new Array('favourite-0')
this should be:
activity.currentConfigGroup = ['stripwidget', 'favourite-0']
and then write your settings.
p.s. i also noticed that in configChanged, the strip widget was not getting
updated, so i fixed that in master as well.
--
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
PW2 planning: one shell to rule them all
hi .. i started a wiki page for the one shell to rule them all feature: http://community.kde.org/Plasma/shellswitching feedback, edits, input, ideas, etc welcome/needed. we'll go over this and more at upcoming meetings, and to give us a head start i'm writing up things we've discussed in the past. -- 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
Re: PW2 planning: one shell to rule them all
On Friday 01 February 2013, Aaron J. Seigo wrote: hi .. i started a wiki page for the one shell to rule them all feature: http://community.kde.org/Plasma/shellswitching feedback, edits, input, ideas, etc welcome/needed. we'll go over this and more at upcoming meetings, and to give us a head start i'm writing up things we've discussed in the past. i added a description of the test shell there is in the future plasma- frameworks repository. is intended to be pretty much a testbed for libplasma features (to unbreak them one by one) but if kept clean can give birth to a full shell (by transplanting the needed pieces from plasma-device and plasma- desktop) this is what does right now: * loads a corona, restores the containments (or creates a default layout) that right now are a pure qobject tree * creates a view per screen (just with qdesktop widget) a View is in the shell, not in libplasma anymore and is a QQuickView subclass * the view loads in itself a qml file, coming from a package (right now org.kde.homescreen.desktop) that will become pretty much the workspace definition the idea for continuing is, when containments and applets will be again worsing scriptengines (and will load a real qml package), Containment will have a pointer to the qml package root element (just a qobject* is all is needed). When a containment gains a screen, the corona will assign the containment root item to the view, making it child of the view root item. this makes the containment graphics migrate scene (thing that hasn't been tested yet how much reliable, but we absolutely need it to work flawlessy) and witll be possible from the view qml even animate the transition, if needed by the workspace. Cheers, Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Review Request 108699: fixes bug 309033
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/108699/ --- Review request for Plasma and Martin Gräßlin. Description --- 1. fixes bug 309033 2. replaces tabs with spaces 3. fixed the coding style This addresses bug 309033. http://bugs.kde.org/show_bug.cgi?id=309033 Diffs - plasmate/editors/metadata/metadata.ui b91a5b7 plasmate/editors/metadata/metadataeditor.h 4ce42ce plasmate/editors/metadata/metadataeditor.cpp 20c3a18 Diff: http://git.reviewboard.kde.org/r/108699/diff/ Testing --- Thanks, Giorgos Tsiapaliokas ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: PW2 planning: one shell to rule them all
On Friday, February 1, 2013 14:05:01 Marco Martin wrote: * the view loads in itself a qml file, coming from a package (right now org.kde.homescreen.desktop) that will become pretty much the workspace definition to expand on the package bit... this package will require the following: * which processes need to be running (e.g.: krunner) * default plasma-device layout * kwin configuration * other app config? * default lock screen + settings * default splash screen + settings * default logout dialog + settings in plasma-device, a Plasma/Generic package is loaded that has: * QML for setting up the default system * a plasma-default-layoutrc which loads the containments, etc. obviously this is not going to work for all targets. that's why we have the desktop scripting. for the plasma-device shell itself, it makes sense to use the desktop scripting API with some changes[1] imho. kwin will also need a strategy. the package could also include a kwin script to adjust settings, and i think that would be the most straight-forward, but as with the scripting this can only be used for first-time setup. when switching between workspaces, all affected config files will need to be backed up in a workspace-specific location for restoration when coming into another shell. this could be accomplished in a few ways, but perhaps the most straightfoward is simply copying the files around on disk. care will need to be taken during this process that the affect applications do not save to disk again before reloading the new config. we may also want to allow a layout to define whether or not the appletsrc file should be saved, or if the layout should be recreated fresh each time. in the case of PMC or a kiosk type environment, for instance, this may be desirable. i think we should avoid putting QML inside these packages, but rather they should only be scripts and config data. the reason for this is 2 fold: * it will make it easier on people making these shells who may not know QML * it will encourage and allow re-use of UI components by not including them in the shell layout package [1] http://community.kde.org/Plasma/DesktopScripting -- 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
Re: PW2 planning: one shell to rule them all
On Friday 01 February 2013, Aaron J. Seigo wrote: On Friday, February 1, 2013 14:05:01 Marco Martin wrote: * the view loads in itself a qml file, coming from a package (right now org.kde.homescreen.desktop) that will become pretty much the workspace definition to expand on the package bit... this package will require the following: * which processes need to be running (e.g.: krunner) * default plasma-device layout * kwin configuration * other app config? * default lock screen + settings * default splash screen + settings * default logout dialog + settings in plasma-device, a Plasma/Generic package is loaded that has: * QML for setting up the default system * a plasma-default-layoutrc which loads the containments, etc. right now the gereric is a subclass of plasmoid, to have mainscript and the other code,images etc subfolders.. probably this is not optimal in the long run, the homescreen may be a package type of its own, to have named content of all that above stuff... obviously this is not going to work for all targets. that's why we have the desktop scripting. the package may contains also desktop scripting js files... -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Review Request 108700: Make sure Menu.status is set to Closed when the menu closes itself
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/108700/ --- Review request for Plasma. Description --- Make sure Menu.status is set to Closed when the menu closes itself Diffs - plasma/declarativeimports/plasmacomponents/qmenu.h 00b73e47f1bbfe12aa1f6d5f7dfc8de7f7a0dfe1 plasma/declarativeimports/plasmacomponents/qmenu.cpp e91c365e401d751d42430eca36dea42f1258ee50 Diff: http://git.reviewboard.kde.org/r/108700/diff/ Testing --- Run attached testmenu.qml program. Without the patch, the text says Opened even after closing the menu. File Attachments Test program http://git.reviewboard.kde.org/media/uploaded/files/2013/02/01/testmenu.qml Thanks, Aurélien Gâteau ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: PW2 planning: one shell to rule them all
On Friday 01 February 2013 15:44:55 Aaron J. Seigo wrote: kwin will also need a strategy. the package could also include a kwin script to adjust settings, and i think that would be the most straight-forward, but as with the scripting this can only be used for first-time setup. I'm more thinking in the direction of a different kconfig file which we parse. Scripting inside KWin cannot cover everything (e.g. which effects to unload, which scripts to load). But a kconfig file contains all the information. 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 108700: Make sure Menu.status is set to Closed when the menu closes itself
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/108700/#review26519 --- one small issue to resolve, and then it can go in... plasma/declarativeimports/plasmacomponents/qmenu.cpp http://git.reviewboard.kde.org/r/108700/#comment20147 we try not to use slot* names (as they tend to drift over time from the signals connected and/or other uses), but rather state what the method does. so in this case perhaps menuClosing() or sth - Aaron J. Seigo On Feb. 1, 2013, 3:04 p.m., Aurélien Gâteau wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/108700/ --- (Updated Feb. 1, 2013, 3:04 p.m.) Review request for Plasma. Description --- Make sure Menu.status is set to Closed when the menu closes itself Diffs - plasma/declarativeimports/plasmacomponents/qmenu.h 00b73e47f1bbfe12aa1f6d5f7dfc8de7f7a0dfe1 plasma/declarativeimports/plasmacomponents/qmenu.cpp e91c365e401d751d42430eca36dea42f1258ee50 Diff: http://git.reviewboard.kde.org/r/108700/diff/ Testing --- Run attached testmenu.qml program. Without the patch, the text says Opened even after closing the menu. File Attachments Test program http://git.reviewboard.kde.org/media/uploaded/files/2013/02/01/testmenu.qml Thanks, Aurélien Gâteau ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Review Request 108706: bodega-server: Move authorization checks to the routes.js
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/108706/ --- Review request for Plasma. Description --- It is better for the bodega-server to check the authorization of the user on the routes.js. Diffs - server/lib/db/changeAccountDetails.js c57de02 server/lib/db/setpassword.js b6c59cf server/routes.js 8861b92 Diff: http://git.reviewboard.kde.org/r/108706/diff/ Testing --- Thanks, Antonis Tsiapaliokas ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Review Request 108706: bodega-server: Move authorization checks to the routes.js
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/108706/#review26526 --- Ship it! Ship It! - Aaron J. Seigo On Feb. 1, 2013, 8:45 p.m., Antonis Tsiapaliokas wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/108706/ --- (Updated Feb. 1, 2013, 8:45 p.m.) Review request for Plasma. Description --- It is better for the bodega-server to check the authorization of the user on the routes.js. Diffs - server/lib/db/changeAccountDetails.js c57de02 server/lib/db/setpassword.js b6c59cf server/routes.js 8861b92 Diff: http://git.reviewboard.kde.org/r/108706/diff/ Testing --- Thanks, Antonis Tsiapaliokas ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: KDEREVIEW: share like connect and plasmate
On Thu, Jan 31, 2013 at 12:47 PM, Aaron J. Seigo ase...@kde.org wrote: On Thursday, January 31, 2013 10:43:29 Ben Cooksley wrote: as it has been mentioned plasmate is ready to go into the extragear. Can you move it to the extragear? Where precisely in Extragear is Plasmate SDK and Share-Like-Connect headed? Base thanks :) Both Plasmate and Share-Like-Connect have now been moved to the appropriate locations. -- Aaron J. Seigo Regards, Ben Cooksley KDE Sysadmin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
[KDE Bugtracking System] REMINDER: current Plasma regressions
Please find below a list of the current regressions reported for Plasma. This is a weekly reminder. This search was scheduled by myr...@kde.org. Plasma regressions -- Bug 241685: https://bugs.kde.org/show_bug.cgi?id=241685 Priority: NOR Severity: crash Platform: Ubuntu Packages Assignee: plasma-b...@kde.org Status: REOPENED Summary: Random Plasma crashes [QGraphicsLayoutItem::isLayout , QGraphicsLayoutPrivate::activateRecursive] Bug 282552: https://bugs.kde.org/show_bug.cgi?id=282552 Priority: NOR Severity: crash Platform: openSUSE RPMs Assignee: plasma-b...@kde.org Status: REOPENED Summary: plasma desktop crash on add default panel Bug 290018: https://bugs.kde.org/show_bug.cgi?id=290018 Priority: NOR Severity: normal Platform: Ubuntu Packages Assignee: plasma-b...@kde.org Status: REOPENED Summary: Add Widgets strip and Activity Manager no longer slide in Bug 301424: https://bugs.kde.org/show_bug.cgi?id=301424 Priority: NOR Severity: normal Platform: openSUSE RPMs Assignee: plasma-b...@kde.org Status: CONFIRMED Summary: Cannot open battery monitor applet if set to hidden in systray Bug 302310: https://bugs.kde.org/show_bug.cgi?id=302310 Priority: NOR Severity: normal Platform: Compiled Sources Assignee: plasma-b...@kde.org Status: REOPENED Summary: Does not reflect insert/removal of battery Bug 307059: https://bugs.kde.org/show_bug.cgi?id=307059 Priority: NOR Severity: normal Platform: unspecified Assignee: plasma-b...@kde.org Status: CONFIRMED Summary: tooltips in widget explorer don't show widget version anymore Bug 311354: https://bugs.kde.org/show_bug.cgi?id=311354 Priority: NOR Severity: normal Platform: unspecified Assignee: plasma-b...@kde.org Status: CONFIRMED Summary: System Tray widget can't be resized to fit all icons in one row when added to the desktop Bug 311503: https://bugs.kde.org/show_bug.cgi?id=311503 Priority: NOR Severity: normal Platform: Compiled Sources Assignee: plasma-b...@kde.org Status: CONFIRMED Summary: Scrollbar in Add Widgets almost invisible with new Air theme ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
