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

On Thursday 14 September 2006 18:00, Jason Harris wrote:
> What if a KAssistantPath did not need to define the entire path from
> start to end, but could instead "branch off" of another path at page N,
> and merge back at page M.

Ok, but what are the semantics of setCurrentPath (), then? After all, this=
=20
would mean you can logically be in several paths (subpaths) at once.

Another reason why I'm sceptical of paths is that I have another (uncommon)=
=20
use case at the back of my mind: In RKWard there are "wizards" (currently=20
custom coded), which are generated at run-time from xml-definitions of the=
=20
pages and their order. Setting pages to inappropriate is simple using some=
=20
static logic. However, I don't see, how I could easiyl map this to paths.

Anyway, I think what you suggest is not too different from what I'd call "p=
age=20
groups". I've created a very rough draft of an API for that (only listing=20
relevant parts, others are omitted; I hope it's enough to get the idea):
http://rkward.sourceforge.net/temp/KAssistantDialog.thoughts

I have not read the previous proposal by Matthias, which is no longer onlin=
e,=20
not sure how close this idea may be to that, so sorry, if I'm taking the=20
discussion into a loop.

Regards
Thomas

--nextPart6308404.dLdyi8HGG2
Content-Type: application/pgp-signature

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

iD8DBQBFCZAqEKRv+5DVNhgRAnVcAJ4kBN3qHAYT3lBUUyDHvaGWy4jAWQCfZof5
8tcYuk9aXCt7vSXaitnDjp4=
=tSs3
-----END PGP SIGNATURE-----

--nextPart6308404.dLdyi8HGG2--