Re: [tools-dev] OOo source split

[Rüdiger Timm]

Jan Holesovsky wrote:
Hi Ruediger,

I am sorry, I missed a part of the mail when I was answering previously :-(

No problem.


On Monday 08 October 2007 17:36, Rüdiger Timm wrote:

This would tremendously decrease the learning curve for the new
developers as well.  Imagine someone who wants to start hacking on Calc. 
Instead of the monster 1.8G sources, he would have to handle 512MB. 
Additionally, the goal
How should that work with your proposal? He would need everything
'below' calc.

Yes, but do we provide an easy way to show him/her what _exactly_ is below 
calc?  I was overwhelmed when I saw the number of the modules for the first 
time [and there was much less of them at that time ;-)].  With the split, 
everything is much clearer - my ideal newcomer would tell himself/herself 
"OK, here is some bootstrap stuff, I don't care, some libs, maybe, but what I 
want is to hack on calc, so ooo-apps-calc.  If I ever need something below, 
I'll learn that later."

If that really is his desire, nowadays he just needs a wiki page telling 
that 'calc' basically is module 'sc'. Than check out 'sc' and start hacking.

Learning OOo is hard, no doubt. I just do not think that splitting souce 
code archive would make it any easier.


Except he uses, what we provide anyway: download 'solver' 
tarball and than check out just module 'sc'. That's exactly for the
purpose you mention.

Well, if the potential contributor has to learn what is that 'solver', we 
again increase the learning curve.  And using it?  I tried it once when I 
started with OOo hacking (as a volunteer), and after having to have the same 
compiler & toolchain that was used for the solver generation, I just gave up 
and let my computer building for 24 hours.

OK, on unix you are right. May be we should restrict providing 'solver' 
for windows. At least on linux it does not really make sense, as there 
are so much different toolchains possible.
The idea may be good, but in practise ...


[...]

So I would propose existing and well tested means to achieve 
nearly the same goals. F.e., the build tool provides a possibility to
build distributed on several computers.

May I ask for a documentation/wiki pointer, please?

http://tools.openoffice.org/servlets/ReadMsg?list=dev&msgNo=6214
and replies to that mail.


addition to the few modules) all the localize.sdf's - should we split
this a bit as well?
There already is work in progress on taking localize.sdf files out of
the modules and concentrate them in one place.

Great, whom to ask about this, please?

Ivo (ihi). Ause also is involved, I think.
See also
http://www.openoffice.org/issues/show_bug.cgi?id=79750
http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fl10ncleanup


Rüdiger

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]