I had a quick look at it.
In Pharo 1.2, the XML-Parser parkage is clean (i.e.,not dirty). Loading XMLSupport turns
the package dirty. The user is asked whether he is ready to lose his changes. I cannot
determine why the packages turned dirty.
Executing:
Gofer new
squeaksource: 'XMLSupport';
package: 'ConfigurationOfXMLSupport';
load.
(Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault.
in a fresh image raises the popup. Without canceling or accepting, open a Monticello
browser, you will see the package dirty.
Jaaryer, can you have a look at it? There is something weird with the configuration. I
sincerely hope we will have a better tool for managing configuration. I am currently
working on it, but it is still too early for releasing it.
Cheers,
Alexandre
On 5 Jan 2011, at 11:41, Tudor Girba wrote:
Hi,
XMLSupport is present in the latest Pharo 1.2. Loading a new version generates an
exception apparently, so I removed for the moment XMLSupport from the default
ConfigurationOfMoose.
I think we should only load this conditionally. Or do you have another solution?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing should have the right to be different."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel
http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.