--nextPart42099425.MXMpCv0Hug
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

In data luned=EC 9 maggio 2011 18:03:18, Olivier Goffart ha scritto:
> Hi,
>=20
> With Qt5 around the corner[1], I think it is time to start thinking about
> KDE5
>=20
>=20
> Raw summary:
>  - Qt5 is planed to be released in about one year from now if everything
> goes well.
>  - It should be mostly source compatible with Qt4, and is just an
> opportunity to break binary compatibility.
>  - QWidget just stay for compatibility. All focus is put on QML. Do not
> expect new development on QWidgets from Nokia.
>  - The "OpenGouvernance" should finaly come into light, meaning we (as
> KDE), can contribute easier to Qt.
>=20
>=20
> I guess it make sens, as Qt breaks binary compatibility, to do the same in
> kdelibs.
> Does that mean "KDE 5"? or "KDE SC 5"? Not necessarily.
> We can break binary compatibility, and change the .so version of our
> library without changing the major version of KDE itself.
> But I think it would anyway still be a smart move to do it.
>=20
> And I think this is a perfect opportunity to get some KDE class in Qt as =
we
> planed. [2]
>=20
> Some item we might want to think about:
>=20
>  - Do we want "KDE 5" to be a big change, or just a small increment?
>=20
>  - Do we want to focus on QML, or stay with QWidget?
>=20
>  - Shall we try drive Qt5 based on KDE5's need?
>=20
>  - Do we have more visions for what KDE5 should or should not be?
>=20
> I guess there is as many opinions as people involved :-)
> Many things to think about, and that can be discussed further, and decided
> in Platform11 [3] (I will be there)
>=20
> But in my opinion, if there is something we should learn from the KDE4
> transition, it is not to be too ambitious.

Hi,
my 2 cents as a long time KDE user and recent time contributor.

1) The name. Some people have tried KDE 4.0, didn't like it (either for the=
=20
instability ore the missing features) and searched for something else. I've=
=20
personally seen how difficult is to change a "first bad impression" with so=
me=20
users. Probably if we took KDE SC 4.6.3 and release it as "KDE5" these user=
s=20
would say "wow, that is fantastic! A lot better than KDE4!". So a new major=
=20
version is a big opportunity to "refresh" the name.

2) Binary compatibility. It has taken four years to port most KDE3 apps to =
the=20
new infrastructure, and some (like Kooka) never did it. Many projects just=
=20
ended the transition from KDE3. Experience shows that even a well alive=20
project may not have the necessary manpower to do a drastic rewrite of the=
=20
code. So I would take Qt5 as an opportunity to fix legacy interfaces withou=
t=20
caring about binary compatibility, but (following Qt direction) the effort =
to=20
port existing code should be nowhere near the one needed from KDE3 to KDE4.=
=20
This would allow to maintain the good condition "there is a KDE app for=20
everything", which has been just recently achieved again. So, from a techni=
cal=20
point of view, don't rush to drop QWidget and switch to QML; let them live=
=20
together for all the necessary time, and ensure a smooth step-by-step=20
migration is possible.

3) Core apps, or "shall we change again everything?". It took at least 3 mi=
nor=20
releases (or 2 years since KDE 4.0) to have a fully crash-free experience w=
ith=20
the plasma shell. Now it looks fantastic, it is modular (desktop, netbook,=
=20
media centre) and light (it is usable on an 800 Mhz pentium III). I would h=
ope=20
for a stable 5.0 release, also in connection with point 1). So I'd say don'=
t=20
start again from scratch: the current base is solid, extendable, users=20
recognize it. Changement is not necessarily for good.

So in the end I fully agree with Olivier: "if there is something we should=
=20
learn from the KDE4 transition, it is not to be too ambitious"

Alberto

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

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

iQIcBAABAgAGBQJNyC/BAAoJEPSLZxv8jMkAKAMQAJxSwxexN6lV8JApYM4cKMa3
e674Dt6AcFQrj2/4DL62dgO32cm3udFtDAHQNRaoGx3ZRKlFHwdimMixvVZCQhS4
+MN6hW3OeeOaNR8vDfalpeFAqB6EDLqosEQnvK/61AGUex2TX/chQe6kB9D2vyJ4
/lB+ssWjcYvNPNkakKUDAQOj/4JquEs/gCuTANJN3CmPNV05h73nBUFP5j2mbKw/
KXwpRUuD5r3a+mHvmp3yh9xX0aX3sLEWsTapcV0mP8YCKIJtq2ES3R1oGT84bnM1
HzDY1L6NQ9XfAQG5Re71iQKNrd3LUP5MSGzX2BKM5zvL/WlsFZIP4TiJ6Si8GkbS
7FxVFWy8//eywdnoDHYF5f35cdb+oEss2hBhMaqgqXy1Y9i1iEYQ8yRI3D1P6Dem
zZGcc8n+sIxXOUo0RqxifHCqZY1lcHt0ZVaA+aOO23SJQ00Z1HNct+tDv3469zB9
6C00P95HqYaClRfQSiKQk8v7WPw3B14vQY9PZOUOIOMoC6RN/89YzGtS1bD+DImr
SrBWueU3kQOZKFoo9kSFFDUZQ/jKvqdZEYO2VCMMbnMNpUWHgETT6gJ/CqTQNG6o
f/uAfOmmfvTrp5gEc0uZd3qREhV1M02MEIvd2yVhvnwoQaw2e36QNdJxubKiSYpG
tdGdueVtVUG4PIjAJ1RU
=UJ8J
-----END PGP SIGNATURE-----

--nextPart42099425.MXMpCv0Hug--