From jeremy.goecks@emory.edu Thu Jul 25 08:36:42 2013
From: Jeremy Goecks <jeremy.goecks@emory.edu>
To: galaxy-dev@lists.galaxyproject.org
Subject: Re: [galaxy-dev] HTML output with external Javascript
Date: Thu, 25 Jul 2013 08:36:31 -0400
Message-ID: <EF0C4294-6C65-4FB0-933D-FE12B5D3F0D9@emory.edu>
In-Reply-To:
 <29498109FA9F36468FA61A177A37E8612BFAF83E@SI-MSEDAG02.US.SINET.SI.EDU>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3842480544303495713=="

--===============3842480544303495713==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable


> The file that Gift is producing is already an html file and there's
> already an html datatype in Galaxy by default.  The output file in
> question just invokes remote javascript libraries inside <script> tags,
> and this seems to be tripping up Galaxy's data viewer. =20

Setting up relative paths to images and scripts inside your HTML output shoul=
d work; this is done in FastQC and other similar tools.

> We've tried downloading and referencing the
> javascript libraries in /static/js as well.

This should work as well and is the approach used by the rGenetics tools, but=
 the path you want is /static/scripts/ Note that Galaxy already has many jQue=
ry libraries in /static/scripts/libs/jquery, which could simplify development.

> I know that the new visualization platform in Galaxy uses a lot of
> external javascript libraries like D3=C5=A0 does anyone know how that is be=
ing
> handled differently?

For now, the viz framework is a different code base that's not relevant for d=
isplaying datasets.

Best,
J.

--===============3842480544303495713==--