>From a user's POV, I second what Ivan wrote. I still think it was a neat
idea but there were several reasons why I didn't use extenders:
1. Crash-prone. Plasma would often crash when playing around with them (the
Extender section in Plasma HowTo was, hands down, the hardest section to
record due
On Tuesday, November 15, 2011 16:08:17 Marco Martin wrote:
> > so ... i'd like to propose that we kill Extender, ExtenderItem and
> > ExtenderGroup in libplasma2.
>
> i say kill it.
>
> to me extender is the typical "seemed a good idea at the time"
My thoughts exactly. :)
+1 for killing them.
On Tuesday, November 15, 2011 16:08:17 Marco Martin wrote:
> now, crazy usual crazy idea moment:
> funny thing, in qml it would be way easier to do them: we could have an
we talked about exactly this, only SVG+Javascript, at the kdelibs meeting
trysil ... yes, that one. way before 4.0. :)
some t
+1 for removal
with a small note - I don't think that extenders turned up to be a bad
idea - from my pov, extenders in plasma failed because of a few design
decisions (eg could have been dropped on an unlocked desktop and
nowhere else) and bugs :)
--
Cheerio,
Ivan
--
While you were hanging y
On Tuesday 15 November 2011, Aaron J. Seigo wrote:
> hi :)
>
> after today's research and reflecting on the situation, i consider them a
> failed experiment. not a terrible one, but it didn't exactly succeed. i
> suppose it's the same thing as the old tear-off menus -> neat idea, few
> used them,
hi :)
i've been working a bit yesterday and today on the de-QGraphicsView-ification
of libplasma2. Applet no longer uses any of the Plasma QGraphicsProxyWidgets
and i believe i have it on a path towards proper abstraction so we can have a
QGraphicsWidget and a QML Item based implementation.
ho