Date: prev next · Thread: first prev next last
2018 Archives by date, by thread · List index

Hi Adrian,

you are very welcome to work with LibreOffice and we try to support you by all means. Unfortunately 
your questions addresses the development and you probably won't find devs in this design mailing 
list. We mostly discuss workflow and appearance questions here, and Android is our cinderella 
anyway. Meaning the design team hasn't done much work in this area.

The better place is the dev ML where a coworker of you (?) had a similar question recently

Good luck for your exercise,

On 13.01.2018 17:08, Adrian Lopez wrote:

I am a post-degree student at the University of A Coruña (Galicia, Spain)
and we have to do a practical exercise about design in an open-source
project, and we have selected LibreOffice in order to do that.

We have downloaded the code of the project core and we would be interested
in know more about the main architectural and design patterns you are using
in the module called "android", and how do you have implemented them in the

Moreover, I would be very grateful if you could lend me some documentation
about the development methodology you are using.

Thank you very much in advance.

Adrián López Martínez
Software Engineer in A Coruña


de virus.

Dr. Heiko Tietze
UX designer
Tel. +49 (0)179/1268509

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.