Local Workspace

Previous Next 1 2 3 4 5 6 7 8 9 10

Firefly implements Local Workspace, an isolated, private work environment sitting on your local hard drive, with the files you need, waiting for your command. Local workspace is not our innovation. In fact, private workspace has long been a common practice to manage changes and obtain consistent environment. It is so common that it is often overlooked. Having a local workspace means having a copy of all the files you need for development. Doesn't that also mean local workspace eats more disk space than working with shared source? Yes it does, but the benefits and simplicity of it is more than worth the megabytes it consumes.

First up it gives you total control. When you work in a local workspace, you control the versions of code and components you are working on. You will have total control over when and how your environment changes.

Then there's safety. A local workspace isolates your work from others. Your work will not be affected by outside changes as long as it is in your local workspace. In turn, your work will not affect other developers. So if anything goes wrong, you won't be a victim or you won't cost a disaster. You will work in your private sandbox to modify code and run unit tests. In other word, you will have a safe place to do your work, and test them and make sure everything is ok before you merge the changes back to the stream.

And local workspace allows you to work in offline mode. You can setup a local workspace on your laptop and take all your work on the go. You check files out in offline mode on the road, edit them and delta them. All history will be recorded and ready to be transferred to the server. When you come back to the office, all change will be submitted to the server. And history entries will be multiple if you delta-ed more than once.

Previous Next 1 2 3 4 5 6 7 8 9 10