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

[Pharo-project] Total image lockup when using middle/right click menu on world
by Simon Kirk Sept. 30, 2008

Sept. 30, 2008

Hi all. Not sure where I should report this. If I use the middle/right (depending on one's preferences) click World menu (the one with Project and Configuration sub-menus down towards the bottom third of the menu), when my mouse goes over the "Configuration" menu section, the entire image freezes irrevocably, at least on OSX (my VM). A few fast-hit alt-. efforts can bring up a debugger on the current process, but it too is frozen. Don't know if this was already something knew about. Sorry for the duplication if so. Cheers, Simon ****************************************************************************************************************************************** This email is from Pinesoft Limited. Its contents are confidential to the intended recipient(s) at the email address(es) to which it has been addressed. It may not be disclosed to or used by anyone other than the addressee(s), nor may it be copied in anyway. If received in error, please contact the sender, then delete it from your system. Although this email and attachments are believed to be free of virus, or any other defect which might affect any computer or IT system into which they are received and opened, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by Pinesoft for any loss or damage arising in any way from receipt or use thereof. ******************************************************************************************************************************************* Pinesoft Limited are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA

3 6

[Pharo-project] [OB] Implementor
by Alexandre Bergel Sept. 30, 2008

Sept. 30, 2008

Hi! Pressing alt-m on a method that is implemented on a class-side prevents from opening a implementor method. I will open an issue. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 3

[Pharo-project] Integrate early and release often and tests was: Installer was: Fwd: [Seaside-dev] preliminary Seaside 2.9 alphauniverse
by Simon Kirk Sept. 29, 2008

Sept. 29, 2008

Hi all. Apropos of the conversation this subject line evolved from, I was thinking about this from Marcus: "Pharo will do it completely differently: release often, integrate as soon as possible, keep the bugtracker down to managable levels and do not be religiously backwards-compatible." This lead me to think various comments recently from Stef (I think - I apologise if I'm miss-paraphrasing, but I can't find the exact messages) about how to tell which tests have failed/passed etc as the versions go by. I submit that in order for early integration and regular release to work, it needs to be an "all tests green or nothing" situation. Of course, it's very difficult to make sure all the tests are passing, but I just ran *all* the tests in the system, and there's only one error and one failure. This is fantastic work! Not only that but the error is down to BookMorph (due for removal iirc?) and a #printString problem with Array, the latter of which *has* to be simple to fix. If this level of passing tests (or even better, all of them; not necessarily possible as various things like EToys are stripped out I imagine) is maintained, there's no need to tell what tests have changed state from version to version; moreover Pharo will be far the better for it, imho. Just my â¬0.02 :) Cheers, Simon ****************************************************************************************************************************************** This email is from Pinesoft Limited. Its contents are confidential to the intended recipient(s) at the email address(es) to which it has been addressed. It may not be disclosed to or used by anyone other than the addressee(s), nor may it be copied in anyway. If received in error, please contact the sender, then delete it from your system. Although this email and attachments are believed to be free of virus, or any other defect which might affect any computer or IT system into which they are received and opened, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by Pinesoft for any loss or damage arising in any way from receipt or use thereof. ******************************************************************************************************************************************* Pinesoft Limited are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA

1 0

[Pharo-project] SqueakMap Packae Loader - nil object
by Dan Corneanu Sept. 29, 2008

Sept. 29, 2008

Hi, there is an exception when trying to open SqueakMap Package Loader in the latest pharo/pharo-dev images with the latests updates. The object instance variable of SMSqueakMap is nil. I'm not sure if I should have put an issue on the tracker or not. Best regards, Dan Corneanu.

3 2

[Pharo-project] How do we manage todos?
by StÃ©phane Ducasse Sept. 29, 2008

Sept. 29, 2008

I would prefer a bugtraker with a tag todo that are not bug fixes. Stef

4 4

Re: [Pharo-project] OB's icon support improved
by Bill Schwab Sept. 29, 2008

Sept. 29, 2008

I apologize for not paying more attention to this thread. Visual feedback in the browser is very much appreciated, and you seem to be doing a very nice job! Had I been paying attention, I'd have said things like the following: (1) Red is probably not the best choice to have lurking on the screen. Maroon/purple/clay rose or just about any "muted" or muddy red IMHO is a much better choice for most things. It might help to add a small amount of blue to the greens too for the same reason. I recommend trying for the psychological benefit with as little eye strain potential as possible. (2) For collections, consider something like a circle drawn a few times from right to left to give an overlapping effect, maybe ... thrown in there if there is room. (3) For exceptions, I like the icon, but two concerns: it might be a little faint/bland; it might work better if its implied movement were upward. Dolphin 5 uses an explosion icon in some situations. That might work well for exceptions and errors. (4) Do we have any color blind people among us? IIRC, something around 12-14% of the population is affected to some degree, so we will encounter it. The test icons will be lost on some of the more extreme red/green sufferers. An alternative would be a boxed check, X or ?. The box (or other border shape) being the suggestion of the test, and the symbol indicating the state. It is fine to add color too, but we should give the red/green crowd a way to see what is going on. Not meaning to jab anyone in the eye, the Installer script is just the kind of thing I'd hope to be able to exchange in situations like this. I do not care so much that it is Installer that we use, but _something_ that can cope with the various publication methods and cope with the details is much needed. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029

4 3

[Pharo-project] About Network-YM.44.mcz
by Yann Monclair Sept. 29, 2008

Sept. 29, 2008

Hi list, I figured I'd explain my commit here, since I don't know how you handle your issue tracker. While I was loading some code in my image (Universes iirc), I got a lot of warnings pop up, about Url>>#toText being deprecated. After taking a look at it, I saw that the deprecation comment recommended using instead Url>>#asText. Which I tried, but it broke most of the SUnits and also the expected behaviour. Looking at the code, I saw that Url>>#toText simply did ^self asString, when Url>>#asText does ^self asString asText. The semantic leap between Text and String is too big (imo) to force that change on users. I thought it would be better to replace the deprecation comment to recommend replacing the obsolote Url>>#toText by Url>>#asString (which is what this method actually does). I would rather have removed the method, since it has been marked for obsolete for more than 3 years now! But I don't know what the approach is to deleting methods, and how to communicate to people that this isn't a missing method but an intentional removal. I hope this helps understand this version. Cheers, Yann

3 4

[Pharo-project] Update 10082
by Norbert Hartl Sept. 28, 2008

Sept. 28, 2008

In 10082 the script is buggy. script174 contains a line with only .mcz and one line with an archive Pinesoft-Removals-EToys-stephane.ducasse.1.mcz that is not in the repository. Norbert

2 5

Sept. 28, 2008

because there is a package Network YM 44 Please please avoid to use initials. Stef

3 3

Sept. 28, 2008

Hi all I'm slowing going over gary's fixes and cleaning etoy. Etoy cleaning from gary (continued) Removed UndefinedObjectTest>>testNewTileMorphRepresentative Removed BooleanTest>>testNewTileMorphRepresentative Removed BookMorph>>chooseAndRevertToVersion Removed BookMorph>>revertToCheckpoint: secsSince1901 BookMorph>>installRollBackButtons BookMorph>>methodHolderVersions BookMorph>>methodHolders BookMoprh>>goToPageMorph: transitionSpec: runTransitionScripts: BookMorph>>goToPageMorph: transitionSpec: TabbedPalette>>selectTab: cleaned Removed TabbedPalette>>becomeStandPalette Removed>>currentPlayerDo: and fixed sender EncodedCharSet fixed initialize stef

1 0