[Ctk-developers] Workflow Widgets

[Jean-Christophe Fillion-Robin]

Hi Matt,

The current implementation of the ctkWorkflow widget was based on its
KWWidgets counter part [1].

(1) If your workflow required the user to go through a pre-defined
sequences of steps, it makes sense to re-use the CTK workflow. For example,
see
http://public.kitware.com/Wiki/Bender/Documentation/2.0/Modules/SimpleWorkflow

(2) On the otherhand, if the user should be able to do any of the "step"
(or task) before or after any other one, following the recommendation
Andras makes sense.

Hth
Jc

[1]
http://www.kwwidgets.org/doc/nightly/html/classvtkKWWizardWorkflow.html#_details

On Thu, Apr 23, 2015 at 8:42 AM, Andras Lasso <lasso at queensu.ca> wrote:

>   I would be very interested in others' experiences, too.
>
> Andras
>  ------------------------------
> From: Clarkson, Matt <m.clarkson at ucl.ac.uk>
> Sent: ‎2015-‎04-‎23 04:59
> To: Andras Lasso <lasso at queensu.ca>
> Cc: ctk-developers at commontk.org
> Subject: Re: Workflow Widgets
>
>   Hi Andras,
>
> thanks for this. Its good to hear your experience.
> If anyone else has any, I’d still love to hear it!
>
> Thanks all.
>
> Matt
>
> On 22 Apr 2015, at 19:59, Andras Lasso <lasso at queensu.ca> wrote:
>
> > Hi Matt,
> >
> > A few years ago we tried to use the CTK (at that time KWWidgets)
> workflow widget for IGT application GUIs, but we did not find useful for
> our purposes mainly due to two reasons:
> > 1. Usually IGT workflows are simple linear workflows (import pre-op
> data, calibration/registration, targeting, and verification).
> > 2. You never want to prevent the user from jumping to any state at any
> time. If a state is not meaningful (e.g., you cannot do targeting before
> calibration) then it is better to let the user to switch to the state,
> display what you can, and show a short warning message that explains what
> you should do (e.g., calibrate first) than simply disabling the "Next"
> button.
> >
> > Nowadays we mostly use QToolbox widget or QButtonGroup of
> ctkCollapsibleButton's. QTabWidget would be nice, too, but usually
> horizontal space is limited and therefore we could only have maximum 3-4
> tabs and short tab captions, which is often not enough.
> >
> > Andras
> >
> > -----Original Message-----
> > From: Ctk-developers [mailto:ctk-developers-bounces at public.kitware.com
> <ctk-developers-bounces at public.kitware.com>] On Behalf Of Clarkson, Matt
> > Sent: Wednesday, April 22, 2015 8:50 AM
> > To: ctk-developers at commontk.org
> > Subject: [Ctk-developers] Workflow Widgets
> >
> > Hi there,
> >
> > Im looking round for inspiration to code up some IGI workflows.
> >
> > Does anyone have a good example of CTK workflow widgets? Im looking for:
> >  a) Nice pictures?
> >  b) An applicaiton I can run?
> >  c) Documentation?
> >  d) Small/medium/large in terms of number of steps and branching.
> >
> > Thanks
> >
> > Matt
> >
> > _______________________________________________
> > Ctk-developers mailing list
> > Ctk-developers at public.kitware.com
> > http://public.kitware.com/mailman/listinfo/ctk-developers
>
>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at public.kitware.com
> http://public.kitware.com/mailman/listinfo/ctk-developers
>
>


-- 
+1 919 869 8849
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20150430/c8becaf1/attachment.htm>