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!
and tools. Moved some methods related to params out of the Tool class, sets
of inputs can also be used in other ways (e.g. for modules). More abstraction
needed here.
is "InputDataset" which allows a workflow to have an input dataset which many
different tools can use (without needing to specify it repeatedly. Still need
to extract out a common interface (tools will become another type of "module")
which will clean this up a lot.
properly update the 'terminals' for the nodes in the editor. Many other fixes
to saving and loading of workflows (error tracking should now be working
properly).
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).
every page can be added to galaxy.base.js). Cleaned up history templates
accordingly. Also, added scripts from IE7.js which fix many layout bugs in
older versions of IE.
to drop the `stored_workflow` table if you have it before running this).
Much better separation between the underlying model and the json model used
to communicate with the browser. Various interface improvements. Most things
should work properly now (excepting still dynamic options and input
parameters inside groupings).
a link to workflow management from the tool menu. From there new workflows
can be created and existing workflows edited / run.
Still substantial problems with:
- Selects using "dynamic options" of any sort
- Repeat/conditional tools (no way to connect inputs in a repeat or conditional)
The database / json representation is a real mess. I'm going to completely
redo that next.
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).
- Fixing an event bug in jquery.ui
- Fixing positioning of canvas iframe
- Working around a weird canvas drawing issue (see HACK in galaxy.workflow_editor.canvas.js)
- Removing some JavaScript 1.6 methods
- 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)
- Can add steps (tool invocations) to the workflow
- Can modify options for tools that do not use dynamic options or nesting
- Can connect outputs to inputs, the editor does check type compatibility
(however this breaks down completely for the "input" type)
There is no way to save or run workflows yet (and not data model for them).
You'll need to set "enable_beta_features = True" in your config for this to
be accessible.
They are somewhat independent (you can use the new layout with the old style
and vice versa) but they belong together.
Tested in Firefox, Safari, IE5.5, IE6, but there are still some features
to be implemented before this is ready for 'main'.
To use, first add "new_style_june_2007=true" to the app:universe section of
universe_wsgi.ini (this gives you the new layout). Second change document_root
to "%(here)s/static/june_2007_style/blue" in the app:static_style section.
Style Features: simplifications, fewer 'hatched' images, space savings in some
places, small changes to the color scheme (same general feel, but the colors
are better matched). Main changes are to history, the new style support nested
datasets much better.
Layout features: no framesets (just iframes, some of which can be replaced with divs and ajax down the road). Frames are resizable and hideable. Tools can provide width hints and history will automatically hide (try UCSC main to see this).
James Taylor