Hi Chris,

Since the external application is outside of Galaxy's control, changes to the Galaxy interface will not necessarily override the behavior of the external application.  One possibility of why a new window is created could be the use of some javascript in the external application, perhaps setting the location or something like that.

Greg

On Jan 4, 2010, at 11:36 AM, Chris Zaleski wrote:

Greetings & Happy New Year,

In the XML file I copied (epigraph.xml) the <inputs> element does not have any attributes. I added in a target attribute as you suggested, but unfortunately it had no effect. My XML is the following (I changed very little from the original file):

<?xml version="1.0"?>
<tool name="GDM" id="gdm_export">
    <description>server</description>
    <redirect_url_params>GALAXY_NAME=${input1.name} GALAXY_TYPE=export</redirect_url_params>
    <inputs>
        <param format="txt" name="input1" type="data" label="Send this dataset to GDM">
            <!-- <validator type="unspecified_build" /> -->
        </param>
        <param name="REDIRECT_URL" type="hidden" value="http://lucca.cshl.edu/GDM/login_from_galaxy.php" />
        <param name="DATA_URL" type="baseurl" value="/datasets" />
        <param name="GALAXY_URL" type="baseurl" value="/tool_runner?tool_id=gdm_export" />
    </inputs>
    <outputs/>
    <help>
        some stuff
    </help>
</tool>


I changed the <inputs> tag to: <inputs target="galaxy_main"> ...but the entire window is replaced.

If I could control the frame, or at least open the external page in a new window, it would save some confusion and offer a more consistent experience. Currently users would need to back-back-back their browser to get to Galaxy again.

If you have any other thoughts on 1) targeting the external web page or at least 2) opening in a new window, I'd really appreciate it.

Thanks very much once again,
Chris



On Thu, Dec 31, 2009 at 11:41 AM, James Taylor <james@bx.psu.edu> wrote:
In this case, I think appearing in the main frame should be the default. This is overridden in the tool config by specifying a target attribute for the inputs element, e.g.

   <inputs action="http://www.flymine.org" check_values="false" method="get" target="_top">
       <display>go to Flymine server $GALAXY_URL</display>
       <param name="GALAXY_URL" type="baseurl" value="/tool_runner?tool_id=flymine" />
   </inputs>

(See target="_top" on the first line which loads at the top level window).

Do you have a target specified in your tool config? To default to galaxy_main, it should just be missing.

On Dec 31, 2009, at 12:28 AM, Kanwei Li wrote:

Hi Chris,

You may do this by using the "target" attribute in your anchor tag, like so:

<a href="url" target="galaxy_main">Link text</a>

Please let me know if this doesn't work.

Kanwei

On Wed, Dec 30, 2009 at 9:30 AM, Chris Zaleski <zaleski@cshl.edu> wrote:
Greetings,

I have implemented a tool to export data to an external site. I used
"tools/data_destination/epigraph.xml" as a template & this works nicely. I
am simply wondering if there is a way to control the destination frame of
the external website. Currently the entire window is replaced. If possible,
I would like it to appear in the content area (galaxy_main?), similar to the
way many of the "Get Data" tools work (eg: UCSC Main).

Thanks very much,
Chris Zaleski

_______________________________________________
galaxy-dev mailing list
galaxy-dev@lists.bx.psu.edu
http://lists.bx.psu.edu/listinfo/galaxy-dev


_______________________________________________
galaxy-dev mailing list
galaxy-dev@lists.bx.psu.edu
http://lists.bx.psu.edu/listinfo/galaxy-dev


_______________________________________________
galaxy-dev mailing list
galaxy-dev@lists.bx.psu.edu
http://lists.bx.psu.edu/listinfo/galaxy-dev

Greg Von Kuster
Galaxy Development Team
greg@bx.psu.edu