Courtland; The Eclipse platform that Composer uses allows you to create links to projects outside of the main workspace. So a suggestion would be to create a workspace in on a local machine. Particularly, make sure all of the TopBraid system projects are on the local disk - those in the projects named TopBraid, server.topbraidlive.org, etc.
Then you can use Import > General > Existing Projects into Workspace to create a link to the projects on the thumb drive. Make sure you do *not* check 'Copy projects into workspace' in the wizard. This could get you some relief from the slowness, but it will never be quite as good as from a local disk. -- Scott On Oct 8, 3:05 pm, ceyockey <[email protected]> wrote: > Hello - I have found recently that switching workspaces and creating new > workspaces has been quite slow. I know that one contributing factor is > that I am using a memory stick to store the workspaces, but it does bring > the question of whether we can identify a subset of the full document set > which Composer copies into each workspace as a minimal base to work from? > What would you recommend as the best way to do this? --courtland.yockey > > (About why I am using a memory stick - it is my understanding that there is > some file management issues on Windows file system in regard to workspace > content so that deletes are not completely clean; I'm using a memory stick > to isolate potential problems away from my main hard drive.) -- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
