GSoC Summary

-
Working with Lireoffice during GSoC has been a great learning experience. It has helped me get better at C++ and taught me how real world applications are built. I also spent most of my time at the debugger rather than writing code which has helped me improve my debugging skills. It also taught me what a great tool git is for managing commits and has been helpful in more than one occasion.

 My mentors, and the Libreoffice community has been very helpful and have guided me whenever I got stuck. It feels good to be a part of such a great community.

Below is a list of tasks that was done as part of the GSoC project and also a list of tasks that I wanted to, but could not finish during the period.

Work Done

  1. Added Data Transformations

    1. https://gerrit.libreoffice.org/#/c/58152/ 
    2. https://gerrit.libreoffice.org/#/c/58151/ 
    3. https://gerrit.libreoffice.org/#/c/56886/ 
    4. https://gerrit.libreoffice.org/#/c/56862/ 
    5. https://gerrit.libreoffice.org/#/c/56780/ 

  2. Added Base as a Data Provider (Unmerged) 

    1. https://gerrit.libreoffice.org/#/c/57447/

  3. Added XML as a Data Provider 

    1. https://gerrit.libreoffice.org/56356 

  4. Export Data Transformations to ODF 

    1. https://gerrit.libreoffice.org/#/c/56665/
    2. https://gerrit.libreoffice.org/#/c/57217/
    3. https://gerrit.libreoffice.org/#/c/58254/

  5. Import ODF with Data Transformations 

    1. https://gerrit.libreoffice.org/#/c/58258/
    2. https://gerrit.libreoffice.org/#/c/58258/ 

Todo

  1. Add UNO Interface
  2. Encrypt credentials for data providers
  3. Manage column headers for imported data

Comments

Post a Comment

Popular posts from this blog

Debugging LibreOffice with GDB

-
Getting started To debug LibreOffice with GDB you need to build LibreOffice with debug symbols. You can either choose to build LO with symbols for the entire project or for selected modules. For building with symbols for the entire project you can use ./autogen.sh --enable-debug For building  with symbols for specific modules ./autogen.sh --enable-debug --enable-selective-debuginfo = "sc/"   More information for setting up GDB can be found here How to debug . Setting up pretty printers Basics Debugging boils down to the following set of actions: Set up a break point Run the program Step through the code Analyze the variables as you go Handling Crashes while debugging The most common reasons for crashes are either an exception occurred or an assertion failures. In case of Exceptions, you can stop GDB at the point where the exception occurred by setting up a breakpoint using catch throw and then analyze the backtrace (generated using bt ).
Read more

Speeding things up

-
I work on an Ubuntu machine with 4GB RAM and Intel i5 processor. Every time I perform a build or run the debugger, the entire system slows down to a crawl making development slow and tedious. Hence I started looking for ways to speed up my system and came across LXDE desktop environment. Being lightweight, it consumes very less system resources. I was amazed at the performance boost I experienced and it sped up my code, build, debug cycle. If you are experiencing difficulties due to a slow system, I recommend switching to either LXDE desktop or using LUbuntu which comes natively with LXDE.
Read more