--===============1913557338==
Content-Type: multipart/signed;
  boundary="nextPart114624903.b8lWrQYfyN";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart114624903.b8lWrQYfyN
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 28 April 2006 07:14, Thorsten Zachmann wrote:
> I think KoInteractionTool might not be the best name if it is kept like
> it is at the moment and if it is not a base class or a class used for
> different tools. You can also have an interaction when you work on
> modifying the points of objects but that would be a different tool.

I was indeed thinking about making the KoInteractionTool basic enough so=20
applications like karbon can have 2 instantiations, one for the default=20
tool and another that works on points.
This is why I chose the name as it is.

As boud pointed out in an earlier email, we need two types and each type=20
of tool will be used more then ones in the end-application.

Remember, this is a library, we provide building blocks, not always things=
=20
that the user will directly see.
=2D-=20
Thomas Zander

--nextPart114624903.b8lWrQYfyN
Content-Type: application/pgp-signature

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

iD8DBQBEUbv/CojCW6H2z/QRAivtAJ9kaiLrmwSCRlguD4IKu34X+XMbAQCgmSpg
ihwEgPdJ3uhDkoiNAVGsOmU=
=M8ee
-----END PGP SIGNATURE-----

--nextPart114624903.b8lWrQYfyN--

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

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

--===============1913557338==--