Files
galaxy/config/plugins/visualizations
Eric Rasche 23b4ddc947 Notebook signatures must be unique
Rather than assigning a static notebook signature, this has been replaced with a randomly,
deterministically generated notebook signature. This is currently done off of the dataset's id,
encoded through trans (so it's the unique hash, and not just the number), however this will need to
be exchanged for history_id whenever we have access to that.
2014-10-18 18:38:01 -04:00
..

Custom visualization plugins
----------------------------

Visualizations can be added to your Galaxy instance by creating
sub-directories, templates, and static files here.

Properly configured and written visualizations will be accessible to
the user when they click the 'visualizations' icon for a dataset
in their history panel.

The framework must be enabled in your 'galaxy.ini' file by uncommenting (and
having a valid path for) the 'visualizations_plugin_directory' entry.

For more information, see http://wiki.galaxyproject.org/VisualizationsRegistry


Sub-directory structure
-----------------------

In general, sub-directories should follow the pattern:

    my_visualization/
        config/
            my_visualization.xml
        static/
            ... any static files the visualization needs (if any)
        templates/
            ... any Mako templates the visualization needs

The XML config file for a visualization plugin can be validated on the command
line using (from your plugin directory):

    xmllint my_visualization/config/my_visualization.xml --valid --noout