host visualization plugins

[wilzbach]

@bgruening had the great idea to host visualization plugins inside this repo (until the ToolShed supports thems).

-> would you be interested (a) in hosting visualization plugins in this repo or (b) do you want to create a separate repo (e.g. vis-iuc) or (c) do you have another idea?

Minimal list of contributors with visualization plugins:

• @saketc
• @carlfeberhard
• @greenify
  [...]

For more infos #71.

[bgruening]

Hi Seb,

+1 for me for (a).
If you can create a pull request I will review them and merge it.

[hexylena]

+1 for a from me.

[jj-umn]

On 10/14/14, 5:44 AM, Seb wrote:

@bgruening https://github.com/bgruening had the great idea to host visualization plugins inside this repo (until the ToolShed supports thems).

-> would you be interested (a) in hosting visualization plugins in this repo or (b) do you want to create a separate repo (e.g. |vis-iuc|) or (c) do you have another idea?

Minimal list of contributors with visualization plugins:

• @saketc https://github.com/saketkc/galaxy_tools/tree/master/visualisation_plugins/
• @carlfeberhard https://bitbucket.org/carlfeberhard/galaxy-visualization-dataset-choice/src/7dbaf921428a13586950104b98687920ebda3233?at=default
• @greenify https://github.com/greenify/galaxy_vis_plugins [...]

For more infos #71 biojs/biojs#71.

—
Reply to this email directly or view it on GitHub #4.

+1
JJ

James E. Johnson Minnesota Supercomputing Institute University of Minnesota

[dannon]

This all sounds good to me.

[saketkc]

Is it possible to have versions for visualization plugins too?
I have a BioJS component ported to Galaxy: https://github.com/saketkc/galaxy_tools/tree/master/visualisation_plugins/inchlib

BioJS is rapidly evolving and this component has already been ported to BioJS2.0: http://registry.biojs.net/client/#/detail/biojs-vis-inchlib
, making it incompatible with BioJS0.1

However a version based approach will allow me to support for both the versions. Something like this in the mako headers?

<meta name="galaxy-vis" content="My Viz" data-version="0.0.1" />

[bgruening]

@saketkc not that I know of. Also this raises a lot of other question: How should a UI look like?
Currently, you are picking the VIS-name from your dataset, with versions how do you think should this look like? Imho, versions don't make much sense in interactive visualisations.
What you probably can do, just include your version number in your VIS-name. Overall, @carlfeberhard will know better than me.

[saketkc]

Naming by version number sounds good!

[wilzbach]

@bgruening suggested in #5 to use edamontology as ontology for the datatypes used in the configuration.

[hexylena]

@galaxyproject/iuc can this be closed? Viz plugins have been merged in so a decision seems to have been made regarding this. (On that note I deprecated my video viz plugin and added that to this repo)

[bgruening]

I think this can be closed. I'm in contact with @greenify and will work on more VIS from biojs.