> Date: Thu, 07 Jan 2010 15:45:43 -0700 > From: Paul Gordon <[email protected]>
> Hi all, Hello, > Well, I guess I'm one of the few crazy people that write .t2flow files > externally of Taverna (Seahawk's export-history-as-workflow function). > Right now I create the XML by building a DOM. I will agree that it's > verbose :-) It certainly is :-) > One of the features I particularly like and use is the ability to > specify sample inputs for services, so please don't get rid of that! No that will be there. I could add it in as a specific Jira issue just to make sure if you want. > Pretty much the only boilerplate I use in creating the document is the > dispatch stack, everything else is instrumented in some way... > Having a lightweight piece of code to generate the workflow diagrams > (either via a network client or a standalone JAR) is DEFINITELY > something I'd like! That will affect the "OSGification" that we'll get started on soon. At the moment, the generation of the diagram is considered as part of the user interface code. It sounds as if it needs to be pulled out as a separate bundle. It may be worthwhile also looking at whether it can be done as a renderer. > My $0.02, > Paul Alan ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/ Developers Guide: http://www.mygrid.org.uk/tools/developer-information
