CmisSync for Mac!

[Nicolas Raoul]

CmisSync is now available for Mac!

You can now synchronize between Alfresco/Documentum/FileNet/SharePoint/etc and your Mac.
- Automatically downloads/uploads changes
- Allows you to work even when offline
- Smart conflict resolution

This is a beta version, with the following bugs remaining:
- No activity indicator when downloading
- Japanese: Mac OS X transforms パ (1 character) into ハ゜ (2 characters)

- Please report any other bug

Don't hesitate to use it, we are waiting for your feedback at Cmis...@aegif.jp
As for the Windows version, professional support is available from Aegif at 120USD per user per year, please contact us at the email address above to learn more :-)

Cheers!

Nicolas Raoul

Aegif

[surya]

Hello Nicolas,

I want to try Cmisync on Mac. I downloaded the beta version but not able to connect to our organisation's 'sharepoint' site.

Could you please help me out with this.

Thank You

Surya

[Ray Saunders]

Hi Nicolas,

Accented characters in French in filenames blocks sync from Alfresco. Hope this can be fixed soon. It's a bit of a surprising show-stopper for us as we have two official languages (English and French) so we have many files in our repository named with accented characters. Macs normally handle such matters with consumate ease!

Otherwise, first impressions are quite positive. We have been able to invoke a few crashes (e.g. A user who tried renaming a folder inside CmisSync folder while CmisSync was running.) It also seems to want to download an additional lib file from OS X Developer Tools at some stage but I haven't identified the precise trigger for that yet.

Hope you can help with the accented characres in filenames, though. It really would help us to have a dropbox style application like this for Alfresco.

Ray

[Nicolas Raoul]

Hello Ray,

Thanks for your feedback!

1) Accents: Yes, Mac corrupts unicode filenames, so we have to keep a local-remote mapping. We are implementing this right now.

2) Sorry about the crash! If you manage to find how to reproduce it, please let us know!

3) We have heard this OS X Developer Tools thing from a client, we will soon start working on it. In any case, OS X Developer Tools is NOT needed to run CmisSync.

Thanks for your patience, and thanks for using CmisSync!

Nicolas Raoul
Aegif

--
You received this message because you are subscribed to the Google Groups "CmisSync" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cmissync+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ray Saunders]

Hi Nicolas

Many thanks for your response and sorry to be so delayed in responding.

1. I thought the Mac uses unicode natively so I'm surprised to hear this!

2. Not repeated yet but I haven't used it much since we need the accented characters to be able to "go-live" with our users.

3. I will be very happy to test pre-release betas for you, if that helps. (I did much the same for Patrick Luby and NeoOffice development in its earliest days. When I see a project addressing a core need for our organisation, I'm ready to help with its fruition. Your CmisSync will help us to leap forward with desktop integration for our Alfresco community edition server.

Thanks for your efforts and I look forward to progress generally.

Ray

[Nicolas Raoul]

Hello Ray,

As you probably know, our betas are here:
https://bitbucket.org/aegif/cmissync/downloads

We have released the latest Mac beta 2 weeks ago.

Thanks a lot for testing CmisSync!

Nicolas Raoul
Aegif

[Ray Saunders]

Hi Nicolas,

Thanks for the link. Latest beta downloaded and installed successfully.

Of course, this version doesn't address the unicode characters in the filename bug. As soon as we have that fixed and colleagues installing CmisSync on Mac, I think it should be relatively easy for me to persuade a good number of my colleagues across the world to help with your translation request: we have five official languages but a multitude of other native languages across our 120+ staff in around ten cities worldwide.

Thanks for your support,

Ray

[Moritaka Soma]

Hello Ray

We released CmisSync for OSX 1.2.12 beta.
It's includes fix of reported unicode character problem.

Please download software from following url.
https://bitbucket.org/aegif/cmissync/downloads/CmisSync-1.2.12.0beta.dmg

Thanks a lot for testing CmisSync!

Moritaka Soma
Aegif

2014年8月23日土曜日 4時32分43秒 UTC+9 Ray Saunders:

[Ray Saunders]

HI,

Just back from vacation. Tested on 2 separate computers and still unable to download files with accented characters in file names.

"Given filename contains illegal patterns" in log entries.

So, I'm not seeing any chane with this release.

Sorry to be the bearer of bad news but thanks for your counting efforts to resolve this problem. It is much appreciated and I look forward to the  breakthrough, when it comes.

Ray

[Nicolas Raoul]

Hello Ray,

Could you please send us the log file, or at least a ~50 lines part showing the message?

Thanks a lot for the feedback! :-)

Nicolas Raoul
Aegif

--

[Ray Saunders]

Attached.

The French accented characters in filenames are broken out as the unaccented character followed by a "?". Thus système becomes system?me etc.

Trust this helps. I'd be happy to exceptionally organise a temporary access to our server, if necessary, to help you overcome this problem. that's how important I consider tho issue to be for us. It will be great to get this fixed so we can really benefit from your efforts in a multi-lingual environment.

With kind regards,

Ray

[Nicolas Raoul]

Hi Ray,

Thank you for the log file!

Interesting.

Could you please install the free open source tool "CMIS Workbench" and use it to connect to your server, up to an accented file, open its properties fullscreen, and send us a screenshot? (or 2 if it does not fit)

http://chemistry.apache.org/java/developing/tools/dev-tools-workbench.html

Thanks for your patience!

Nicolas Raoul
Aegif

--

[Ray Saunders]

Hi Nicolas,

Sorry to have been out of touch for quite so long but I was heavily committed to other work these last weeks.

Anyway, it looks as though we may have resolved the particular issue and it was on our side. The files concerned were incorrectly named and contained characters that Alfresco itself was unable to display, as revealed through CMIS Workbench. So it was not a character substitution in transit issue as I originally believed.

I'll now get back to testing CMISsync a bit more closely and hopefully we'll be able to deploy it shortly ourselves.

Thanks for your support, your patience and a nice little implementation.

Ray