From quanta  Mon Mar 31 21:38:06 2008
From: Andras Mantia <amantia () kde ! org>
Date: Mon, 31 Mar 2008 21:38:06 +0000
To: quanta
Subject: [Quanta] Call for test
Message-Id: <200804010038.13762.amantia () kde ! org>
X-MARC-Message: https://marc.info/?l=quanta&m=120699969518624
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1737132099=="

--===============1737132099==
Content-Type: multipart/signed;
  boundary="nextPart1364112.mFy40qc4WM";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1364112.mFy40qc4WM
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

 here is an early call for test the upcoming Kommander 2.0 version.=20
According to my plans, the first step would be to port the existing=20
Kommander Executor 1.3 to KDE4 without changing it too much.
This will allow the users to:
=2D use the Kommander Editor 1.3 until the new one is ready
=2D run existing dialogs without modifications [see notes]

As quite some things have changed between KDE3 and KDE4, there are high=20
chances that the port has quite some bugs. I tried to port everything=20
that was in the current 3.5 branch, this means that it has some extra=20
functions that were added by Eric after 1.3 was released.

This call is intended mainly for those who created Kommander dialogs or=20
have time to download a few from www.kde-apps.org and compare when they=20
are run under KDE3 and KDE4.

I'd like to get as much feedback as possible, either on the mailing list=20
or using the bugs.kde.org, with (short) examples that demonstrate what=20
fails or does not work as it should.

Now the notes:
=2D internal DCOP calls (@dcop, @dcopid, etc.) will not work. This is=20
something we cannot do anything about, as KDE4 is using DBUS, not DCOP
=2D external dcop ("dcop" command executed in a shell) will work except=20
when it calls a method of the running dialog itself (because of the=20
above reason). So an external DCOP call to a running KMail from KDE3=20
session should work.
=2D the DBUS interface is completely untested
=2D the executor is named "kommander", not "kmdr-executor"
=2D the code is in trunk/kdewebdev
=2D you probably need at least qt-copy, kdelibs, kdepimlibs, kdevplatform=20
from trunk to build trunk/kdewebdev. Kommander itself depends only on Qt=20
and kdelibs, so if you know how to do it, you can build Kommander only.=20
It might even work with KDE 4.0.x.
=2D information about building KDE 4 from trunk is on techbase:=20
http://techbase.kde.org/index.php?title=3DGetting_Started/Build/KDE4



Andras

=2D-=20
=20
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org

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

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

iD8DBQBH8VnFTQdfac6L/08RAprFAJ4qm0Vzz8UbcctOkTKSXZ2i+l40fwCgynLe
7TbAlU32PXBtqOY6bKl59Bk=
=QB1t
-----END PGP SIGNATURE-----

--nextPart1364112.mFy40qc4WM--

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

_______________________________________________
Quanta mailing list
Quanta@mail.kde.org
https://mail.kde.org/mailman/listinfo/quanta

--===============1737132099==--