You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Kay Schenk <ka...@gmail.com> on 2013/04/23 22:58:21 UTC
Is the project dependency chart still valid?
In my search to find out more about resource files (.src), I came across
the old Tools information on the web server, and specifically the project
dependency chart:
http://www.openoffice.org/tools/project_dependencies.png
Is this still valid?
--
----------------------------------------------------------------------------------------
MzK
"There's no upside in screwing with things you can't explain."
-- Captain Roy Montgomery, "Castle"
Re: Is the project dependency chart still valid?
Posted by Rob Weir <ro...@apache.org>.
On Wed, Apr 24, 2013 at 12:05 PM, Louis Suárez-Potts <lu...@gmail.com> wrote:
> Hi
>
> On 2013-04-24, at 11:42 , Rob Weir <ro...@apache.org> wrote:
>
>> On Wed, Apr 24, 2013 at 3:28 AM, Andre Fischer <aw...@gmail.com> wrote:
>>> On 23.04.2013 22:58, Kay Schenk wrote:
>>>>
>>>> In my search to find out more about resource files (.src), I came across
>>>> the old Tools information on the web server, and specifically the project
>>>> dependency chart:
>>>>
>>>> http://www.openoffice.org/tools/project_dependencies.png
>>>>
>>>> Is this still valid?
>>>>
>>> No, it is not. Some new modules are missing, for example apr, apr-util,
>>> coinmp, serf.
>>> We should create a new one. This one has probably been created with
>>> graphviz. Does anybody know of a better graphh visualization tool that
>>> produces prettier and/or better readable output?
>>>
>>
>> I use Gephi, and it is quite good:
>>
>> https://gephi.org/
>>
>> If we can get the raw data into a CSV file showing the dependencies,
>> that will import nicely into Gephi.
>
> Thanks! I hadn't been aware of this before. It's quite nice. I'm curious if they'd (or we'd) be interested in devising an extension that could utilize it as we wish. Yes, it's easy enough now, as is, but for those of us even lazier than thou….
>
It is possible. But if we wanted to add support I'd target the
GraphML format, which is understood by Gephi and other graph analysis
packages:
http://graphml.graphdrawing.org/
A simple project for a student could be an extension that exports
GraphML from a spreadsheet.
-Rob
>
> Louis
>>
>> For example:
>>
>> A,B
>> B,C
>> B,D
>>
>> This shows A depends on B, and B depends on C and D
>>
>> You can also repeat edges to give them greater weight.
>>
>> When graphing you can then scale the nodes so the ones that have the
>> highest in-degree are larges, i.e., the ones that most other modules
>> depend upon, etc. You can also color code. Of course, all this can
>> be done by graphviz as well. The beauty of Gephi is it does these
>> calculations automatically,
>>
>> Regards,
>>
>> -Rob
>>
>>
>>> -Andre
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Is the project dependency chart still valid?
Posted by Louis Suárez-Potts <lu...@gmail.com>.
Hi
On 2013-04-24, at 11:42 , Rob Weir <ro...@apache.org> wrote:
> On Wed, Apr 24, 2013 at 3:28 AM, Andre Fischer <aw...@gmail.com> wrote:
>> On 23.04.2013 22:58, Kay Schenk wrote:
>>>
>>> In my search to find out more about resource files (.src), I came across
>>> the old Tools information on the web server, and specifically the project
>>> dependency chart:
>>>
>>> http://www.openoffice.org/tools/project_dependencies.png
>>>
>>> Is this still valid?
>>>
>> No, it is not. Some new modules are missing, for example apr, apr-util,
>> coinmp, serf.
>> We should create a new one. This one has probably been created with
>> graphviz. Does anybody know of a better graphh visualization tool that
>> produces prettier and/or better readable output?
>>
>
> I use Gephi, and it is quite good:
>
> https://gephi.org/
>
> If we can get the raw data into a CSV file showing the dependencies,
> that will import nicely into Gephi.
Thanks! I hadn't been aware of this before. It's quite nice. I'm curious if they'd (or we'd) be interested in devising an extension that could utilize it as we wish. Yes, it's easy enough now, as is, but for those of us even lazier than thou….
Louis
>
> For example:
>
> A,B
> B,C
> B,D
>
> This shows A depends on B, and B depends on C and D
>
> You can also repeat edges to give them greater weight.
>
> When graphing you can then scale the nodes so the ones that have the
> highest in-degree are larges, i.e., the ones that most other modules
> depend upon, etc. You can also color code. Of course, all this can
> be done by graphviz as well. The beauty of Gephi is it does these
> calculations automatically,
>
> Regards,
>
> -Rob
>
>
>> -Andre
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Is the project dependency chart still valid?
Posted by Rob Weir <ro...@apache.org>.
On Wed, Apr 24, 2013 at 3:28 AM, Andre Fischer <aw...@gmail.com> wrote:
> On 23.04.2013 22:58, Kay Schenk wrote:
>>
>> In my search to find out more about resource files (.src), I came across
>> the old Tools information on the web server, and specifically the project
>> dependency chart:
>>
>> http://www.openoffice.org/tools/project_dependencies.png
>>
>> Is this still valid?
>>
> No, it is not. Some new modules are missing, for example apr, apr-util,
> coinmp, serf.
> We should create a new one. This one has probably been created with
> graphviz. Does anybody know of a better graphh visualization tool that
> produces prettier and/or better readable output?
>
I use Gephi, and it is quite good:
https://gephi.org/
If we can get the raw data into a CSV file showing the dependencies,
that will import nicely into Gephi.
For example:
A,B
B,C
B,D
This shows A depends on B, and B depends on C and D
You can also repeat edges to give them greater weight.
When graphing you can then scale the nodes so the ones that have the
highest in-degree are larges, i.e., the ones that most other modules
depend upon, etc. You can also color code. Of course, all this can
be done by graphviz as well. The beauty of Gephi is it does these
calculations automatically,
Regards,
-Rob
> -Andre
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Is the project dependency chart still valid?
Posted by Andre Fischer <aw...@gmail.com>.
On 23.04.2013 22:58, Kay Schenk wrote:
> In my search to find out more about resource files (.src), I came across
> the old Tools information on the web server, and specifically the project
> dependency chart:
>
> http://www.openoffice.org/tools/project_dependencies.png
>
> Is this still valid?
>
No, it is not. Some new modules are missing, for example apr, apr-util,
coinmp, serf.
We should create a new one. This one has probably been created with
graphviz. Does anybody know of a better graphh visualization tool that
produces prettier and/or better readable output?
-Andre
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Is the project dependency chart still valid?
Posted by Kay Schenk <ka...@gmail.com>.
On Mon, Apr 29, 2013 at 7:30 AM, Rob Weir <ro...@apache.org> wrote:
> On Mon, Apr 29, 2013 at 3:36 AM, Andre Fischer <aw...@gmail.com> wrote:
> > On 24.04.2013 18:41, Kay Schenk wrote:
> >>
> >> On Wed, Apr 24, 2013 at 1:36 AM, janI <ja...@apache.org> wrote:
> >>
> >>> On 24 April 2013 09:45, Oliver-Rainer Wittmann <
> orwittmann@googlemail.com
> >>>>
> >>>> wrote:
> >>>> Hi,
> >>>>
> >>>>
> >>>> On 23.04.2013 22:58, Kay Schenk wrote:
> >>>>
> >>>>> In my search to find out more about resource files (.src), I came
> >>>>> across
> >>>>> the old Tools information on the web server, and specifically the
> >>>
> >>> project
> >>>>>
> >>>>> dependency chart:
> >>>>>
> >>>>> http://www.openoffice.org/**tools/project_dependencies.png<
> >>>
> >>> http://www.openoffice.org/tools/project_dependencies.png>
> >>>>>
> >>>>> Is this still valid?
> >>>>>
> >>>>>
> >>>> I do not think that it is still 100% valid.
> >>>> It contains modules neon and berkeleydb which had been removed during
> >>>> our
> >>>> IP clearance work.
> >>>>
> >>>> But for a broader view about the module dependencies it can be used.
> >>>> Such a dependency graph can only be a snapshot on a certain revision
> or
> >>>> release.
> >>>>
> >>>> A dependency graph could be build using the information in the files
> >>>> <module>/prj/build.lst. The first text line contains the modules on
> >>>> which
> >>>> <module> depends on. The build process uses this information to figure
> >>>
> >>> out
> >>>>
> >>>> which module needs to build first. But be aware, there might be
> missing
> >>>
> >>> the
> >>>>
> >>>> one or the other dependency, because it is not needed for the build
> >>>
> >>> process.
> >>>>
> >>>> Deeper investigation/evaluation of the makefiles would also reveal
> >>>> dependency information.
> >>>> But there are also dependencies which are not express in the makefiles
> >>>> or
> >>>> the <build.lst> files. For example, certain modules depend on
> >>>> default_images - it contains icons and images for the UI -, but this
> >>>> dependency is not explicitly mentioned.
> >>>>
> >>> I can only agree with the statement that some dependencies is missing.
> >>> During the changed of localize.pl to genLang, I have seen quite a
> number
> >>> of
> >>> strange things (and written it on my list).
> >>>
> >>> When I get some air, I will start the build project by updating the
> >>> dependency chart...we need that to see if we can modularize parts of
> >>> main.
> >>>
> >>> rgds
> >>> Jan I.
> >>>
> >> Thanks to all for the feedback. I do think a current layout would be
> MOST
> >> helpful to developers, and for our makefile retooling.
> >
> >
> > I wrote a script [1] to extract module dependencies from the build.lst
> > files.
> > First I converted them into a GEXF file [2] for visualization with gephi.
> > That did not produce an output I was happy with. Maybe somebody else has
> > more luck.
>
>
> The GEXF file didn't work for me either. But I did extract the
> dependencies from the DOT file and ran that through Gephi to get this:
>
> http://www.robweir.com/aoo/aoo-modules.svg
>
> The size of each node is proportionate to the "in-degree", i.e., the
> number of incoming dependencies. The colors group sets of modules
> that are highly interconnected.
>
> -Rob
>
>
> > Then I tried the DOT file format [3] for visualization with dot of the
> > graphviz package. The look of the SVG output [4] is similar to the old
> > dependency overview. I color coded some modules for your convenience
> [5]:
> > application modules are blue, build related modules green, test modules
> are
> > a darker green and external libraries are orange. Any ideas for
> improvement
> > are welcome.
> >
> > I also started to analyze the file dependencies and checked for missing
> > module dependencies (if a file from sw has an include of the form
> > .../inc/svx/... then I assumed a dependency of sw on svx). Luckily I
> found
> > no missing dependencies.
> > Some statistics:
> > gbuild modules: 1763354 dependencies in 3510 .d files.
> > dmake modules: 1273271 dependencies in 5700 .dpcc files
> >
> > The numbers are a bit surprising, given that there are only a handful of
> > gbuild modules, while the large majority is still based on dmake. So I
> am
> > not entirely sure if the numbers are correct.
> >
> > -Andre
> >
> > [1] http://people.apache.org/~af/dependencies/AnalyzeDependencies.pl
> > [2]
> http://people.apache.org/~af/dependencies/aoo-module-dependencies.gexf
> > [3]
> http://people.apache.org/~af/dependencies/aoo-module-dependencies.dot
> > [4]
> http://people.apache.org/~af/dependencies/aoo-module-dependencies.svg
> > [5]
> http://tvtropes.org/pmwiki/pmwiki.php/Main/ColourCodedForYourConvenience
> >
>
WOW! I am impressed! Thank you Andre and Rob for working on this area! I
will definitely take a look later today and see if I can also follow your
reasoning. Really, this kind of analysis is crucial to any build
restructuring of course.
The charts are awesome to say the least!
> >
> >>
> >>
> >>
> >>>>
> >>>> Best regards, Oliver.
> >>>>
> >>>>
> >>>>
> >>>>
> ------------------------------**------------------------------**---------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org<
> >>>
> >>> dev-unsubscribe@openoffice.apache.org>
> >>>>
> >>>> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>>>
> >>>>
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >
> > For additional commands, e-mail: dev-help@openoffice.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
----------------------------------------------------------------------------------------
MzK
"There's no upside in screwing with things you can't explain."
-- Captain Roy Montgomery, "Castle"
Re: Is the project dependency chart still valid?
Posted by Rob Weir <ro...@apache.org>.
On Mon, Apr 29, 2013 at 3:36 AM, Andre Fischer <aw...@gmail.com> wrote:
> On 24.04.2013 18:41, Kay Schenk wrote:
>>
>> On Wed, Apr 24, 2013 at 1:36 AM, janI <ja...@apache.org> wrote:
>>
>>> On 24 April 2013 09:45, Oliver-Rainer Wittmann <orwittmann@googlemail.com
>>>>
>>>> wrote:
>>>> Hi,
>>>>
>>>>
>>>> On 23.04.2013 22:58, Kay Schenk wrote:
>>>>
>>>>> In my search to find out more about resource files (.src), I came
>>>>> across
>>>>> the old Tools information on the web server, and specifically the
>>>
>>> project
>>>>>
>>>>> dependency chart:
>>>>>
>>>>> http://www.openoffice.org/**tools/project_dependencies.png<
>>>
>>> http://www.openoffice.org/tools/project_dependencies.png>
>>>>>
>>>>> Is this still valid?
>>>>>
>>>>>
>>>> I do not think that it is still 100% valid.
>>>> It contains modules neon and berkeleydb which had been removed during
>>>> our
>>>> IP clearance work.
>>>>
>>>> But for a broader view about the module dependencies it can be used.
>>>> Such a dependency graph can only be a snapshot on a certain revision or
>>>> release.
>>>>
>>>> A dependency graph could be build using the information in the files
>>>> <module>/prj/build.lst. The first text line contains the modules on
>>>> which
>>>> <module> depends on. The build process uses this information to figure
>>>
>>> out
>>>>
>>>> which module needs to build first. But be aware, there might be missing
>>>
>>> the
>>>>
>>>> one or the other dependency, because it is not needed for the build
>>>
>>> process.
>>>>
>>>> Deeper investigation/evaluation of the makefiles would also reveal
>>>> dependency information.
>>>> But there are also dependencies which are not express in the makefiles
>>>> or
>>>> the <build.lst> files. For example, certain modules depend on
>>>> default_images - it contains icons and images for the UI -, but this
>>>> dependency is not explicitly mentioned.
>>>>
>>> I can only agree with the statement that some dependencies is missing.
>>> During the changed of localize.pl to genLang, I have seen quite a number
>>> of
>>> strange things (and written it on my list).
>>>
>>> When I get some air, I will start the build project by updating the
>>> dependency chart...we need that to see if we can modularize parts of
>>> main.
>>>
>>> rgds
>>> Jan I.
>>>
>> Thanks to all for the feedback. I do think a current layout would be MOST
>> helpful to developers, and for our makefile retooling.
>
>
> I wrote a script [1] to extract module dependencies from the build.lst
> files.
> First I converted them into a GEXF file [2] for visualization with gephi.
> That did not produce an output I was happy with. Maybe somebody else has
> more luck.
The GEXF file didn't work for me either. But I did extract the
dependencies from the DOT file and ran that through Gephi to get this:
http://www.robweir.com/aoo/aoo-modules.svg
The size of each node is proportionate to the "in-degree", i.e., the
number of incoming dependencies. The colors group sets of modules
that are highly interconnected.
-Rob
> Then I tried the DOT file format [3] for visualization with dot of the
> graphviz package. The look of the SVG output [4] is similar to the old
> dependency overview. I color coded some modules for your convenience [5]:
> application modules are blue, build related modules green, test modules are
> a darker green and external libraries are orange. Any ideas for improvement
> are welcome.
>
> I also started to analyze the file dependencies and checked for missing
> module dependencies (if a file from sw has an include of the form
> .../inc/svx/... then I assumed a dependency of sw on svx). Luckily I found
> no missing dependencies.
> Some statistics:
> gbuild modules: 1763354 dependencies in 3510 .d files.
> dmake modules: 1273271 dependencies in 5700 .dpcc files
>
> The numbers are a bit surprising, given that there are only a handful of
> gbuild modules, while the large majority is still based on dmake. So I am
> not entirely sure if the numbers are correct.
>
> -Andre
>
> [1] http://people.apache.org/~af/dependencies/AnalyzeDependencies.pl
> [2] http://people.apache.org/~af/dependencies/aoo-module-dependencies.gexf
> [3] http://people.apache.org/~af/dependencies/aoo-module-dependencies.dot
> [4] http://people.apache.org/~af/dependencies/aoo-module-dependencies.svg
> [5] http://tvtropes.org/pmwiki/pmwiki.php/Main/ColourCodedForYourConvenience
>
>
>>
>>
>>
>>>>
>>>> Best regards, Oliver.
>>>>
>>>>
>>>>
>>>> ------------------------------**------------------------------**---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org<
>>>
>>> dev-unsubscribe@openoffice.apache.org>
>>>>
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>
>>>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Is the project dependency chart still valid?
Posted by Andre Fischer <aw...@gmail.com>.
On 24.04.2013 18:41, Kay Schenk wrote:
> On Wed, Apr 24, 2013 at 1:36 AM, janI <ja...@apache.org> wrote:
>
>> On 24 April 2013 09:45, Oliver-Rainer Wittmann <orwittmann@googlemail.com
>>> wrote:
>>> Hi,
>>>
>>>
>>> On 23.04.2013 22:58, Kay Schenk wrote:
>>>
>>>> In my search to find out more about resource files (.src), I came across
>>>> the old Tools information on the web server, and specifically the
>> project
>>>> dependency chart:
>>>>
>>>> http://www.openoffice.org/**tools/project_dependencies.png<
>> http://www.openoffice.org/tools/project_dependencies.png>
>>>> Is this still valid?
>>>>
>>>>
>>> I do not think that it is still 100% valid.
>>> It contains modules neon and berkeleydb which had been removed during our
>>> IP clearance work.
>>>
>>> But for a broader view about the module dependencies it can be used.
>>> Such a dependency graph can only be a snapshot on a certain revision or
>>> release.
>>>
>>> A dependency graph could be build using the information in the files
>>> <module>/prj/build.lst. The first text line contains the modules on which
>>> <module> depends on. The build process uses this information to figure
>> out
>>> which module needs to build first. But be aware, there might be missing
>> the
>>> one or the other dependency, because it is not needed for the build
>> process.
>>> Deeper investigation/evaluation of the makefiles would also reveal
>>> dependency information.
>>> But there are also dependencies which are not express in the makefiles or
>>> the <build.lst> files. For example, certain modules depend on
>>> default_images - it contains icons and images for the UI -, but this
>>> dependency is not explicitly mentioned.
>>>
>> I can only agree with the statement that some dependencies is missing.
>> During the changed of localize.pl to genLang, I have seen quite a number
>> of
>> strange things (and written it on my list).
>>
>> When I get some air, I will start the build project by updating the
>> dependency chart...we need that to see if we can modularize parts of main.
>>
>> rgds
>> Jan I.
>>
> Thanks to all for the feedback. I do think a current layout would be MOST
> helpful to developers, and for our makefile retooling.
I wrote a script [1] to extract module dependencies from the build.lst
files.
First I converted them into a GEXF file [2] for visualization with
gephi. That did not produce an output I was happy with. Maybe
somebody else has more luck.
Then I tried the DOT file format [3] for visualization with dot of the
graphviz package. The look of the SVG output [4] is similar to the old
dependency overview. I color coded some modules for your convenience
[5]: application modules are blue, build related modules green, test
modules are a darker green and external libraries are orange. Any ideas
for improvement are welcome.
I also started to analyze the file dependencies and checked for missing
module dependencies (if a file from sw has an include of the form
.../inc/svx/... then I assumed a dependency of sw on svx). Luckily I
found no missing dependencies.
Some statistics:
gbuild modules: 1763354 dependencies in 3510 .d files.
dmake modules: 1273271 dependencies in 5700 .dpcc files
The numbers are a bit surprising, given that there are only a handful of
gbuild modules, while the large majority is still based on dmake. So I
am not entirely sure if the numbers are correct.
-Andre
[1] http://people.apache.org/~af/dependencies/AnalyzeDependencies.pl
[2] http://people.apache.org/~af/dependencies/aoo-module-dependencies.gexf
[3] http://people.apache.org/~af/dependencies/aoo-module-dependencies.dot
[4] http://people.apache.org/~af/dependencies/aoo-module-dependencies.svg
[5] http://tvtropes.org/pmwiki/pmwiki.php/Main/ColourCodedForYourConvenience
>
>
>
>>>
>>> Best regards, Oliver.
>>>
>>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org<
>> dev-unsubscribe@openoffice.apache.org>
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Is the project dependency chart still valid?
Posted by Kay Schenk <ka...@gmail.com>.
On Wed, Apr 24, 2013 at 1:36 AM, janI <ja...@apache.org> wrote:
> On 24 April 2013 09:45, Oliver-Rainer Wittmann <orwittmann@googlemail.com
> >wrote:
>
> > Hi,
> >
> >
> > On 23.04.2013 22:58, Kay Schenk wrote:
> >
> >> In my search to find out more about resource files (.src), I came across
> >> the old Tools information on the web server, and specifically the
> project
> >> dependency chart:
> >>
> >> http://www.openoffice.org/**tools/project_dependencies.png<
> http://www.openoffice.org/tools/project_dependencies.png>
> >>
> >> Is this still valid?
> >>
> >>
> > I do not think that it is still 100% valid.
> > It contains modules neon and berkeleydb which had been removed during our
> > IP clearance work.
> >
> > But for a broader view about the module dependencies it can be used.
> > Such a dependency graph can only be a snapshot on a certain revision or
> > release.
> >
> > A dependency graph could be build using the information in the files
> > <module>/prj/build.lst. The first text line contains the modules on which
> > <module> depends on. The build process uses this information to figure
> out
> > which module needs to build first. But be aware, there might be missing
> the
> > one or the other dependency, because it is not needed for the build
> process.
> > Deeper investigation/evaluation of the makefiles would also reveal
> > dependency information.
> > But there are also dependencies which are not express in the makefiles or
> > the <build.lst> files. For example, certain modules depend on
> > default_images - it contains icons and images for the UI -, but this
> > dependency is not explicitly mentioned.
> >
> I can only agree with the statement that some dependencies is missing.
> During the changed of localize.pl to genLang, I have seen quite a number
> of
> strange things (and written it on my list).
>
> When I get some air, I will start the build project by updating the
> dependency chart...we need that to see if we can modularize parts of main.
>
> rgds
> Jan I.
>
Thanks to all for the feedback. I do think a current layout would be MOST
helpful to developers, and for our makefile retooling.
>
> >
> >
> > Best regards, Oliver.
> >
> >
> > ------------------------------**------------------------------**---------
> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org<
> dev-unsubscribe@openoffice.apache.org>
> > For additional commands, e-mail: dev-help@openoffice.apache.org
> >
> >
>
--
----------------------------------------------------------------------------------------
MzK
"There's no upside in screwing with things you can't explain."
-- Captain Roy Montgomery, "Castle"
Re: Is the project dependency chart still valid?
Posted by janI <ja...@apache.org>.
On 24 April 2013 09:45, Oliver-Rainer Wittmann <or...@googlemail.com>wrote:
> Hi,
>
>
> On 23.04.2013 22:58, Kay Schenk wrote:
>
>> In my search to find out more about resource files (.src), I came across
>> the old Tools information on the web server, and specifically the project
>> dependency chart:
>>
>> http://www.openoffice.org/**tools/project_dependencies.png<http://www.openoffice.org/tools/project_dependencies.png>
>>
>> Is this still valid?
>>
>>
> I do not think that it is still 100% valid.
> It contains modules neon and berkeleydb which had been removed during our
> IP clearance work.
>
> But for a broader view about the module dependencies it can be used.
> Such a dependency graph can only be a snapshot on a certain revision or
> release.
>
> A dependency graph could be build using the information in the files
> <module>/prj/build.lst. The first text line contains the modules on which
> <module> depends on. The build process uses this information to figure out
> which module needs to build first. But be aware, there might be missing the
> one or the other dependency, because it is not needed for the build process.
> Deeper investigation/evaluation of the makefiles would also reveal
> dependency information.
> But there are also dependencies which are not express in the makefiles or
> the <build.lst> files. For example, certain modules depend on
> default_images - it contains icons and images for the UI -, but this
> dependency is not explicitly mentioned.
>
I can only agree with the statement that some dependencies is missing.
During the changed of localize.pl to genLang, I have seen quite a number of
strange things (and written it on my list).
When I get some air, I will start the build project by updating the
dependency chart...we need that to see if we can modularize parts of main.
rgds
Jan I.
>
>
> Best regards, Oliver.
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org<de...@openoffice.apache.org>
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
Re: Is the project dependency chart still valid?
Posted by Oliver-Rainer Wittmann <or...@googlemail.com>.
Hi,
On 23.04.2013 22:58, Kay Schenk wrote:
> In my search to find out more about resource files (.src), I came across
> the old Tools information on the web server, and specifically the project
> dependency chart:
>
> http://www.openoffice.org/tools/project_dependencies.png
>
> Is this still valid?
>
I do not think that it is still 100% valid.
It contains modules neon and berkeleydb which had been removed during
our IP clearance work.
But for a broader view about the module dependencies it can be used.
Such a dependency graph can only be a snapshot on a certain revision or
release.
A dependency graph could be build using the information in the files
<module>/prj/build.lst. The first text line contains the modules on
which <module> depends on. The build process uses this information to
figure out which module needs to build first. But be aware, there might
be missing the one or the other dependency, because it is not needed for
the build process.
Deeper investigation/evaluation of the makefiles would also reveal
dependency information.
But there are also dependencies which are not express in the makefiles
or the <build.lst> files. For example, certain modules depend on
default_images - it contains icons and images for the UI -, but this
dependency is not explicitly mentioned.
Best regards, Oliver.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org