Bug 166725 - Jewel launcher button plasmoids
Summary: Jewel launcher button plasmoids
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-16 14:30 UTC by John
Modified: 2013-05-27 10:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John 2008-07-16 14:30:58 UTC
Version:            (using KDE 4.0.98)
Installed from:    Ubuntu Packages
OS:                Linux

A very useful and practical plasmoid would be a launcher button.

I can see this resembling the Kickoff button, i.e. one that can be added, resized and rotated on the desktop.

The user could choose from a variety of "jewel" designs, i.e. circular, rounded square (like the Kickoff one), triangular, etc., and from a variety of colours. The launcher buttons would resemble the "bejewelled" shapes, i.e. be very pretty.

Finally, the user could choose an image that could sit "inside" the button, making it useful. (I'm thinking of Nemo-in-the-egg from Finding Nemo - hope you're with me on that one.)

This is all very simple, but would allow the user to have a highly customisable desktop with buttons that could be grouped, sized and coloured to taste and importance.
Comment 1 Michael Bohlender 2013-05-27 10:14:32 UTC
Thank you for your suggestion for a new applet. Unfortunately the core developer team of KDE Plasma is only working on the infrastructure of Plasma and the most important applets to provide a desktop shell. Your suggestion does not fall into this category. But anyone from the wider KDE community could implement such an applet as you suggested. It doesn't need the core Plasma developers to implement this. As the wider KDE community is not using this bugtracker, it is very unlikely that this request will be picked up by anybody and as the core developer team will not implement this feature, we have to set it as won't fix.