- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 5323b0: 40161

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 5323b0744238156df1a407a0ea1b7806323a237d https://github.com/pharo-project/pharo-core/commit/5323b0744238156df1a407a0… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-08-07 (Thu, 07 Aug 2014) Changed paths: M Nautilus.package/ClassWidget.class/instance/protocol/showHierarchy_.st M NautilusCommon.package/AnnotationRequest.class/instance/requests/implementorsCount.st R NautilusCommon.package/extension/SystemNavigation/instance/browseSharedPoolUsersOf_.st R NautilusCommon.package/extension/SystemNavigation/instance/confirmRemovalOfSelectors_on_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script161.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40161.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Support.package/SystemNavigation.class/instance/query/allUnsentMessagesIn_.st R System-Support.package/SystemNavigation.class/instance/query/numberOfImplementorsOf_.st A Tool-Base.package/extension/SystemNavigation/instance/browseSharedPoolUsersOf_.st A Tool-Base.package/extension/SystemNavigation/instance/classFromPattern_withCaption_.st A Tool-Base.package/extension/SystemNavigation/instance/confirmRemovalOfSelectors_on_.st A Tool-Base.package/extension/SystemNavigation/instance/confirmRemovalOf_on_.st M Tool-Browser-Old.package/CodeHolder.class/instance/annotation/annotationForSelector_ofClass_.st R Tools.package/extension/SystemNavigation/instance/classFromPattern_withCaption_.st R Tools.package/extension/SystemNavigation/instance/confirmRemovalOf_on_.st Log Message: ----------- 40161 13795 Browsing certain classes takes several seconds https://pharo.fogbugz.com/f/cases/13795 13800 another small SystemNavigation cleanup https://pharo.fogbugz.com/f/cases/13800 13798 empty package UI can be deleted https://pharo.fogbugz.com/f/cases/13798 http://files.pharo.org/image/40/40161.zip

Aug. 7, 2014

[pharo-project/pharo-core]

by GitHub

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

Aug. 7, 2014

Re: [Pharo-dev] Deprecator

by Sean P. DeNigris

camille teruel wrote > It's because I don't want users to have to know RB pattern syntax and also > because I plan to not depend on the rewriter in future versions. Ah I see. RB is powerful and well-known. While easy to replace for simple cases, I wonder if you might be forced to either limit that power or reinvent the wheel... Why not just rely on RB, which was designed for this and battle hardened over many years? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Deprecator-tp4769843p4772319.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 7, 2014

Re: [Pharo-dev] Deprecator

by Camille Teruel

On 7 aoÃ»t 2014, at 16:32, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Sean P. DeNigris wrote >> How do you activate it? > > Oh, okay. I guess from looking at the tests that the new pragma is > <deprecatedIn:replaceWith:> > > Next problem ;)... > > I see that you've omitted the RB `@ syntax. While easier to type, I don't > like that it's more magical - It's because I don't want users to have to know RB pattern syntax and also because I plan to not depend on the rewriter in future versions. > what is the list of string tokens that are > meaningful? The available metavariables are: receiver: the receiver expression of the sending message node arg1, ..., arg15: the arguments expression of the sending message node > Also, now the following now fails to compile with an "Unbounded > variable" error > preferencesGeneralFolder > <deprecatedIn: 'Pharo 3.0' replaceWith: 'StartupPreferencesLoader > preferencesGeneralFolder'> I look at it now :) > But this capability is /very/ exciting!! Thanks :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Deprecator-tp4769843p4772316.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Aug. 7, 2014

Re: [Pharo-dev] Deprecator

by Sean P. DeNigris

Sean P. DeNigris wrote > How do you activate it? Oh, okay. I guess from looking at the tests that the new pragma is <deprecatedIn:replaceWith:> Next problem ;)... I see that you've omitted the RB `@ syntax. While easier to type, I don't like that it's more magical - what is the list of string tokens that are meaningful? Also, now the following now fails to compile with an "Unbounded variable" error preferencesGeneralFolder <deprecatedIn: 'Pharo 3.0' replaceWith: 'StartupPreferencesLoader preferencesGeneralFolder'> But this capability is /very/ exciting!! Thanks :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Deprecator-tp4769843p4772316.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 7, 2014

Re: [Pharo-dev] Deprecator

by Camille Teruel

On 7 aoÃ»t 2014, at 16:15, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > camille teruel wrote >> I hope for comments > > How do you activate it? I loaded into #40160, and copied your snippets from > the post, but when I did "MyClass new senderMethod", no debugger came up... Hello Sean, Sorry, I did a few modifications that I didn't reported here. First, the pragma changed. Now it's <deprecatedIn: #versionSymbol replaceWith: 'rewriteString'>. Second, the syntax changed: the '`@' that were needed before (for the RBParseTreeRewriter) are gone. So each available metavariable are written directly: receiver, arg1, arg2, ... arg15. You need the latest version (8). So the example is now: C>>deprecatedMethodArg1: o1 arg2: o2 <deprecatedIn: #Pharo42 replaceWith: 'receiver replacementMethodArg1: arg2 arg2: arg1'> ^ #deprecated C>>replacementMethodArg1: o1 arg2: o2 ^ #replacement C>>senderMethod ^ self deprecatedMethodArg1: 1 + 1 arg2: 2 + 2. Then evaluating C new senderMethod should bring the following pre-debug window. Cheers, Camille > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Deprecator-tp4769843p4772312.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Aug. 7, 2014

Re: [Pharo-dev] Athens WorldMorph

by Nicolai Hess

Ok, thank you. 2014-08-07 13:31 GMT+02:00 Igor Stasenko <siguctua(a)gmail.com>: > Very nice! Please commit this code to Athens repository. > We will integrate it > > http://smalltalkhub.com/mc/Pharo/Athens/main > > This is a good way to debug stuff without killing own world :) > > Just in case, i added you as Athens contributor, so you can commit. > > > > On 7 August 2014 12:14, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> I created some fogbugz entries for morphs drawing with athens api. >> >> And a parent case 13790 "Port what is needed for Athens (drawing morphs)" >> >> We can test the Athens based drawing by putting the morphs into an >> AthensWrapMorph. >> But this is difficult for Morph like Dialog, Menus and SystemWindows. >> >> So for testing purpose I attached changeset to the >> issue 13790 : >> a small hack for making a second WorldMorph working in a Morph. >> I omit all the small little details that are needed to make a >> second WorldMorph fully working. I just wanted to make >> sure the second WorldMorph doesn't constantly try to occupy >> the whole display. >> The real fun is to put this WorldMorph inside an AthensWrapMorph. >> That way we can test Athens based drawing even for Morphs >> like the WorldMenu or SystemWindows. >> Just drag and drop a Morph or Window between >> the Athens WorldMorph and the real WorldMorph. >> >> Open the AthensWrapWorldMorph with: >> AthensWrapWorldMorph new openInWorld >> >> >> nicolai >> > > > > -- > Best regards, > Igor Stasenko. >

Aug. 7, 2014

Re: [Pharo-dev] Deprecator

by Sean P. DeNigris

camille teruel wrote > I hope for comments How do you activate it? I loaded into #40160, and copied your snippets from the post, but when I did "MyClass new senderMethod", no debugger came up... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Deprecator-tp4769843p4772312.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 7, 2014

Re: [Pharo-dev] About your contributions: Improve Pharo right now, right there.

by stepharo

I added a description on the contribute page http://pharo.org/contribute

Aug. 7, 2014

Re: [Pharo-dev] About your contributions: Improve Pharo right now, right there.

by stepharo

> Okay, so thatâs good, but you guys /really/ need to improve the > documentation on the mechanical walkthrough of how to actually claim > and submit a bug fix. > > Today, I happened to have some spare time, so I figured, what the > hell, why not see if I canât fix some bugs blocking the Pharo 4 > release. Itâs a reach, granted, but I used to be good at Smalltalk, > Iâm still a good programmer, and I figure at least one of the blockers > is in the really-annoying-but-technically-easy bucket that no one was > willing to touch yet, so chances are good. > > Armed with my old knowledge of how Squeak contrib used to work, I at > least got as far as manually downloading a VM, manually downloading a > .changes/.image, and manually downloading a .sources. Then I go to > pharo.org <http://pharo.org> andâ¦ > > Well, hmm. No instructions on the submission or development process? > Well, no matter, I know you guys use FogBugz, so maybe on the FogBugz > wiki? The landing page is unhelpful; clicking on the word âhereâ at > âReporting or Fixing a Bug?â takes me to http://pharo.org/get-involved > which is a 404. Heading back, I try âDocumentationâ, which contains a > lot of documentation, but none how to//submit fixes. You know the guy doing the video remove it because it was in rage against us. We were not aware that it was linked them. > Likewise, I can get great info on the workflow of a bug, but not on > how to move code through that workflow. > > At this point, by luck, I realize that thereâs a link to âContributeâ > in the TOC in FogBugz. Brilliant, exactly what I want! And it has a > video walkthrough, no less, which takes me to > http://vimeo.com/75183993 andâ¦nope, thatâs a 404 again. Thankfully, > the link below it appears to let me download a nice MP4, which > /does/ walk me throughâ¦submitting a slice. I actually have no idea if > this is the right way to do things anymore, but given that you guys > /seem/ to have a super-active GitHub repo, I kind of doubt it. And > while thereâs some documentation scattered around about how to use Git > and Pharo, itâs not centralized or obvious. > > Itâs up to the community to be involved with the tools they love and > to submit patches, and youâre totally right to remind everyone that > itâs up to us to improve Pharo if we want to keep it alive, but itâs > up to the core team to make sure that itâs easy for us to do so, and I > think that Pharoâs not doing terribly well on that front right now. > We add a description on the old web site but he got lost. Now in a nutshell, to submit a fix - donwload latest image (there is a script on download) - do a fix for a giving bug - publish a slice press (+ slice) in MC, add the dirty packages - publish it in the inbox (click on inbox and press save) - take a fresh image. - reload it and check that it fixes the problem (open MC and click on inbox + open). Does it help? Was it so complex? > âBenjamin

Aug. 7, 2014