KAssistantDialog - reworked proposal

Thomas Friedrichsmeier thomas.friedrichsmeier at ruhr-uni-bochum.de
Thu Sep 14 18:23:50 BST 2006

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 
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) 
use case at the back of my mind: In RKWard there are "wizards" (currently 
custom coded), which are generated at run-time from xml-definitions of the 
pages and their order. Setting pages to inappropriate is simple using some 
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 "page 
groups". I've created a very rough draft of an API for that (only listing 
relevant parts, others are omitted; I hope it's enough to get the idea):

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060914/0e32a468/attachment.sig>

More information about the kde-core-devel mailing list