Summary: | service menu management to kcontrol | ||
---|---|---|---|
Product: | [Unmaintained] kcontrol | Reporter: | Theodore Imre <blurymind> |
Component: | general | Assignee: | Daniel Molkentin <molkentin> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | wishlist | CC: | blurymind, lex.lists, tyrerj |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Slackware | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Theodore Imre
2006-04-08 15:53:45 UTC
This seems like a good idea. I don't know if it can be easily realized. This is a new KDE Control Centre module. Do we have any volunteers to write such code? I think the idea is great and would solve a significant problem but honestly the mockup at KDE-Look is frightening complicated and the suggested implementation too. I would vote for this idea if it could be shown more simply. What do you consider the essential or core components to look like? behave like? Note - I am not saying you must cater to newbies or that your idea is too difficult, I am saying can you keep this high-level and let the coders worry about implementation? well,you do have point.It does seem abit complicated,but its only the first mockup idea.You can do it in anyway you consider possible.I am not a developer. What i can think of the behaving of the script .. *installing new service menus (for one user(~/.kde/...) or for all users -if possible) *enabling and disabling their menus the installation should just read a script within the service menu package (tar.gz archive) and copy the files within to proper directories...and ask for root password if needed of course. enabling and disabling their submenus should be done harder i think.The scripts are usually placed in the konqueror/services folder and i am not absolutelly sure how they can be handled by the module. So yeah.I just give you the idea,you are the developers,you should know a better way to implement this...even if it is partially. How do I edit this page?I want to edit what i wrote. Hi,I made a NEW MOCKUP IDEA,which is Much simpler and effective!! You can see my edit at: http://www.kde-look.org/content/show.php?content=37465 New MockUP: http://img284.imageshack.us/img284/8389/mockup2legend6ss.jpg Would love to see this integrated in the next version of KDE. Perhaps 3.5.3, if it's not too late. somebody said: "You`re right, thats really a needfull feature, but it can get into KDE not before 3.5.5 ;)" hope it gets. I am gonna work out a better mockup later.It needs a simpler interface. =D MOCKUP 3 (screenshot1/download) ================ in this version of the mockup,I added my idea for adding custom actions,which was driven by Thunars' User Customizable Actions (thunar-uca): http://thunar.xfce.org/plugins.html#thunar-uca i think that a sepparate dialogue for making a custom action is better in this case,but you know,it can also be done with only one input text box (and a short HowTo for the sintax) =) I was hasty and I couldnt think of a better sintax than: servicename= /action1(command1;command2;etc...)&action2(command1;command2;etc)&... and for submenus: />submenu1-action1(...)&action2(...)>submenu2-same/>submenutosubmenu2.... etc etc or something like that.Where submenu* stands for the name of the menu and action* stands for the name of the action (the things we will see in the right click menu) and (*) are the commands that are being executed for the action name before the () ... or something simple like that. =) =============== check it out here: http://www.kde-apps.org/content/preview.php?preview=1&id=37465&file1=37465-1.jpg&file2=37465-2.jpg&file3=37465-3.jpg&name=service+menu+management+to+kcontrol or http://www.kde-apps.org/content/show.php?content=37465 (download link) Stumbled apon this bug via a comment of the author. I've created a Korundum app which enables the user to manage servicemenus, although not implemented as a KControl module but as a standalone application. Currently it's not possible to automatically install scripts (only the .desktop file), because many of them require a configure/make/make install cycle. Like the Theodore Imre pointed out, this would require a special package format. Take a look at: http://kde-apps.org/content/show.php/Themis+Action+Editor?content=55644 Feedback welcome. Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. Kcontrol has been replaced by System Settings in Plasma. Please give the latest version of that a try, and open a new bug in "systemsettings" if you continue to have an issue. Thank you! |