On Wed, Mar 25, 2009 at 11:04, Andrew Gibson <[email protected]> wrote: > You could put these files in a /tmp directory in $Taverna_home which > would be detected by taverna at startup, which would then ask you if you > want to apply unsaved chances or something?
That's the best idea so far! We've wanted to do serialisation of the edit history anyway.. and then as Alan suggested optionally even including it in the workflow itself. (It would be the provenance of making a workflow) With the tmp-solution you could re-open a workflow the next day in a fresh Taverna, you can start undo-ing (on your own machine) - however if you send the workflow to someone they won't have the edit log, and can't see your (possibly embarrassing) mistakes done in the earlier life of developing the workflow. Supporting this would require making all the edits serialisable, so it would take .. well.. I would guesstimate 2 weeks of effort. Alan - should we put it in the Jira machine? :-) -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ taverna-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/taverna-users Documentation: http://www.mygrid.org.uk/usermanual1.7/ FAQ: http://www.mygrid.org.uk/wiki/Mygrid/TavernaFaq Biological Services: http://www.mygrid.org.uk/wiki/Mygrid/BiologicalWebServices
