Two quick questions this morning : 1) If I am using a package from squeaksource.com and this package only works with Squeak now (methods have been removed from Pharo, methods only exists in Squeak, different behavior in Pharos vs Squeak, whatever the reason), what is the preferred way of committing a works-in-Pharo version to SqueakSource ? I wouldn't want the same problem happening to Squeakers, i.e. someone loads this package in Squeak and discover that the new version only works in Pharo now! Perhaps the answer is "Pharo needs its own SqueakSource repository" but in the meantime, what should I do and how? 2) Is there a preferred way of adding settings/preferences to the Pharo environment, if so can someone redirect me to the proper documentation/link on how-to-do-it ? I'm a bit confused as to what I'd have to use since there seems to be some old (?!?!) Preferences stuff still present in Pharo. In my case, I'd like to be able to specify my own parseableSourceCodeTemplate instead of the default one. ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)