Issue 3490 in pharo: ConfigurationOfPharo still uses Preferences

Status: Accepted
Owner: [hidden email]

New issue 3490 by [hidden email]: ConfigurationOfPharo still uses  
Preferences
http://code.google.com/p/pharo/issues/detail?id=3490

- see #preloadForPharo and #postloadForPhaor
- same in ConfigurationOfNonPharo

Updates:
        Labels: Milestone-1.2

Comment #1 on issue 3490 by [hidden email]: ConfigurationOfPharo  
still uses Preferences
http://code.google.com/p/pharo/issues/detail?id=3490

(No comment was entered for this change.)

Updates:
        Status: Invalid

Comment #2 on issue 3490 by marianopeck: ConfigurationOfPharo still uses  
Preferences
http://code.google.com/p/pharo/issues/detail?id=3490

Yes, because of history. It is used by versions and baselines of pharo 1.0  
and 1.1.
But, as you can see, none  of the version/baselines 1.2 use it. So, it is  
ok.

Comment #3 on issue 3490 by [hidden email]: ConfigurationOfPharo  
still uses Preferences
http://code.google.com/p/pharo/issues/detail?id=3490

Maybe one should rename #preloadForPharo to preloadForPharoBelow12 or  
something ;)

Comment #4 on issue 3490 by marianopeck: ConfigurationOfPharo still uses  
Preferences
http://code.google.com/p/pharo/issues/detail?id=3490

rename not, beacause we don't want to touch all the already released  
versions/baselines. Maybe we didn't choose the best name and we should have  
called it preloadPharo10 or something like that. But we were learning.

Anyway, what both mehtods used to do, I think have not sense any more in  
1.2. If this is not the case, then we should create as you say  
preloadForPharo12  and do that without using Preferences.