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

The developers are slowly re-writing much of the coding that use JAVA and "converting it" over to Python-based - or so I have been told. Many of the extensions are JAVA based, so we will not be free of having to install/run a JRE with LO for some time yet.

I really hate it when people find coding that is still in the files that are no longer used but never removed. Then there are those developers that never document their work at all or to the point where someone else can understand what is going on with that part/block/module of coding. When I was a mainframe programmer, your could get fired if you did not document your work properly. They did not want to have any problems with one person writing the code and a different person understand what is going on so they can easily make modifications.

Every programming language class I had, for 2 programming degrees, taught "proper" documentation and you we in trouble with the teachers if you did not do it.

Now people are our of the classroom or out of the business environment, so they seem to forget that you need to ALWAYS document your coding and your modifications to existing code. It is a real pain when you see documentation for code that does not exist anymore because it was modified and the person did not update the documentation/comments in the file to reflect those changes.

My problem, sometimes, was writing more documentation/comments in my code that was needed. I explained EVERYTHING.

On 10/19/2012 11:16 AM, Joel Madero wrote:
I would say the code is "getting better". I've only been on the project a
few months so I can't say how much progress we've made but I know that we
still have a build time of 4+ hours which says a lot. The code is still a
bit tricky, not enough comments left by previous developers, etc...

Also, I would argue that "our project" (meaning LibO, we don't use LO ;) ),
is quite small still. We have a very small team of developers who routinely
(>1 patch per week) contribute, a slightly bigger team that submits at
least one patch a month, and then a couple hundred that have submitted 1 or
2 patches in the course of several months (this includes myself ). We could
probably double our number of developers doing 1 patch or so a month and
still be in need for quite a few more.


On Fri, Oct 19, 2012 at 8:11 AM, Tom Davies <> wrote:

Hi :)
Just one thing.  LO is not particularly small and it's definitely not
new.  The original code was called Star Office and was developed around a
decade or so ago.  After a couple of years Sun took it on and called it and then TDF took the code and called it LibreOffice.  So
there are probably chunks of the code and ways of doing things that date
back to the last century!  Hence why you still see references to "soffice"
if you look in your task-manager or systems processes.

Now that a lot of the old irrelevant comments and stuff have been almost
cleaned out (allegedly) it might be possible to focus more on streamlining
and using more modern approaches in some areas.  It should definitely be
easier to find your way around the code and i think that is going to have
some big impacts on the effectiveness of any work done by the devs.  The
Pita stuff is nearly done.  Time for some fun!  (or have i got it wrong
Regards from
Tom :)

*From:* Joel Madero <>
*Sent:* Friday, 19 October 2012, 14:53

*Subject:* Re: [libreoffice-users] ... not working ...

On 10/18/2012 11:11 PM, rost52 wrote:
This is a very interesting information. I am not really surprised by the
ration indicated here. I exepcte finding the cause of a bug takes much more
time than final fix. I am grateful to the dev because I know myself how
difficult it is to find a bug in a complicated SW.
Question: What means:
- bot lists
In IRC (chat client) we have automatic robots that routinely (ten's of
times a day) say what patches have been submitted to gerrit (the service we
use to keep our code). Every time a patch is submitted the robot (bot)
spits out an automated message saying that a person (with a name) has
submitted a patch and explains what that patch does.

FDO = free desktop . org (f d o). Ans is where you can report bugs
pertaining to the libreoffice project. If you want to see a list of
confirmed bugs look here -- you'll see immediately how overwhelmed a small
project can get:

That is 3,956 bugs and climbing (there are an additional 1,200 or so that
are reported but not confirmed yet...the QA team confirms the bugs so
developers can focus on coding)


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

For unsubscribe instructions 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.