October 2008 - Pharo-dev - lists.pharo.org

[Pharo-project] History and SUnit
by Alexandre Bergel Oct. 13, 2008

Oct. 13, 2008

Dear list, In PharoInbox Gwenael and I put an extension of SUnit that records results when running a set of test. Feel free to suggest improvement.... Open a TestRunner to enjoy its 'History' button. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

8 23

[Pharo-project] [MC] Adding a constraint when declaring a required package
by Alexandre Bergel Oct. 13, 2008

Oct. 13, 2008

Maybe we should forbid a package XXX-YYY to be required for a package named XXX What do you think? A simple check will do it... Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

5 17

[Pharo-project] faster snapshotting
by StÃ©phane Ducasse Oct. 13, 2008

Oct. 13, 2008

Hi matthew I'm checking your http://code.google.com/p/pharo/issues/detail?id=235&colspec=ID%20Type%20Sta… "Adding the ivar 'category' to methodReference allows a 25% speedup in Monticello snapshotting, after source caching. This capability is exploited as of PackageInfo-Base-mtf.56" for 10092 now. http://code.google.com/p/pharo/issues/detail?id=235&colspec=ID%20Type%20Sta… Several questions - I do not know what you mean by PackageInfo-Base-mtf.56? Where is it? Is this package uses your setter method category:? - why the category and category: methods are not in the *monticello extension? (There were in *monticello in 10091) - When I categorized them in *monticello I got problems or my network is really gettiong slow. Stef

2 3

[Pharo-project] about classVar
by StÃ©phane Ducasse Oct. 13, 2008

Oct. 13, 2008

Hi to my stupefaction I discovered that the classVariables of a class are not the same as the ones of its metaclass. TheRoot classVarNames ~= TheRoot class classVarNames Does any body have some ideas why this is like that? For me this is a conceptual bug. Stef

2 2

[Pharo-project] [ANN] 10092
by StÃ©phane Ducasse Oct. 13, 2008

Oct. 13, 2008

> - FullScreen refactoring by mike Roberts > - fixed a bug in PluggableListMorph>>basicKeyPress introduced in > 10087 by Matthew Fulmer > - improve SUnit history (removed PopUpMenu) > - Issue 235: 0007205: Monticello Snapshot Speedup via new > MethodReference ivar (http://bugs.squeak.org/view.php?id=7205) by > Matthew Fulmer > > > Stef Matthew could you sign the agreement? Stef

2 2

[Pharo-project] Fwd: food for thoughts :)
by StÃ©phane Ducasse Oct. 12, 2008

Oct. 12, 2008

Begin forwarded message: > From: pharo-project-owner(a)lists.gforge.inria.fr > Date: October 12, 2008 9:29:18 PM CEDT > To: stephane.ducasse(a)free.fr > Subject: food for thoughts :) > > You are not allowed to post to this mailing list, and your message has > been automatically rejected. If you think that your messages are > being rejected in error, contact the mailing list owner at > pharo-project-owner(a)lists.gforge.inria.fr. > > > From: stephane ducasse <stephane.ducasse(a)free.fr> > Date: October 12, 2008 9:29:16 PM CEDT > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> > Subject: food for thoughts :) > > > http://producingoss.com/ > > p 129 > > At the Apache Software foundation we discourage the use of author > tags in source > code. There are various reasons for this, apart from the legal > ramifications. Collabor- > ative development is about working on projects as a group and caring > for the project > as a group. Giving credit is good, and should be done, but in a way > that does not al- > low for false attribution, even by implication. There is no clear > line for when to add or > remove an author tag. Do you add your name when you change a > comment? When > you put in a one-line fix? Do you remove other author tags when you > refactor the code > and it looks 95% different? What do you do about people who go about > touching every > file, changing just enough to make the virtual author tag quota, so > that their name will > be everywhere? > > There are better ways to give credit, and our preference is to use > those. From a tech- > nical standpoint author tags are unnecessary; if you wish to find > out who wrote a par- > ticular piece of code, the version control system can be consulted > to figure that out. > Author tags also tend to get out of date. Do you really wish to be > contacted in private > about a piece of code you wrote five years ago and were glad to have > forgotten? > > > >

1 0

[Pharo-project] [ANN] 10093
by StÃ©phane Ducasse Oct. 12, 2008

Oct. 12, 2008

- Network fix by Yann Monclair Modified the deprecation comment on Url>>#toText. It was recommending using Url>>#asText instead, but that would mean the method would return a Text instead of a String as it currently does. I replaced the deprecation comment to recommend replacing #toText with #asString. All NetworkTests run green - Fix by A. Bergel. The method PasteUpMorph>>findAPreferencesPanel: is now an extension of MorphicExtras. Before it was part of Mophic- Worlds. The reason to move findAPreferencesPanel: to MorphicExtras is the method references PreferencesPanel, which is defined in MorphicExtras. PasteUpMorph calls findAPreferencesPanel: within PasteUpMorph>>defaultDesktopCommandKeyTriplets. The cycle is therefore not completely removed. However, defaultDesktopCommandKeyTriplets should be turned into a registration mechanism to completely remove the cycle. - allUnSentMessages -> allUnsentMessages, removeAllUnSentMessages -> removeAllUnsentMessages, allUnSentMessagesIn: -> allUnsentMessagesIn: Stopping for this evening :) Stef

1 0

Oct. 12, 2008

but UIManager Tx

1 0

[Pharo-project] Pharo Harvesting Infrastructure
by Matthew Fulmer Oct. 12, 2008

Oct. 12, 2008

Hi. I found a bug in Pharo, and I started wondering how to determine where it came from. I checked a few methods in the debugger to see if they had recently been modified, but that was no help. I checked the change sorter to see if it had any idea what had been recently installed, but it was choked by Monticello updates. Then I opened a new Pharo Image in order to try each update one by one (whatever Monticello you guys use to load your changes is *really* slow. I gotta fix you guys up with MC1.6). But before I did that, I noticed on the right of the screen is something that looks like a change log. And at the bottom, it said: (full list of changes: print "ScriptLoader new logContents") So I tried it in my 10091 image, and sure enough, it printed up a changelog. So I went to see what this mysterious class ScriptLoader is. I found a whole lot of methods. Some looked auto-generated. Some seemed to be convenience methods for loading MC packages from Pharo and PharoInbox. It looks kind of like Installer, which I am more familiar with. I'm rather curious now about how you manage Pharo. I took a look at http://code.google.com/p/pharo/wiki/HowToContribute and wondered what happens after that. I now imagine it involves ScriptBuilder building the update, and then something uploading it. What is the mechanism? How is Pharo tested? is it regularly tested by someone using TestRunner, or something fancier? What are all the auto-generated methods in ScriptLoader for? How do you typically trace a bug from image to problem package to update to issue? I'm interested because keith and I are building a build server that is able to build images, build packages, load packages, run tests, build VM's and such, all automated and with an easy interface. So far, we have the easy interface (Installer), but are still working on making it do more. So I'm interested in learning how it works here, so that we can at least end up with something as good as this -- Matthew Fulmer -- http://mtfulmer.wordpress.com/

3 6

Oct. 12, 2008

1 0