Hi Ning, Please find my inline-comments. On Mon, May 21, 2012 at 3:14 PM, Shen, Ning <leos...@illinois.edu> wrote:
> Hi Suresh, Lahiru and Saminda, > > We have encountered following issues when testing avirata today and hope > they can be addressed asap. > Points 1&2 are job running related > 1. The execution order of workflow is not correct > For example, block 1 and 2 are green at the same time which is > confusing since blocks should be running sequentially. > The dotted line connecting block 1 and 2 was not there as before(we > are told that it is not necessary for avirata), but since the execution > order was not correct. > there's no wrong with execution order, its just a matter of the coloring. We wait until we get the response from first and then only we execute the second one. This issue is there in ogce version too, this will be fixed when I create the dottod line between forEach and first node, I just created the workflow and updated the registry. > > 2. The improper execution coloring. > if the first block fails, it does not turn red and stops running, > instead the block is still green. The script has found that execution has > failed but this message is not properly passed to the gui interface to turn > red showing error. > How did the execution failed ? > > Points 3&4 are gui related issues: > 3. We want to know where to specify the aviata window location and size > from the code because it blocks other window and we want the window to be > at specified places. > I need to commit something regarding this change. You can specify the height and width with following parameters [-width width]" + " [-height height]" and I need to do a commit to specify the location of the left top corner cordinates.. by default it is 50,50. You can configure it with --x and --y arguments. I committed this code to 0.3 branch please take svn up and update and build new xbaya jar. > 4. Still the the input window to launch the workflow from gui, we think > is too large and ok button in the bottom is not visible by default. > Currently, we set non-editable one to be grey and that takes two much > space. > What solution are you suggesting ? Lahiru > > > Thanks > > Ning > > > -- System Analyst Programmer PTI Lab Indiana University
