At 3:12am -0400 Tue, 26 Oct 2010, Cedric Bosdonnat wrote:
On Mon, 2010-10-25 at 13:44 -0400, Kevin Hunter wrote:
For a project as large as LibreOffice, you may also more appreciate
the use of an IDE (Integrated Development Environment). Eclipse is
often touted to me, as is Geany, and KDevelop.
Did you ever tried loading the sw module sources in Eclipse? it may
be possible, but you'll have some memory troubles and slowdowns with
the indexing.
Have I with LO? No, not yet. But I've only just started with the LO
codebase. No offense intended, but I will try it myself first.
Software (and hardware!) configurations can vary wildly even within a
single distribution, meaning that where one developer struggles, another
might have great success.
A combination of Vim/Emacs and ctags is great and much quicker. I'll
try to cleanup and push my vim configuration somwhere for others to
download.
In response to the original question, I intentionally kept a very even
keel about the editors/IDEs available. Though I personally can work
well in a number of environments, I also have my preferred environments
for certain situations and code bases. Coding is such an individual
activity (outside of XP of course), that I think it foolhardy to push
one's environment as "the best".
In this vein, I standby my original statement:
"Picking the right programming environment is often a never-ending
journey, but certainly not one that someone else can choose for you."
Regards,
Kevin
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.