- When building a workflow, most parameters can be switched to
be set later ("at runtime"). The main (only?) exception is
parameters which are used as the test for conditionals
- When running a workflow, the user fills in the runtime parameters
just like in any other tool form.
- As a consequence, the run workflow form behaves more like a full
tool form (automatic refreshes, validation, et cetera).
- There is still a problem when paramters depend on a data input
that is not created until later. These should probably fall back
on late validation, but that requires a bit of cleanup to param
depedencies.
workflow editor works on IE7 (using excanvas). It actually *nearly* works on IE6 but
there are some layout problems that are probably not worth wasting time on. If any IE
users can test this that would be great!
the workflow editor. Some improvements from workflow pushed back to main
interface. IE specific CSS and javascript tweaks removed. No longer relying
on 'quirks mode' to make things work (instead, relying on IE7.js to make IE
behave like a standards compliant browser).
connections
2) Added a script for packing the javascripts, everything is now repacked
with yui-compressor (the packed versions are slightly large, but they
gzip better resulting in an overall reduction).
- Workflows have a simple database representation (StoredWorkflow)
- Workflow step parameters can be manipulated
- Workflows can be saved and loaded
- Many improvements to workflow editing interface
2) General interface cleanup
- Styles for the overall layout have been moved from the index page to
CSS files, colors for layout backgrounds and borders and such can now
be configured in the colors.ini file
- Styles and javascript code for dialogs and popupmenus (code is currently
in the workflow editor but will be moved out after more testing)
James Taylor