[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: Re: Re: Kickoff-QML and classic launcher
From: Nowardev-Team <nowardev () gmail ! com>
Date: 2011-12-22 9:58:41
Message-ID: CAL6cU-2_82sf89-K6-e9mezcyJW4JnYG52bqFKty+rXUagzNzg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
2011/12/22 Martin Gr=E4=DFlin <mgraesslin@kde.org>
> 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 c=
an
> > 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 pan=
el
> > 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
>
:) i did a lots of panels btw.. mm i could try to make classic kde3
layout right now,
svn export --force
https://plasma-panels-script.googlecode.com/svn/trunk/usr/share/kde4/apps/p=
lasma/layout-templates/
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
>
[Attachment #5 (text/html)]
<br><div class="gmail_quote">2011/12/22 Martin Gräßlin <span dir="ltr"><<a \
href="mailto:mgraesslin@kde.org">mgraesslin@kde.org</a>></span><br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <div class="im">On Wednesday 21 December 2011 18:25:51 Aaron \
J. Seigo wrote:<br> > On Tuesday, December 20, 2011 20:51:32 Martin Graesslin \
wrote:<br> > > My personal favorite is option 3.<br>
><br>
> 3 is a good solution imho ... except that it will break people's<br>
> installations who have kde-workspace but not kdeplasma-addons installed. so<br>
> we can break this into two applets, but i don't think we can move the<br>
> classic menu out just yet.<br>
</div>With a kconf update script it might be possible. If the user uses the \
classic<br> menu and it's not available any more we transfer him to Kickoff.<br>
<div class="im">><br>
> also, right now the "switch to classic menu" / "switch to \
kickoff" option in<br> > the context menu works by deleting the existing \
applet and creating a _new<br> > one_ of the new type. this pretty well sucks as \
it means settings get lost<br> > in what should be a setting-loss-less event.<br>
</div>full ack. I thought about that before I wrote the mail and decided that iff \
I<br> port the classic menu to QML it would not become an own applet but just a<br>
different QML frontend for the same applet.<br>
<div class="im">><br>
> it's really a horrible hack and i'd suggest getting rid of it. people \
can<br> > add the classic menu from the widget explorer like all the rest.<br>
><br>
> in fact, since we had a thread about the scripting stuff here already, we<br>
> could easily add a "Classic KDE" panel script option that creates a \
panel<br> > just like in KDE 3. heck, it could even change the desktop use icons \
only.<br> > this would be rather trivial to make happen for 4.9 .. thoughts?<br>
</div>What you want to destroy the use case for Trinity and Qt-Razor? ;-)<br>
<br>
Sure sounds like a good idea.<br>
<br>
Cheers<br>
<span class="HOEnZb"><font \
color="#888888">Martin</font></span><br></blockquote><div>:) i did a lots of panels \
btw.. mm i could try to make classic kde3 layout right now, <br><pre \
class="prettyprint"><span class="pln"> svn </span><span \
class="kwd">export</span><span class="pln"> </span><span class="pun">--</span><span \
class="pln">force https</span><span class="pun">:</span><span class="com">//<a \
href="http://plasma-panels-script.googlecode.com/svn/trunk/usr/share/kde4/apps/plasma/ \
layout-templates/">plasma-panels-script.googlecode.com/svn/trunk/usr/share/kde4/apps/plasma/layout-templates/</a> \
</span></pre> <br><br> <br></div><blockquote class="gmail_quote" style="margin:0pt \
0pt 0pt 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br> \
<br></blockquote></div><br>
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic