Hi,

Ok, I understand that part, but my question was: what code relationships does the analyzer take into account?

Cheers,
Doru��

On Thu, Sep 10, 2015 at 9:43 AM, Christophe Demarey <Christophe.Demarey@inria.fr> wrote:
The data comes from the dependency analyzer analysis (re-compute each time to avoid wrong information) + the information given in Manifests : manuallyResolvedDependencies (potential dependencies needing a human decision) and ignoredDependencies.

Le 9 sept. 2015 �� 23:32, Tudor Girba a ��crit :

Hi,

Very interesting.

Could you detail which information you use for building the edges?

Cheers,
Doru



On Wed, Sep 9, 2015 at 11:33 AM, Christophe Demarey <Christophe.Demarey@inria.fr> wrote:
Hi,

We now have a best overview of bootstrap dependencies.
With Max, we reused Dijkstra algo in Moose to help finding dependencies leading to Morphic and co.
It is now possible to have a visualization that is usable (there is also a button to open it in the report): ��https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTML_Report/bootstrap-dependency-report-graph.html

Next steps are to cut dependencies in red in the report table.

Christophe.

ps: by the way the dependency analyzer (with fixes asked) will be introduced soon in the image.

<Capture d�����cran 2015-09-09 �� 11.33.02.png>

Le 4 sept. 2015 �� 15:13, Christophe Demarey a ��crit :

Hi,

I created a job to automatically generate a report of the Pharo image dependencies as well as current bootstrap dependencies.
You can find them here:
There are a lot (too many) dependencies but you can focus on some of them with the search field.
Dependencies inside orange boxes are dependencies that are there but that we ignore (for example, an example method adds an extra-dependency). It should be fixed later but is not a problem for now. Ignored dependencies are declared in the package manifest in #ignoredDependencies.
Dependencies inside red boxes are dependencies we want to remove for the bootstrap. For now, they are listed in the bootstrap dependency report.

People that are willing to help to have a more modular Pharo could first take a look at the bootstrap dependency report and check dependencies that we should cut.
Once we know, we can open issues on fogbugz in the 'bootstrap category' and update manifests accordingly.
To investigate more deeply dependencies, you can use the DependencyAnalyzer (in the Pharo Catalog) to actually check dependencies (inheritance, reference, extension, traits, message send).

Regards,
Christophe.




--

"Every thing has its own flow"




--
www.tudorgirba.com

"Every thing has its own flow"