[Kolab-devel] Fwd: Re: Questions about tags and description of notes

[Ing. Konrad Renner]

Hi,

you are right with the point, that a central library can help to have a correct implementation of a specification. But as stated before, I am afraid that the bindings are not maintained in the future (eg like qt-jambi). Beside this "fear" the bindings are JNI wrappers, maybe with Java 9 (there is JEP #191) it is possible to call native libs without such wrappers and then, the usage of this libs can be reevaluated from me.

I know the SyncKolab project, unfortunatley the implementation of the Kolab specificas and the Android clue code was not separated. My lib is separeted from the Android code, so it is also able to use in any Java application. Also it is easily possible to fork the app and use instead of my library eg the JNI wrappers.

But of course I will have a look on the bindings.

One last thing: You guys are doing a great work! Thank you for creating such a cool product and making the code and specifications available for everyone!

Kind regards,
Konrad

Am 20.05.2015 3:52 vorm. schrieb Torsten Grote <torsten at kolab.org>:
>
> Hi Konrad, 
>
> On Tuesday 19 May 2015 23:27:06 Ing. Konrad Renner wrote: 
> > where do I find those bindings? Are they available via Maven central vor any 
> > other "Maven compatible" repository? 
>
> Unfortunately, they are not directly available as a Java library. 
>
> The Java bindings are generated with SWIG and directly part of libkolab. 
> Here's an article I found on the subject: 
>
>     http://www.swig.org/Doc2.0/Android.html 
>
> > I use Maven and Gradle as build/dependency systems, so it would be nice if 
> > it is available through such a repo. 
>
> That would indeed be very nice and make Kolab related Android development a 
> lot easier. 
>
> > I have made very often negative experiences with such bindings (normally 
> > they are created with JNI, which really sucks). They are very often 
> > "stepchilds", thats why I wanted to create a pure Java lib. Java has really 
> > great XML support, so adopting code because of changes in a xsd is easier 
> > than be dependent on a binding which is maybe some versions behind. 
>
> I see your point. However, having only one implementation that multiple people 
> use where issues can be fixed centrally also has advantages over several 
> implementations that all develop their own issues. The developer of SyncKolab 
> also thought it would be easier to just write his own implementation and this 
> still has many issues today. 
>
> > I like Android because it builds on Linux and Java, I really like to code 
> > with Java, so C/C++ was no alternative this time for me ;-). 
>
> You wouldn't need to code in C/C++, that is the idea of the Java binding. You 
> just use them with Java from Java. 
>
> Kind Regards, 
> Torsten 
>
> -- 
> Torsten Grote 
> Kolab.org Community Manager 
>
> e: torsten at kolab.org 
> w: https://Kolab.org 
>
> pgp: 0x2175A534A4F2EFA3