Kickoff-QML and classic launcher

[Martin Gräßlin]

On Wednesday 21 December 2011 18:25:51 Aaron J. Seigo wrote:
> On Tuesday, December 20, 2011 20:51:32 Martin Graesslin wrote:
> > My personal favorite is option 3.
> 
> 3 is a good solution imho ... except that it will break people's
> installations who have kde-workspace but not kdeplasma-addons installed. so
> we can break this into two applets, but i don't think we can move the
> classic menu out just yet.
With a kconf update script it might be possible. If the user uses the classic 
menu and it's not available any more we transfer him to Kickoff.
> 
> also, right now the "switch to classic menu" / "switch to kickoff" option in
> the context menu works by deleting the existing applet and creating a _new
> one_ of the new type. this pretty well sucks as it means settings get lost
> in what should be a setting-loss-less event.
full ack. I thought about that before I wrote the mail and decided that iff I 
port the classic menu to QML it would not become an own applet but just a 
different QML frontend for the same applet.
> 
> it's really a horrible hack and i'd suggest getting rid of it. people can
> add the classic menu from the widget explorer like all the rest.
> 
> in fact, since we had a thread about the scripting stuff here already, we
> could easily add a "Classic KDE" panel script option that creates a panel
> just like in KDE 3. heck, it could even change the desktop use icons only.
> this would be rather trivial to make happen for 4.9 .. thoughts?
What you want to destroy the use case for Trinity and Qt-Razor? ;-)

Sure sounds like a good idea.

Cheers
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20111222/475c1be6/attachment.sig>