You mean and import it into pharo. Yes! What is the status of the MooseLoader and friends?
Stef On Sep 5, 2009, at 3:14 AM, Tudor Girba wrote:
Hi Jannik,
FormalContext and TimeWarpingEngine were part of the SCGAlgorithms package in VW. It would be great if someone could take a look at this package :)
Cheers, Doru
On 3 Sep 2009, at 07:52, Laval Jannik wrote:
Hi all,
After a check, the method MooseEntity>>uniqueNameMatchesExpression is not loaded in the standard MooseLoader>>load.
But, in Hismo there are some methods which use FormalContext or TimeWarpingEngine. I have found 4 methods:
- HismoAbstractHistory>>allEarliestEvolutionOfPropertyNamed:
HismoAbstractHistory
timeWarpingSimilarityAsComparedWith:relatedToVersionProperty:
- HismoClassHistoryGroup>>historiesThatChangedLOCTogether
- HismoHistoryGroup>>coChangeConceptsUsing:
Is there another package to load to fix this? Or are these methods deprecated ?
Thank you
Jannik
On 2 sept. 09, at 17:53, Laval Jannik wrote:
Hi all,
I found some methods which use CFBlockOperator or other unknown classes
The list is:
- MooseEntity>>uniqueNameMatchesExpression with no sender which
use CFBlockOperator
- HismoClassHistoryGroup>>historiesThatChangedLOCTogether with no
sender which use FormalContext
- HismoHistoryGroup>>coChangeConceptsUsing: with no sender which
use FormalContext.
I think there are other concerned methods. I have create the issue 140.
Is it possible to remove these methods ?
Jannik Laval PhD Student - Rmod Team - INRIA Certified Project Management Associate (IPMA) http://www.jannik-laval.eu http://rmod.lille.inria.fr
Jannik Laval PhD Student - Rmod Team - INRIA Certified Project Management Associate (IPMA) http://www.jannik-laval.eu http://rmod.lille.inria.fr
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev