February 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Review]: Case 12737 Morph sends mouseUp twice to handlers

by Sean P. DeNigris

Sean P. DeNigris wrote > https://pharo.fogbugz.com/default.asp?12737 I did a safer fix which is much less likely to break other things and still fixes the problem. Two people looked at it and the monkey validated it. Should I "Fix to include" or would a core dev like to have a quick look first. I'm being extra cautious because it is inside Morphic... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Review-Case-12737-Morph-sends-mouseUp-twice-to-handle… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 1, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by GOUBIER Thierry

Johan, It wasn't when I ported. Now, it is. Thanks! Thierry ________________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Johan Fabry [jfabry(a)dcc.uchile.cl] Date d'envoi : samedi 1 fÃ©vrier 2014 14:50 Ã : Pharo Development List Objet : Re: [Pharo-dev] poolDictionaries removal breaks my projects Please note that the change IS at the Nautilus level. The default class description is the same as before! Your class porting example is unharmed by this change. On Feb 1, 2014, at 7:16 AM, GOUBIER Thierry <thierry.goubier(a)cea.fr> wrote: > Shortening the default class description is also painfull when you port code, because it makes the class appear different (description with and without pool dictionaries) in the change sorter. I wrote a pac change reader to port SmaCC from Dolphin to Pharo, and, really, this kind of change makes that unusable. > > In short, make that change correctly: at the Nautilus level. It's a GUI issue, not a language issue. ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

Feb. 1, 2014

How to suck (and yet be awesome)

by Sebastian Sastre

I wish we could take one day off workâ¦ sit all in a room to watch this science-backed stuff: KATHY SIERRA: BUILDING THE MINIMUM BADASS USER, BUSINESS OF SOFTWARE. A MASTERCLASS IN THINKING ABOUT SOFTWARE PRODUCT DEVELOPMENT. http://businessofsoftware.org/2013/02/kathy-sierra-building-the-minimum-bad… and then have face to face conversations I leave you with just this quote: People doesnât use your product because they like it or because they like you People use your product because they like themselves What are you doing to enable more of that? sebastian o/

Feb. 1, 2014

Re: [Pharo-dev] Can someone help me with this issue 12469 (Sometimes an empty protocol is created)

by Nicolai Hess

2014-02-01 Sven Van Caekenberghe <sven(a)stfx.eu>: > I believe Marcus said that the validator takes the highest numbered > version. Yours is .2 and Ben's is .3 even though it is older. You can save > a .4 one by manually editing the name just before saving. > > On 01 Feb 2014, at 18:29, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > I tried a dozen times to create a slice for the fix. > > Every time the slice marks the all classes and methods as changed, > > even so, I only changed some methods. > > > > Now I have finally uploaded a slice with only my changes but.. > > The Validator chooses an older slice for validation ? > > ( > https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/9284//artifact/vali… > ) > > > > I don't know anymore, what I can do, I despair. > > > > > > Nicolai > > > > > > I don't know how to do it. If I choose save I get a MCPermissionDenied error. :(

Feb. 1, 2014

Re: [Pharo-dev] Can someone help me with this issue 12469 (Sometimes an empty protocol is created)

by Sven Van Caekenberghe

I looked at your slice while integrating some other changes - it looked clean. Are you going to try to rename it or should I give it a try ? On 01 Feb 2014, at 18:29, Nicolai Hess <nicolaihess(a)web.de> wrote: > I tried a dozen times to create a slice for the fix. > Every time the slice marks the all classes and methods as changed, > even so, I only changed some methods. > > Now I have finally uploaded a slice with only my changes but.. > The Validator chooses an older slice for validation ? > (https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/9284//artifact/vali…) > > I don't know anymore, what I can do, I despair. > > > Nicolai > >

Feb. 1, 2014

[pharo-project/pharo-core] 5ea61e: 30734

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 5ea61e56e16a0efe7cb6de6db80e9d5aacab4064 https://github.com/pharo-project/pharo-core/commit/5ea61e56e16a0efe7cb6de6d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-02-01 (Sat, 01 Feb 2014) Changed paths: M FileSystem-Core.package/IllegalName.class/README.md M FileSystem-Tests-Core.package/AbstractEnumerationVisitorTest.class/README.md M FileSystem-Tests-Core.package/BreadthFirstGuideTest.class/README.md M FileSystem-Tests-Core.package/CollectVisitorTest.class/README.md M FileSystem-Tests-Core.package/CopyVisitorTest.class/README.md M FileSystem-Tests-Core.package/DeleteVisitorTest.class/README.md M FileSystem-Tests-Core.package/DirectoryEntryTest.class/README.md M FileSystem-Tests-Core.package/FileLocatorTest.class/README.md M FileSystem-Tests-Core.package/FileReferenceTest.class/README.md M FileSystem-Tests-Core.package/FileSystemHandleTest.class/README.md M FileSystem-Tests-Core.package/FileSystemResolverTest.class/README.md M FileSystem-Tests-Core.package/FileSystemTreeTest.class/README.md M FileSystem-Tests-Core.package/GuideTest.class/README.md M FileSystem-Tests-Core.package/InteractiveResolverTest.class/README.md M FileSystem-Tests-Core.package/PathTest.class/README.md M FileSystem-Tests-Core.package/PlatformResolverTest.class/README.md M FileSystem-Tests-Core.package/PostorderGuideTest.class/README.md M FileSystem-Tests-Core.package/PreorderGuideTest.class/README.md M FileSystem-Tests-Core.package/SelectVisitorTest.class/README.md M FileSystem-Tests-Core.package/SingleTreeTest.class/README.md M FileSystem-Tests-Core.package/SystemResolverTest.class/README.md M FileSystem-Tests-Disk.package/DiskFileSystemTest.class/README.md M FileSystem-Tests-Disk.package/FileHandleTest.class/README.md M FileSystem-Tests-Disk.package/WindowsStoreTest.class/README.md M FileSystem-Tests-Memory.package/MemoryFileSystemTest.class/README.md M FileSystem-Tests-Memory.package/MemoryHandleTest.class/README.md M Kernel.package/Process.class/instance/accessing/isTerminated.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script387.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30734.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Changes.package/CurrentChangeSetChanged.class/README.md M System-Clipboard.package/MacOSClipboard.class/README.md M System-FilePackage.package/FilePackage.class/README.md M System-FilePackage.package/PseudoMetaclass.class/README.md M System-Hashing.package/HashFunction.class/README.md M System-Installers.package/MczInstaller.class/README.md M System-Localization.package/ISOLanguageDefinition.class/README.md M System-Localization.package/LocaleID.class/README.md M System-Settings.package/MultipleSettingDeclaration.class/README.md M System-Settings.package/SettingNodeBuilder.class/README.md M System-Settings.package/SettingTreeBuilder.class/README.md M System-Settings.package/SystemSettingLauncher.class/README.md M System-Support.package/ExternalDropHandler.class/README.md M UIManager.package/DummySystemProgressItem.class/README.md M UIManager.package/ProvideAnswerNotification.class/README.md Log Message: ----------- 30734 12761 Class comments missing for FileSystem package https://pharo.fogbugz.com/f/cases/12761 11674 MNU: receiver of #> is nil https://pharo.fogbugz.com/f/cases/11674 12762 Class comments missing in UIManager https://pharo.fogbugz.com/f/cases/12762 12756 Class comments missing in System-* package https://pharo.fogbugz.com/f/cases/12756 http://files.pharo.org/image/30/30734.zip

Feb. 1, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30734 Home: https://github.com/pharo-project/pharo-core

Feb. 1, 2014

Re: [Pharo-dev] Can someone help me with this issue 12469 (Sometimes an empty protocol is created)

by Sven Van Caekenberghe

I believe Marcus said that the validator takes the highest numbered version. Yours is .2 and Ben's is .3 even though it is older. You can save a .4 one by manually editing the name just before saving. On 01 Feb 2014, at 18:29, Nicolai Hess <nicolaihess(a)web.de> wrote: > I tried a dozen times to create a slice for the fix. > Every time the slice marks the all classes and methods as changed, > even so, I only changed some methods. > > Now I have finally uploaded a slice with only my changes but.. > The Validator chooses an older slice for validation ? > (https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/9284//artifact/vali…) > > I don't know anymore, what I can do, I despair. > > > Nicolai > >

Feb. 1, 2014

Recruit more volunteers

by Sebastian Sastre

Smalltalk gives here only 4 hits in this site where people wanting to learn might reach the community: http://openhatch.org/search/ Not Amber not Pharo not Squeak are there Leave a seed? sebastian o/

Feb. 1, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Sebastian Sastre

Just to clarify... 5 emails saying âitâs okayâ plus no active complains is a whole different thing than making usability tests with 5 users. I wish so much I could say that Nautilus rocks, seriously Itâs a pity because the community is putting so much effort on it On Feb 1, 2014, at 2:41 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > Sent today at 10:37 AM chilean time, a few minutes before I sent the mail you are replying to. Same subject as this mail. For completeness, here is the content: > >> For what it's worth: this was asked on the users list (some months ago). There were about 5 replies and they were positive. I do not recall having any negative replies. >> >> I think that asking much more than that is hard, given the nature of mailing lists and the comity being busy with many other things. >> >> Also, having learned about user studies and performed a few (for this "science" thing I'm supposed to be doing), I can tell you that getting a really representative group of users together is nearly impossible in the scenario we are in. So anything you can get out of an inquiry will just be 'some people say: OK'. Nothing is guaranteed about other people. Which is just what is happening here ! ;-) >> >> On Jan 31, 2014, at 6:43 PM, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: >> >>> Lets says it convinces youâ¦ >>> >>> Time to be skeptic. Test. >>> >>> Test with someone else. Tests it with 5 guys and ask how they feel about it. >>> >>> Hear.

Feb. 1, 2014