From kde-core-devel  Fri Aug 25 15:56:36 2006
From: "Aaron J. Seigo" <aseigo () kde ! org>
Date: Fri, 25 Aug 2006 15:56:36 +0000
To: kde-core-devel
Subject: Re: KAssistantDialog proposal
Message-Id: <200608250956.37873.aseigo () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=115652141023535
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1206158.jhp3UVdTai"

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

On Friday 25 August 2006 4:54, Matthias Lechner wrote:
> although I have some concerns about... I also appreciate Aaron's comments.
> Most of them mean just minor changes.

yes, hope you don't mind me picking through things with a fine tooth comb.=
=20
it's how we make code better ... just look at the messages on my recent=20
clearable lineedit improvement with people even picking out=20
individual "should be const" methods ;) it's how kde gets good code. peer=20
review. yum.

> Comments on the second point:
> The question which arises here is whether I should continue developing th=
is
> component when there are so many fundamental design issues.

i don't think there are so many ... even if there were, everything is fixab=
le.

> I designed the=20
> KAssistantDialog with the end user in mind. I don't think that the end us=
er
> should be exposed to any kind of hierarchy. And in my opinion designing
> pages hierarchically in the background and showing the user a flatten view
> is a good thing.

i don't think the problem is showing a flat view. i think the problem is=20
having coders construct trees. it's probably not necessary for the (coding)=
=20
use cases involved. can we simply get rid of the "construct trees" thing?

> Actually I really don't understand why my proposal makes things
> complicated.

it's complicated from the app developer's POV.

remember that when designing a UI class in a library that you have two sets=
 of=20
users:

end users who see the UI
coders to see the API

just as the UI needs to be usable for users, the API needs to be usable for=
=20
developers. this way people -enjoy- writing code with your classes and find=
=20
themselves more productive. this means coders will actually use it and=20
therefor users will get to enjoy your UI =3D)

> Well, actually it's not my decision whether I should continue. Please tell
> me! However, I want to be sure not to waste time.

i vote "continue on" ... things take a rev or two =3D)

=2D-=20
Aaron J. Seigo
Undulate Your Wantonness
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

=46ull time KDE developer sponsored by Trolltech (http://www.trolltech.com)

--nextPart1206158.jhp3UVdTai
Content-Type: application/pgp-signature

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

iD8DBQBE7x211rcusafx20MRAjmHAKCAhEwg/VvBM7tvAZ1MoRmVtnMlTwCfZrMs
/hCiybHSiDqD/TxaQhhtqVw=
=c/AB
-----END PGP SIGNATURE-----

--nextPart1206158.jhp3UVdTai--