March 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] Auto-rename image and changes file after updating
by HernÃ¡n Morales Durand March 25, 2010

March 25, 2010

Hi, I've noticed every time I update a Pharo image I should rename manually the image and changes file names to match the new updated version number. I.e.: If you have PharoCore-1.1-11291-UNSTABLE.changes PharoCore-1.1-11291-UNSTABLE.image then update to #11295 and save and quit, you should modify the file names manually to PharoCore-1.1-11295-UNSTABLE.changes PharoCore-1.1-11295-UNSTABLE.image The attached files does the following: -After a Pharo software update, evaluate the FileOutNewNamesAfterUpdate.st script -Quit the image -For Win users: Run the batch updateFileNames.bat to rename the image and changes files to the latest version. (this is not the same as Save as...) Feel free to modify and use it as you want :) Cheers, HernÃ¡n

3 4

[Pharo-project] SystemSetting fixes + Preferences references removal
by Alain Plantec March 25, 2010

March 25, 2010

Hi all, In the InBox: SLICE-SystSettings * range setting: bad widget height in the SettingBrowser * improve TimeProfiler (MorphTreeMorph example) * remove resurrected Preferences references Cheers Alain

2 1

[Pharo-project] Update cache?
by HernÃ¡n Morales Durand March 25, 2010

March 25, 2010

Hi all Updating a Pharo image to the latest version doesn't use the downloaded update files as a cache for future updates. Is this done on purpose? Cheers, HernÃ¡n

2 1

[Pharo-project] funny behavior with MC
by StÃ©phane Ducasse March 25, 2010

March 25, 2010

this is strange before lunch I could select Polymorph-Widgets and merge at will and now I cannot anymore because I got a message could not find versions for example 107 Now this is really strange because this is the first version that was merged so normally it should be found. It is either in the UIEnhancements repository or the one of pharo. Does anybody encountered this behavior? Right now I'm blocked. MC looks so mysterious we will have to fix it in the future. Stef

3 12

[Pharo-project] Searching for references
by Mariano Martinez Peck March 25, 2010

March 25, 2010

Hi folks. Today I were talking with Noury and from our point of view, there is a bug in the Class references. Forget about refactoring browser. Right now, if you look for the references of a class, it ONLY searches literal matches in the source code of methods. It doesn't take into account for example if you have subclasses. In the abstract speaking, if there are subclasses, isn't that considered a reference ? Even more, the tool would be much more useful if it can find such information. Several times, I look for references of a class I don't know and that I think it can be removed. I look references, zero. Excellent, I can removed. But then....I realized it has a subclass and that class is referenced in 200000 places...fresh example: DummySuperclassOfColorPickerMorph. In summary, it would be great if subclasses can be tacking into account also. Or at least I don't know, create another menu entry for that... I am the only one who think that ? what is your opinion ? Cheers Mariano

3 2

Re: [Pharo-project] cannot update metacello in rc3
by Dale Henrichs March 24, 2010

March 24, 2010

Doru, I was just a little bit worried when RC3 was shipped with a #development blessing for 1.0-beta.25, now I have a concrete reason to be worried. Since 1.0-beta.25 is in #development, the latestVersion of Metacello is 1.0-beta.24.1 and thats the version that gets loaded by #loadLatestVersion... With that said you _have_ exposed a bug in the #loadLatestVersion method: | project | project := self project. project updateProject. project latestversion load When self project is evaluated the latestVersion is 1.0-beta.24.1. After #updateProject is performed, the latestVersion in ConfigurationOfMetacello is 1.0-beta.25.1, but since we don't refresh the project, we load 1.0-beta.24.1. If you do "ConfigurationOfMetacello loadLatestVersion", close the walkback(s) and try "ConfigurationOfMetacello loadLatestVersion" again, you'll be updated correctly. I've checked in a fix for #loadLatestVersion, so if you update the configuration first, then do #loadLatestVersion ... that will work also. Nice catch and I hope that you get better, Dale ----- "Tudor Girba" <tudor.girba(a)gmail.com> wrote: | Hi, | | I took the RC3 dev image and I tried "ConfigurationOfMetacello | loadLatestVersion", but it fails. | | I did not have time to look into this, but this is problematic :). | | Cheers, | Doru | | | -- | www.tudorgirba.com | | "It's not how it is, it is how we see it." | | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] cannot update metacello in rc3
by Tudor Girba March 24, 2010

March 24, 2010

Hi, I took the RC3 dev image and I tried "ConfigurationOfMetacello loadLatestVersion", but it fails. I did not have time to look into this, but this is problematic :). Cheers, Doru -- www.tudorgirba.com "It's not how it is, it is how we see it."

2 3

[Pharo-project] Issue 2205
by laurent laffont March 24, 2010

March 24, 2010

http://code.google.com/p/pharo/issues/detail?id=2205 In PharoInbox: Morphic-LaurentLaffont.558 As all SimpleHierarchicalListMorph & PluggableTreeMorph users put autoDeselect to false (or bug if not), it's now the default. Laurent Laffont

1 0

[Pharo-project] JPEGReadWriter and JPEGReadWriter2
by Mariano Martinez Peck March 24, 2010

March 24, 2010

I read class comments and seem to be different, but I don't like the name at all. We should rename (or remove?) JPEGReadWriter2 to something better. we should merge them ? I have no idea...I just send a warning to you. Cheers Mariano

2 2

[Pharo-project] Montacello configuration writing
by Hilaire Fernandes March 24, 2010

March 24, 2010

Learning Montacello configuration. Instead of writing a package dependency as spec package: 'CoolToolSet--Core' with: [spec requires: 'CoolBrowser ALL'] Can't we write more clearly as; spec package: 'CoolToolSet--Core' requires: 'CoolBrowser ALL' I find the first one far too cryptic. Hilaire

2 1