Hi Ben,
Le 9 sept. 2015 à 16:03, Ben Coman a écrit :
> The interactive graph is cool. Some suggestions:
> * Mark nodes of dependencies you want to prune in red.
yes, I will add it ASAP
> * Allow nodes to be pinned
>* http://bl.ocks.org/GerHobbelt/3637711
very good idea.
TBH, I justa
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 :
Le 10 sept. 2015 à 15:31, Tudor Girba a écrit :
> Hi,
>
> Ok, I understand that part, but my question was: what code relationships does
> the analyzer take into account?
Supported dependencies are:
inheritance: you inherit from a class of another package
reference: there is an explicit
On Thu, Sep 10, 2015 at 3:54 PM, Christophe Demarey
wrote:
> Hi Ben,
>
> Le 9 sept. 2015 à 16:03, Ben Coman a écrit :
>
> The interactive graph is cool. Some suggestions:
> * Mark nodes of dependencies you want to prune in red.
>
>
> yes, I will add it ASAP
>
> *
Hi Craig,
Le 9 sept. 2015 à 11:53, Craig Latta a écrit :
>
> Hoi Christophe--
>
>> We now have a best overview of bootstrap dependencies.
>
> That's a pretty grim picture. :) Can you post a movie of you
> picking through that ball of connections? (E.g., with the search feature
> as you
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.dema...@inria.fr> wrote:
> The data comes from the dependency analyzer analysis (re-compute each time
> I updated the graph. There is now:
>
> * dependencies to remove in red
> * if you double-click on a node, you only see links where the node
> is involved.
Very nice!
-C
--
Craig Latta
netjam.org
+31 6 2757 7177 (SMS ok)
+ 1 415 287 3547 (no SMS)
Very cool. A couple of minor improvements:
* The double-clicked "target" node is also hidden, so its label does not show.
* When double-clicking a second node "B", it resets to show all links,
rather than showing only the links for "B". Perhaps reset only when
the "target" node is double-clicked
I updated the graph.
There is now:
dependencies to remove in red
if you double-click on a node, you only see links where the node is involved.
Le 10 sept. 2015 à 13:30, Ben Coman a écrit :
> On Thu, Sep 10, 2015 at 3:54 PM, Christophe Demarey
> wrote:
>> Hi Ben,
>>
Hoi Christophe--
> We now have a best overview of bootstrap dependencies.
That's a pretty grim picture. :) Can you post a movie of you
picking through that ball of connections? (E.g., with the search feature
as you described, or any with any other UI affordance that you have with
this
The interactive graph is cool. Some suggestions:
* Mark nodes of dependencies you want to prune in red.
* Allow nodes to be pinned
* http://bl.ocks.org/GerHobbelt/3637711
*
http://stackoverflow.com/questions/11584757/interactively-fixing-a-node-in-a-directed-force-graph
*
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:
https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTML_Report/dependency-report.html
On Fri, Sep 4, 2015 at 11:18 PM, Christophe Demarey
wrote:
> Hi Ben,
>
> Le 4 sept. 2015 à 17:04, Ben Coman a écrit :
>>
>> I tried the Dependency Analyzer. First a minor point, it wasn't
>> obvious how to invoke it. I expected to see "Dependency Analyzer" in
>> the
On Sat, Sep 5, 2015 at 12:23 AM, Ben Coman wrote:
> In Package Dependencies Analysis, taking for example "(AST-Core -->
> Dependent packages : 15 | Dependencies : 134 (+ 14 extension
> dependencies)"
If I select Announcements-Core, then click to unselect it, I get "MNU
On Fri, Sep 4, 2015 at 9:13 PM, Christophe Demarey
wrote:
> 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:
>
>
btw, I'm not sure how much gloss you'd like to put on the Package
Dependencies Browser, but just some immediate thoughts:
* It feels awkward having the button at the top and the
button at the bottom. It would be nicer if the first was
also at the bottom on the same line (i.e. half the width).
Hi Christophe,
the tool and this depedency report is great.
But how are the dependencies categories "Ignored dependency" , "Dependency
to remove" created,
is this a manual step?
For examlpe, I don't understand why
Graphics-Display Objects
Le 4 sept. 2015 à 18:23, Ben Coman a écrit :
> On Fri, Sep 4, 2015 at 11:18 PM, Christophe Demarey
> wrote:
>> Hi Ben,
>>
>> Le 4 sept. 2015 à 17:04, Ben Coman a écrit :
>>>
>>> I tried the Dependency Analyzer. First a minor point, it wasn't
>>> obvious how to
Hi Nicolai,
Le 4 sept. 2015 à 21:12, Nicolai Hess a écrit :
> Hi Christophe,
>
> the tool
The tool was originally created by Baptiste Quidé and I enhanced it with
message send analysis.
> and this depedency report is great.
Thanks.
> But how are the dependencies categories "Ignored
Le 4/9/15 21:54, Christophe Demarey a écrit :
Are examples the only (or majority) kind of ignoredDependencies ? If
>there is a significant number of other kinds, it might be useful to
>split the examples out
At this time, not a lot.
It is mostly when you know that a code will not be
Hi Ben,
Le 4 sept. 2015 à 17:04, Ben Coman a écrit :
> On Fri, Sep 4, 2015 at 9:13 PM, Christophe Demarey
> wrote:
>> Hi,
>>
>> I created a job to automatically generate a report of the Pharo image
>> dependencies as well as current bootstrap dependencies.
>> You
21 matches
Mail list logo