[Kolab-devel] Android client (Re: How to get involved?)

[Bernhard Reiter]

Am Montag, 11. Januar 2010 22:49:17 schrieb Gunnar Wrobel:
>   1) having a local Kolab client on the android
>   2) using a web based Kolab client
>   3) Synchronize the data with the server
>
> For 1) the easiest choice would be to look into Kontact: Can you  
> compile it for the android and run it there? Which fixes might be  
> needed to get it running? Kontact is by far the most tested and  
> feature rich Kolab client out there.

Am Dienstag, 12. Januar 2010 07:48:42 schrieb Sascha Deutschkron:
>  Yes, I plan to write a local Kolab client for Android.

So the technical subchoice is: Do you want to base it on KDE Kontact,
which is the current leading Free Software Kolab client or do you want to base 
it on a different piece of software?  

If you aim for KDE Kontact, the next step is to see if you could get Qt ported 
to Android. So far I've heard (not confirmed my self) that this will be 
difficult, but not impossible, e.g. see 
http://www.kdedevelopers.org/node/4070 . Android apparently uses a Java based 
GUI. It well may be too much for a single developer. But if you get Qt ported 
on Android for good, you are certainly almost done and have a good result.
To go this road you would need to actively try to seek other people to take 
part of the load of porting Qt.

The other road is to pick any capable IMAP email client which already is Free 
Software and more capable with the Android Java GUi and extend it.


Best Regards,
Bernhard

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20100112/c291e528/attachment.sig>