[kepler-dev] PythonScript example workflow for dynamic GUI dialogs

Bertram Ludaescher ludaesch at ucdavis.edu
Thu Mar 13 11:37:02 PDT 2008

This sounds very good!

In prehistoric Kepler times, we did some rerouting of actor output to the
user's default browser, letting the user inspect (or modify) data, before it
is fed back into the pipeline.

Seems that this would be possible now in a more integrated manner.

Having said this, I still think a "detour through the default web browser"
can be a useful thing...


On Thu, Mar 13, 2008 at 11:25 AM, Dan Higgins <higgins at nceas.ucsb.edu>

> Hi All,
>    I just checked in the example workflow
> $KEPLER/demos/Python/PythonDialogExample.xml
>    This workflow uses the PythonScript actor to dynamically create
> dialog for Kepler user input (simple text input and a choice box). It
> uses jython's capability of scripting Java swing widgets. I think this
> is a useful example that shows users how they could create new GUI I/O
> dialogs that execute when a workflow is running. This would also allow
> users to examine/modify parameters during execution.
>    One specific example in the workflow is a choicebox for user input.
> This has been requested by several Kepler users.
>     Comments/suggestions always appreciated.
> Dan Higgins
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/kepler-dev/attachments/20080313/b1a3babf/attachment.htm

More information about the Kepler-dev mailing list