I am very happy to announce that Andrei solved the long-lasting
Glamour bug that prevented the correct
refresh of browsers with circular dependencies between panes.
This means that from now on, we have significantly more freedom in
creating complex browsers.
For example, in the Meta Browser, if you click on the bottom
visualization, the browser will properly navigate to that entity and
highlight it in the visualization.
"Some battles are better lost than fought."
I would like to clean up some visualization scripts which appear in contextual menus and have been around for some times but, in my opinon, are now quite useless. I wrote them mainly to test different algorithms from graphs as well as mondrian tricks, but the results is not so compelling.
So, does anyone use the following?
If not, I will delete them.
The result of the discussion I just had with Doru.
In the last version of Mondrian.
As usual, if you experience trouble, then let me know.
Alexandre Bergel http://www.bergel.eu
I noticed a recent commit in Arki-Reporter. It would be nice to get
your efforts in this repository, but in this case, the commit is wrong:
1. you removed REPConcernSpecification class>>open (is this by any
chance due to the overriding problem?)
2. you removed the error checking of the result computation which can
easily break the whole report
Could you please take a look?
"Yesterday is a fact.
Tomorrow is a possibility.
Today is a challenge."
I changed a bit the model of Arki:
- I introduced Stakeholder as first class
- I introduced a ConcernStatus hierarchy to be able to distinguish
between: success, failure, error and neutral
- With this occasion I also strengthen a tiny bit the error handling
- I removed statusValue
I will probably still change it a bit, but not dramatically. Please
let me know if you have any problems with it.
"Every successful trip needs a suitable vehicle."
I'm looking for a good name which covers both package and namespace concepts. 'ScopingEntity' sounds a bit too verbose.
The reason is that today, we have queries like clientClassesOutOfMyPackage, clientClassesOutOfMyNamespace. There are strong similarities between such queries so that it can actually be written once and reused multiple times. Tomorrow, I want such queries to be defined in a trait and injected in both FamixPackage and FamixNamespace. But, I want a single good name to name both Namespace and Package. Container?
Begin forwarded message:
> (19 August 2010 6:08:23 am) -- BEGIN: ConfigurationOfMoose
> (19 August 2010 6:08:23 am) -- loading
> (19 August 2010 6:11:27 am) -- **Warning/Halt when loading of ConfigurationOfMoose
> ** Warning: This package depends on the following classes:
> You must resolve these dependencies before you will be able to load these definitions:
Fixed: change MOGraphVizLayout superclass to MOLayout following Alex's change