[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [geclipse-dev] Minutes of the JSDL meeting from today
|
There may be another - very simple - solution.
Since the INPUT type implies that source location will be provided and for
OUTPUT - target location, I propose to redesign the table layout to 3
columns: source location, name, target location. Attached image will hepl
to understan this idea.
Dnia 17-05-2007 o 13:41:51 Pawel Wolniewicz <pawelw@xxxxxxxxxxxxx>
napisaĆ(a):
On Thu, 17 May 2007, Katarzyna Bylec wrote:
The problem is that for now user can only specify INPUT and OUTPUT
files (providing their names and locations). On JSDL meeting we decided
that it would be nice if they will also be able to choose INPUT/OUTPUT
type of file. But for INPUT/OUTPUT user has to specify 2 locations
(source and destiny/target)
For me the type INPUT/OUTPUT means, that the file should be transfered
from storage location to WN before job starts and from WN to the same
storage location when the job is finished. If user wants to get the
INPUT/OUTPUT file back to different location then it should be splited
to two entries. INPUT from location 1, and OUTPUT to location 2.
But I think that we can skip the type INPUT/OUTPUT (at list for now).
There are usecases and applications, where file is transmitted to WN,
updated by application, and transmitted back, but they are not so
common. And the same functionality can be achieved by defining two
separate entries, INPUT and OUTPUT.
Pawel
_______________________________________________
geclipse-dev mailing list
geclipse-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/geclipse-dev
--
Katarzyna Bylec
Attachment:
NewWizard.JPG
Description: JPEG image