--nextPart1438656.qNRzAeFEX2 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, On Thursday 14 September 2006 12:43, Matthias Lechner wrote: > here is a reworked proposal for the KAssistantDialog class created by > Jaroslaw (jstaniek) and me. I wonder whether this is not slightly too high level for many cases. Sure,= =20 your proposal is very helpful, if you have a structure like this: Page2a - Page3a - Page4a / \ Page1 End \ / Page2b - Page3b -=20 However, what about cases where you really just want to skip over one page: Page1 - Page3 - Page4 - Page6 - End \ / \ / Page2 Page5 If I understand your proposal correctly, this would mean setting up four=20 different paths, eight if there's a third optional page. What I do think is very nice about your approach is the ability to "group"= =20 pages. Two suggestions: 1) Maybe it would be more useful to just allow the user to define page grou= ps=20 instead of "paths". Then, in the first example you could just say "disable= =20 group b" or "disable group a". In the second example, you'd use a more=20 traditional approach of disabling pages 2 and 5, if appropriate. 2) If you want to stick with paths, at least do the following: a) re-add a KAssistantPage::setAppropriate()/isAppropriate() to make the=20 second example less painful b) maybe add something like a default path to the KAssistantDialog, and add= a=20 KAssistantDialog::addPage(), which would add to the default path, so very=20 simply assistants (fixed page order) remain very simply to set up. Regards Thomas --nextPart1438656.qNRzAeFEX2 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQBFCTxQEKRv+5DVNhgRArzhAKCXe9MKBC4GdEYkyOOP6v72wKX0/wCdFsKV NkIzUykOSDsCHj9xl+pDE8M= =fM+J -----END PGP SIGNATURE----- --nextPart1438656.qNRzAeFEX2--