18 Feb
2011
18 Feb
'11
3:40 p.m.
In fact it was the tests from System announcement that were unregistering
the package organizer from the announcer. I fixed all the tests but this
revealed a new error :) I will have to fix it
2011/2/15 Cyrille Delaunay <cy.delaunay(a)gmail.com>
All work well with class refactoring, the problem is
that when opening a
moose image, RPackageOrganizer has not yet registered to system
announcements. This should be done in the initialization of the class
RPackageOrganizer.
If I do myself a 'ConfigurationOfRPackage loadDefault' in a fresh pharo
image, the organizer correctly register to announcements.
Could it be a problem with metacello that does not correctly initialize
classes ?
2011/2/15 Tudor Girba <tudor(a)tudorgirba.com>
Don't forget to write a test :)
Doru
On 15 Feb 2011, at 11:36, Cyrille Delaunay wrote:
--
www.tudorgirba.com
"Every thing has its own flow."
Indeed there is something wrong. I will try to
fix that today
2011/2/15 Tudor Girba <tudor(a)tudorgirba.com>
I did not try recently. But if I remembered correctly, I just performed
a rename
refactoring and then checked the RPackage model.
Cheers,
Doru
On 15 Feb 2011, at 11:14, Cyrille Delaunay wrote:
> Do you still have this problem?
>
> 2011/1/31 Cyrille Delaunay <cy.delaunay(a)gmail.com>
> Thanks, I will look at that
>
> 2011/1/31 Tudor Girba <tudor(a)tudorgirba.com>
>
> Hi Cyrille,
>
> I noticed a case in which the RPackage did not seem to refresh after
performing a class rename refactoring.
>
> I did not have a chance to write a test case for this, but I think it
probably affects the importing as well.
Cheers,
Doru
--
www.tudorgirba.com
"No matter how many recipes we know, we still value a chef."
--
www.tudorgirba.com
"Reasonable is what we are accustomed with."