From kde-panel-devel  Fri Sep 30 17:06:28 2011
From: Martin =?ISO-8859-1?Q?Gr=E4=DFlin?= <mgraesslin () kde ! org>
Date: Fri, 30 Sep 2011 17:06:28 +0000
To: kde-panel-devel
Subject: Re: Re: ScreenSaver and KDE Plasma 4.8?
Message-Id: <5564779.LPnZIgPaiD () martin-desktop>
X-MARC-Message: https://marc.info/?l=kde-panel-devel&m=131740241416303
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============2207338886739550887=="


--===============2207338886739550887==
Content-Type: multipart/signed; boundary="nextPart2087916.tLjICz9xDX"; micalg="pgp-sha1"; protocol="application/pgp-signature"
Content-Transfer-Encoding: quoted-printable


--nextPart2087916.tLjICz9xDX
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

On Friday 30 September 2011 12:38:34 Aaron J. Seigo wrote:
> On Thursday, September 29, 2011 22:14:59 Martin Gr=C3=A4=C3=9Flin wro=
te:
> > * add Plasma widget support to new screen
> > locker implementation but drop screensaver support (same problems a=
s first
> > option)
>=20
> +1 for this.
>=20
> if the lock screen is QML, when we get a QML version with OpenGL shad=
ers=20
> people can go crazy creating new screensavers in all their glory.
I just had a lengthy discussion about it with my GSoC student and we ca=
me up with the following plan:

* for 4.8 use a hack to fall back to the legacy implementation if a scr=
een saver is configured
* advertise the new functionality in the release announcement including=
 that you don't get the new super-awesome=20
lock screen if you use an old screensaver and that the old screensavers=
 are not secure
* advertise a new improved screen saver functionality in 4.9 based on Q=
ML with GHNS integration and more
* announce that the old screen saver support will be removed in 4.9 in =
favor for the new support and because it's an=20
old X dependency which we need to remove in order to start the transiti=
on to Wayland

This gives us no pressure to implement everything now for 4.8 and we do=
n't have unhappy users. In best case we=20
already have the new QML screen saver support in 4.8 and can get the co=
mmunity to port their screen savers to=20
QML. Also we give a good technical reason why we have to drop the scree=
nsavers.

I hope that makes everyone happy :-) (and is also the easiest way for m=
e in 4.8 as I don't want to spend too much=20
time on screen savers).

Cheers
Martin

>=20
> for Plasma widgets: it would mean creating a Containment and loading =
the=20
> configuration in that Containment; which means: not much.
>=20
> the current Plasma widgets support has a bunch of complicated code fo=
r working=20
> with (or more accurately: around) the screensaver unlocker window dia=
log. with=20
> a QML locker that doesn't require such hacking about, the code should=
 be a lot=20
> simpler and cleaner.
>=20
> i don't think we can just drop the widgets-on-locker functionality, h=
owever,=20
> as that's an actual real-world-useful feature (whereas screensavers a=
re an=20
> anachronism)
>=20
> --=20
> Aaron J. Seigo
> humru othro a kohnu se
> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
>=20
> KDE core developer sponsored by Qt Development Frameworks

--nextPart2087916.tLjICz9xDX
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEABECAAYFAk6F9xQACgkQqVXwidMiVrpxngCeONH50SLBzE3n7V4jgBda07j/
Pb0AoJs065ReOJBfh9GPHIyukBmKaUEZ
=pMa+
-----END PGP SIGNATURE-----

--nextPart2087916.tLjICz9xDX--


--===============2207338886739550887==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

--===============2207338886739550887==--