No, because my pools were not there and my tests were failing. But no matters, it works now :)
> On 31 Jan 2014, at 17:45, Johan Fabry <[email protected]> wrote: > > > What probably happened is that Monticello loading with pooldictionaries was > still working, but Nautilus was not showing them. This is the only thing that > changed, and the fix addresses the showing part. So you should not worry. > >> On Jan 31, 2014, at 1:26 PM, Esteban Lorenzano <[email protected]> wrote: >> >> I don’t know what happened. All that I know is that it was not working and >> now with the last fix it is, so I’m happy for now. >> worried? yes. But not too much :) >> >>> On 31 Jan 2014, at 14:59, Henrik Johansen <[email protected]> >>> wrote: >>> >>> >>>> On 30 Jan 2014, at 6:14 , Esteban Lorenzano <[email protected]> wrote: >>>> >>>> So… that. >>>> >>>> Is super cool to remove poolDictionaries from the default class template. >>>> What is not cool *at all* is the fact that now my low level projects, who >>>> uses them intensively, does not work anymore. >>>> The reason? the classes are created without poolDictionaries. >>>> >>>> So, please… whoever pushed this change. Please fix it. >>>> >>>> thanks, >>>> Esteban >>> >>> Sooo, since I’m curios, anyone care to explain how a change intended to >>> affect whether Nautilus displays pool Dicts end up breaking how they’re >>> loaded from Monticello? >>> >>> Did Nautilus pick up on the class load announcement from RPackage and end >>> up recompiling the class with it’s own (lacking) default definition or >>> something similarly crazy? >>> >>> Cheers, >>> Henry > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > >
