Demo is online

[cabeza]

A demo installation of OpenGoo 0.6.6 is online. Just visit http://demo.opengoo.org and login using 'demo' as username and password.
Enjoy it ! Ans please continue sending your feedback!

[stenyak]

Awesome, thanks.

Minor bugs:
- Concurrent edition of documents is not warned, last person saving overwrites the others' changes.
- When adding a new contact, and adding a company, the company list is not automatically refreshed, so it doesn't reflect the newly added compeny.

Are there plans for concurrent edition (a la google docs), and spreadsheet support?
Thanks!

[ignacio]

Hi stenyak!

First, thanks for the bug reports! The one about the contacts has already been fixed and will be out on next release. The other one, you are right, it should warn you or directly not allow you to edit it when someone is editing. Now there's the possibility to checkout the document so that no one else can edit it while you have it checked out. Maybe that should be done automatically always when editing the document. We'll think about it.

We do not plan to support concurrent editing in the short term. The editor we are using now is an open source text editor called FCKEditor, and it doesn't support concurrent editing. We would need to work on our own specific editor or alter FCK and we don't have the time availability to do that yet.

However, we plan to support spreadsheets soon, maybe in a couple of months, and since that component is being developed by some members of the OpenGoo team, we plan to support concurrent edition for spreadsheets.

Cheers

[stenyak]

The other one, you are right, it should warn you or directly not allow you to edit it when someone is editing. Now there's the possibility to checkout the document so that no one else can edit it while you have it checked out. Maybe that should be done automatically always when editing the document. We'll think about it.

May i suggest the use of some merging tool? If no conflicts are found, automatically merge the changes. If conclicts are found, ask whether to rewrite the version of the other guy, or revert to his version (cancel one's changes).

Ideally, a versioning tool like svn/mercurial could be used... since there's already a filesystem storage backend (not just db backend). Just some suggestions :-)

[cabeza]

Thank you stenyak.
We will consider it for the future.