Re: unity-like interface
On Thu, Mar 15, 2012 at 4:00 AM, Aaron J. Seigo wrote: > On Wednesday, March 14, 2012 17:22:19 Heath Matlock > wrote: > >> There's someone else >> working on a Kwin-QML interface similar to what you would get >> combining Moblin and Gnome, and he's looking at making it a shell. > > do you have a link to this? He/she hangs in #plasma, the user's nickname is "mokush" re:rest of your responses Thanks, time to get some work done! -- Heath Matlock +1 256 274 4225 ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: unity-like interface
On Wednesday, March 14, 2012 17:22:19 you wrote: > Ideally this work can be downloaded as an activity template, right? Or yes; however this is where some additional work is needed as this really isn't an activity template at all but using the scripting to modify the workspace shell itself. so while behind the scenes it's all the same javascript API and package format for distribution, plasma-desktop needs to be able to differentiate between different kinds of script packages: those which are meant to be used as an activity template; those that define a panel layout that can be added to an existing configuration; those that re-work the entire shell; etc. > There's someone else > working on a Kwin-QML interface similar to what you would get > combining Moblin and Gnome, and he's looking at making it a shell. do you have a link to this? > referring to shells or activities? You also stated, "we just need to > add the ability to run a kwin js after the plasma-desktop js for the > full effect," how do you propose doing this? the relevant code is in kde-workspace/plasma/desktop/shell in plasmaapp.cpp there is a method PlasmaApp::createActivityFromScript which is currently called from the ActivityManager. this ends up calling DesktopCorona::evaluateScripts. createActivityFromScript is not actually very activity-specific at all :) then there is DesktopCorona::addPanel which is similar and called from the Add Panel menu. it optionally loads a script, also using evaluateScripts. so .. what probably needs to be done: * a new method in DesktopCorona which takes a Plasma::Package to execute (this will encapsulate all the script handling in one place; right now it is duplicated/scattered across createActivityFromScript, populateAddPanelsMenu, ActivityManager::activityTypeActions, etc.) * in that method, after running the plasma desktop script, if there is a kwin script also in the package, trigger kwin (via dbus) to run it > Also, what do I need to look into in integrating a maximized window's > titlebar into the default panel? This should be enough to get me > started. there is the active window plasmoid, but that always shows the window name and close button. so .. one could take that plasmoid and modify it so that only if the current window is maximized that it shows anything, and you should be done. -- 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
unity-like interface
I'm sure almost everyone here has seen the videos which make the Plasma Desktop shell like the Unity interface. I think these setups are beautiful, but my my gripe with them is that when a window is maximized, the window isn't integrated with the default panel on top. So when you sling your mouse to the top right of the screen and left click, you aren't closing the window like you do in Unity or in the default setup for Plasma Desktop, which makes for an accessibility problem. Because I find the oxygenized Unity-like interface appealing, I want to fix this problem and I'm going to dedicate some of my time to working on this; but I need guidance. This is where you guys can help! ...hopefully :) Ideally this work can be downloaded as an activity template, right? Or should activities not be confused with shells? There's someone else working on a Kwin-QML interface similar to what you would get combining Moblin and Gnome, and he's looking at making it a shell. Aaron, you mentioned that there is some work needed "so that script packages can advertise a bit more clearly what they do (e.g. 'remake the whole desktop') and then present that in the UI", are you referring to shells or activities? You also stated, "we just need to add the ability to run a kwin js after the plasma-desktop js for the full effect," how do you propose doing this? Assuming activities are the way forward for this oxygenized-Unity interface idea (henceforth called Amity) , here's a link which may be relevant to this work: http://techbase.kde.org/KDE_System_Administration/PlasmaDesktopScripting#Templates In the metadata.desktop file, can you specify in X-KDE-PluginInfo-Depends= other widgets the activity depends uses? In my case, initially, I need the Icon-only task manager and Takeoff widgets. Also, what do I need to look into in integrating a maximized window's titlebar into the default panel? This should be enough to get me started. Best regards Plasma dev team! -- Heath Matlock +1 256 274 4225 ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
