--===============1439863668== Content-Type: multipart/signed; boundary="nextPart5705665.jSCKBRjoMz"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart5705665.jSCKBRjoMz Content-Type: multipart/alternative; boundary="Boundary-00=_X97hIYFkkhhnSOM" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-00=_X97hIYFkkhhnSOM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Tuesday 22 July 2008, A.J. Venter wrote: > Hi guys, > Last night I began hacking on kde3to4 version 0.0.2, the major changes are > a switch to kioclient as the library backend and the one I am writing > about. > > Working on plugins, it quickly became apparent that barring a very small > number of exceptions, you can migrate almost anything by copying > $KDE3DIR/share/apps/$APP and $KDE3DIR/share/config/$APPrc to the same > locations in $KDE4DIR In theory JuK should be able to import data from KDE 3.5. KDE 3.4 and befo= re=20 may be an issue with trunk as some support for old data used has been excis= ed=20 in trunk. The KDE 3.5 importing is heuristic, not deterministic but I can't see any=20 reason why the mechanism used to detect old code shouldn't succeed most of = the=20 time. Regards, - Michael Pyne --Boundary-00=_X97hIYFkkhhnSOM Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: 7bit On Tuesday 22 July 2008, A.J. Venter wrote:
> Hi guys,
> Last night I began hacking on kde3to4 version 0.0.2, the major changes are
> a switch to kioclient as the library backend and the one I am writing
> about.
>
> Working on plugins, it quickly became apparent that barring a very small
> number of exceptions, you can migrate almost anything by copying
> $KDE3DIR/share/apps/$APP and $KDE3DIR/share/config/$APPrc to the same
> locations in $KDE4DIR

In theory JuK should be able to import data from KDE 3.5. KDE 3.4 and before may be an issue with trunk as some support for old data used has been excised in trunk.

The KDE 3.5 importing is heuristic, not deterministic but I can't see any reason why the mechanism used to detect old code shouldn't succeed most of the time.

Regards,
- Michael Pyne

--Boundary-00=_X97hIYFkkhhnSOM-- --nextPart5705665.jSCKBRjoMz Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAkiHv1wACgkQqjQYp5Omm0rh1QCfQCLpahwUdjAe6ccnr2GOMiRe wtIAnjN5m6RrjqNRFN5/+AhY5onv4Dr3 =skuI -----END PGP SIGNATURE----- --nextPart5705665.jSCKBRjoMz-- --===============1439863668== 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 << --===============1439863668==--