Subclipse workflow clarification
===

I have been using TortoiseSVN for a while now and just recently started using the eclipse plugin **subclipse**. I am really happy with it, although there is some stuff confusing me. 

I have a few projects, which each have a different subfolder in the repository. I never worked with branches (so far), so my SVN use was fairly easy.

 1. Update to head
 2. Solve conflict if there are any
 3. Make some changes in the code/project
 4. Commit (Tortoise tells me, if an update is neccessary before)

Now with subclipse, I fell that there are other possibilities. For instance, what's with the synchronize view? I don't really get it. At the moment, I use `Team->Update to head/Commit` on the project folder and if there are conflicts, I use `Team->Edit conflicts...` on the conflicted file. That's it. So I never touch the synchronize stuff. I haven't really found a good explanation on the subclise page or google...

Is the idea to just synchronize and everything is done automatically or what?

Basically, I am asking for the workflow (or some link to a good basic explanation). I am not asking, what is possible or what does what, but how subclipse is **intended** to be used for small projects (<100 files, <5 persons working on it, no branches so far).