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


Hi Hassan,

you are very welcome to work on this topic. The idea was described at 
https://design.blog.documentfoundation.org/2016/07/31/how-the-navigator-may-support-object-handling-in-libreoffice-draw/
 for Draw but it would be similar for Writer (as stated somewhere in the blog post). It is also 
listed in short at http://pad.documentfoundation.org/p/UX-GSoC_Ideas #7. Your mentor would be 
Bjoern Michaelsen, he is known as Sweet5hark on IRC. Ideally you get in contact with him and prove 
him that you are able to do the work, as Tomaz said. If all signs are green we should figure out 
what features are needed in detail and what can be done during this GSoC session.

Looking forward to get you on board,
Heiko

On 03/08/2017 03:20 PM, Hassan Ali wrote:
Sir,
  I am interested in working on Navigator feature  for google summer of
code. Kindly brief me about the project so i can start working on it as
soon as possible.

Regards,
Hassan Ali


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


-- 
To unsubscribe e-mail to: design+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/design/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.