--===============1559415006==
Content-Type: multipart/signed;
  boundary="nextPart5084277.UMnFMnfVCs";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart5084277.UMnFMnfVCs
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 17 July 2006 23:03, Jaros=C5=82aw Staniek wrote:
> For 2.0 (probably not this year..) I plan to integrate with the startup
> screen/window for Kexi as much as possible.=20

Thats really cool; I welcome any and all efforts that will make kexi feel=20
more like a part of the family

> Since starting a new Kexi=20
> project is not a mater of choosing template, we need some exensibility
> for the startup screen.

Why would it not fit in the template dialog? You would benefit from the=20
extensive work many people did on that dialog to make it the best=20
usability wise and technically.
I fail to see how kexi functionality can not be modified to fit with the=20
template idea making it really integrate.
The way kexi now handles opening or creating is certainly in need of=20
improvement; too many dialogs and steps making the user feel lost.

I suggest you work in that direction, and I suggest you talk to the people=
=20
from openusability who are experts in knowing what will have the best=20
impression.
=2D-=20
Thomas Zander

--nextPart5084277.UMnFMnfVCs
Content-Type: application/pgp-signature

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

iD8DBQBEvJ0bCojCW6H2z/QRAteqAJ91FnSvpneE5ZVv0K5Fp34ZD+urqACfd9VB
Rsenx+5ZEo0jNNtgPQbUP5A=
=phWv
-----END PGP SIGNATURE-----

--nextPart5084277.UMnFMnfVCs--

--===============1559415006==
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

--===============1559415006==--