This tool can really get on your nerves

This tool can really get on your nerves

Hi there,

today, I spent two hours in vain editing text in ZoHo Writer. The first hour was in a train, where I used the offline feature of the writer. When I had an Internet connection again, I tried to sync which apparently went right (that's what the GUI pretended at least). However, back online I saw an old version that had been edited in parallel and my version work (done offline) was gone. When trying to synchronize, it told me both the online and my version were changed so it would create a new version with my changes. But that version never made it into the history list :-(

The next time I was editing in online mode. I locked the document because it is more convenient to edit then (no one else was edtiting it). So I started working (re-doing my work from the train) and saving regualarly. It on each save, the browser would first frees for 15 seconds, then the spinner in the tab would appear and about 1 minute later, the notification on the lower right would appear and tell me the doc has been saved. I did this about 20 times (during another wasted hour). When I was finished, it wanted to make sure that everything had really been saved by going to the history view. I was shocked to see that the latest verion in the history was still the one edited by my colleague some hours ago. I went back to "edit" and yes, everyting was lost again.

Honestly guys, unreliably is one thing. It's still beta and one expects it. But this pretending of your GUI code, that everything goes fine is really not the way it should be. Is this so hard to control in the browser environment? Can't you do an extra acknowledgement cycle with the server? I mean saved should be saved, shouldn't it?

Don't get me wrong - the idea you had with this tool is and will always be great. But you are far away from a tool that can be used in a productive environment - sorry for having to tell you.

Regards,
Patrik
patrik_spiess_sap