Re: [libreoffice-users] Re: resolved (Re: getting LO source)
On 11/09/2017 05:28 PM, Alexander Thurgood wrote: > Errm, seriously, not really, other than perhaps just focussing on one area of > the code. :( > thereby making it difficult to have increasing in-depth knowledge and > insights. That knowledge kind of tends to be assumed. Not to mention that there used to be a great set of developer documentation. I didn't grab it back when it was available, thinking it would always be available, and today it is nowhere to be found. > I would probably need several lifetimes to become proficient enough in > programming in C++ At least it isn't APL. I'm delving into the "expert configuration" in ">Tools >LibreOffice >Advanced >Open Expert Configuration", trying to figure out how to get LibO to behave the way I want it to. And to find out what those options do, I have to study the source. jonathon -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: resolved (Re: getting LO source)
On 11/09/2017 12:28 PM, Alexander Thurgood wrote: > Le 09/11/2017 à 16:30, jonathon a écrit : > > Any pointers on how to minimise the pain of reading the code? > > Aspirin ;-) May the source be with you. ;-) -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] Re: resolved (Re: getting LO source)
Le 09/11/2017 à 16:30, jonathon a écrit : Any pointers on how to minimise the pain of reading the code? Aspirin ;-) Errm, seriously, not really, other than perhaps just focussing on one area of the code. I tend to mostly focus on the database stuff, and have recently started looking at memory leaks with the aid of Instruments.app on MacOS, which does facilitate somewhat the fingerpointing and blaming game for the bits of code it considers "wrong". Not that it always gets it right mind. With the database code, I started occasionally perusing the driver classes when I was still using OpenOffice.org and trying to understand how they were constructed and how they were intended to function. I held the vain hope of developing my own driver class at the time (but for which db backend I fail to recall now), realising very quickly that it was out of my league, so I just kept opening up the cxx files and scrolling through them, and then forgetting most of what I'd found interesting as soon as I'd closed it. At the time, I was also subscribed to the dba mailing list for OpenOffice.org where the devs from Sun frequently intervened to explain this or that function, and parts of the API. Unfortunately, the dba code side of things is heavily undersubscribed in the behemoth project that is LibreOffice today in terms of human investment, there is but one dba code caretaker who has a dayjob other than helping out with LO, and a few other occasional committers, mostly people working for Linux distros to fix bugs, or GSOC-ing, thereby making it difficult to have increasing in-depth knowledge and insights. That knowledge kind of tends to be assumed. I would probably need several lifetimes to become proficient enough in programming in C++ to be able to even dream of understanding each time what is going on. I'd say, even with the amateur knowledge I have currently, it has taken me more than 10 years of repeated blank staring at lines of code to even start to comprehend, sadly... Anyway, we are seriously digressing from the initial topic, so I'll stop here... Alex -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: resolved (Re: getting LO source)
On 11/09/2017 09:04 AM, Alexander Thurgood wrote: > As a non-developer trying to read the code for bug hunting, it has given me > migraines on many an occasion. Any pointers on how to minimise the pain of reading the code? jonathon -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: resolved (Re: getting LO source)
On 09/11/17 09:04, Alexander Thurgood wrote: Le 08/11/2017 à 10:52, Mike Scott a écrit : Hi Mike, Having established it would build and run (with the same video problem, incidentally), I finally looked at the sources. Now I begin to see why changes take so long not a comment in sight for one thing, and a spider's web of complexity. Sheesh! Nightmarish. The lack of significant comments stems from the original source code of OpenOffice.org when it was released, which itself came from StarOffice (after Sun bought the code). Most of the existing comments at the time were also in German, and particularly concise or absconse. Unfortunately, at least for the occasional person wanting to dive into the code, heavy commenting does not seem to be widely adopted amongst the currently active open source developers contributing to the project. One might also bear in mind that the LibreOffice code base is huge - certainly larger in lines of code than any other current open source project. As a non-developer trying to read the code for bug hunting, it has given me migraines on many an occasion. Thanks. I'd forgotten the original would have been German (and StarOffice was actually my first foray into a 'proper' WP -- iirc Sun were giving it away at the time.) Probably time this thread died off, the 'source' issue being resolved and purely down to my failure. I've started another thread on the particular video issue I'm concerned with. If anyone can shed light there to help getting it resolved, I think not a few users would be grateful! Thanks again to all who've replied here. -- Mike Scott (unet2 [deletethis] scottsonline.org.uk) Harlow Essex England "The only way is Brexit" -- anon. -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] Re: resolved (Re: getting LO source)
Le 08/11/2017 à 10:52, Mike Scott a écrit : Hi Mike, > Having established it would build and run (with the same video problem, > incidentally), I finally looked at the sources. Now I begin to see why > changes take so long not a comment in sight for one thing, and a > spider's web of complexity. Sheesh! Nightmarish. > The lack of significant comments stems from the original source code of OpenOffice.org when it was released, which itself came from StarOffice (after Sun bought the code). Most of the existing comments at the time were also in German, and particularly concise or absconse. Unfortunately, at least for the occasional person wanting to dive into the code, heavy commenting does not seem to be widely adopted amongst the currently active open source developers contributing to the project. One might also bear in mind that the LibreOffice code base is huge - certainly larger in lines of code than any other current open source project. As a non-developer trying to read the code for bug hunting, it has given me migraines on many an occasion. Alex -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
