Hi. On Tue Feb 19 11:54:47 2013, Paolo Di Tommaso wrote: > What do you mean by "machine readable command line argument > description". The idea is exactly as you said, the client takes any > native T-Coffee command line options, and execute it on the server > side. When it terminates, collects the result files and send them back > to the client.
what i mean is, can I get an xml description of all the command line options ? > The only requirement is to prefix input file arguments with the > "file:" string, doing that the client takes care to upload them in the > scratch folder where T-Coffe will be execute. ok. That's good to know - although with Jalview I try to avoid creating files on the client side if possible. Incorporating the client would be a good summer project for a student - want to propose it as a google summer of code project ? Jim. _______________________________________________ Jalview-dev mailing list [email protected] http://www.compbio.dundee.ac.uk/mailman/listinfo/jalview-dev
