--===============0556092632042170738==
Content-Type: multipart/signed; boundary="nextPart3396713.aedgkxkvZR"; micalg="pgp-sha1"; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7Bit


--nextPart3396713.aedgkxkvZR
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

On Monday, June 4, 2012 08:13:45 Anatoli Gorchetchnikov wrote:
> Hi all,
> 
> I will be redesigning my app (last supported under KDE 3.5, dormant for
> about 7 years) for a modern system. As I noticed Qt 5 is in the process of
> appearing and I would presume KDE 5 will follow shortly. The engine
> redesign will take at least a few months, so I have some flexibility on the
> GUI side timewise. Do you guys think I shall aim at the 5 from the start,
> or play it safe, stick with 4, and set aside some time for porting it to 5
> later?

the jump to Qt5 and KDE Frameworks 5 will not be big. if you get started now 
with a port to Qt4 you'll be mostly done :)

something to keep in mind while porting: more than ever the separation of data 
and UI is being emphasized in Qt. Qt4 edged this way with model/view, but this 
is now absolutely key to QML...

-- 
Aaron J. Seigo
--nextPart3396713.aedgkxkvZR
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)

iEYEABECAAYFAk/MusUACgkQ1rcusafx20OFLACeKFaQzPUzP9iNzg/T4KjQJa8V
ujkAn13THP9aEDL8KmOnACeAsu/6dPfi
=sH7v
-----END PGP SIGNATURE-----

--nextPart3396713.aedgkxkvZR--


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


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============0556092632042170738==--