Re: [ptp-dev] ETFW classes and methods to query togoption settings

[Wyatt Spear <wspear@xxxxxxxxxxxxxx>]

Just to make sure I'm clear: The middle step has a UI element, the value of which sets an environment variable.  You need to access that value from within the first step.  This isn't possible with the current architecture because each 'step' is encapsulated in its own object and only has access to the values assigned to it in the launch configuration.  What I was suggesting above is that you could have two elements, one for each step, with the same value.  The idiom of the system is that each tool defined in the xml workflow is gets its parameters set by a distinct set of widgets with no sharing.  The proper fix, though, is to allow a single xml element to set a value for more than one tool.  I think I could implement something like that, but I want to make sure what I'm describing addresses your requirements.

=Wyatt

On Wed, Feb 29, 2012 at 5:38 PM, Brian Watt <bwatt@xxxxxxxxxx> wrote:

> Greetings
>
> The ability to set environment variables through the xml-spec is
> already present, with syntax like:
>         <global name="SCORPEnvironment">
>               <envvar flag="FOO" value="BAR"/>
>       </global>
> (The environment variable FOO is set to the value BAR)
> Or though a ui element:
> <togoption label="Env Bar" optname="BAR" envvar="true">
>                       <optvalue type="text"/>
> </togoption>
> (envvar means the optname, BAR, will be set as the environment
> variable name and given the value put in the text box created in the UI)
>
> If I understand, you need to pass the same value as an environment
> variable for one step and a command line argument for another?

Restating it a bit... I need to query the value within the
first step's dataManager class, which is set into an environment
variable UI element defined in the middle step. Is this even possible?

> The
> easy, but ugly way is to have two UI elements, one for the variable
> and one for the argument and set them to the same value.  I will
> need to dig around a bit to find a cleaner way to handle it.
>
> Regards,
> Wyatt
>
> On Wed, Feb 29, 2012 at 2:40 PM, Brian Watt <bwatt@xxxxxxxxxx> wrote:
>
> Wyatt,
>
> I have a three step ETFW process.
>
> 1. The first step creates a temporary file as an "analyze" task.
> 2. The second sets some environment variables and runs an executable that
> produces several output files as an "execute" task.
> 3. The third step compares the timestamp of the temporary file to the
> output files and loads only the latest files into a view as an "analyze"
> task.
>
> Presently this all works if all of the files are created in the current
> working directory. However, I now need to specify an output directory as
an
> environment variable in the second task, and I need to access its value
in
> the first task when I create the temporary file. What ETFW classes and
> methods should I investigate to accomplish this?
>
> Brian Watt, IBM
>
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev

> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev

_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev