osworkflow / docs / 4.3 Workspaces.html

<html>
    <head>
        <title>4.3 Workspaces</title>
	    <link rel="stylesheet" href="styles/site.css" type="text/css" />
    </head>

    <body>
	    <table class="pagecontent" border="0" cellpadding="0" cellspacing="0" width="100%" bgcolor="#ffffff">
		    <tr>
			    <td valign="top" class="pagebody">

				    <ul class="star">
<li> Back to <a href="4.2 Quick Start Guide.html">4.2 Quick Start Guide</a></li>
<li> Forward to <a href="4.4 Palettes.html">4.4 Palettes</a></li>
</ul><br/>
A workspace in the designer is any collection of workflows. A workspace is a convenient grouping that allows you to work on multiple workflows at a time. It is somewhat analogous with a &#039;project&#039;. All of the files associated with a workspace are created in the same directory as the master configuration file, which is why it is strongly recommended that when creating a workspace, you do so in an empty directory.<p class="paragraph">In terms of implementation, a workspace is a type of WorkflowFactory, in that it knows how to load and save workflows, as well as providing extra functionality to handle the storage of workflow layout data.</p>

				    
			    </td>
		    </tr>
	    </table>
    </body>
</html>
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.