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

About contents of Pharo by Example updated

by stepharo

Hi I'm looking at some chapters of Pharo by Example like environment that presents many tools and I think that I cannot spend time updating this chapter. What I will do is to have one tool per page with a small description and key points. Else the book will again get obsolete. I do not know what you think but I do not have the cycles for all the tiny details. Stef

Feb. 24, 2016

Re: [Pharo-dev] Process>>restart

by Max Leske

I like the idea. I implemented something similar recently and one of the real advantages is that you can kill (suspend, inspect, etc.) such a process. Fast spawning processes are very hard to debug (e.g. in the process browser). Max > On 24 Feb 2016, at 16:23, Ben Coman <btc(a)openInWorld.com> wrote: > > Just sharing a passing thought so I don't forget it before I have time > to think more deeply on it. > > Several parts of Pharo (like SHTextStyler) are designed to have a > background process running, and when new input arrives that process is > killed so another can be immediately started - and sometimes we seem > to end up with large amounts of zombie processes. > > As I poke around Process>>terminate, I wonder if a different approach > would be to have a Process>>restart. I see there is Context>>restart. > > The starting the background process might look like... > > stylingProcess := [ [ "do stuff with nextData". self suspend ] > repeat ] forkAt: 30. > > and the code in the main morphic priority 40 thread might look like... > > sylingProcess suspend. > nextData := 'blah'. > sylingProcess restart. > > anyway, back to the grind for me, > cheers -ben >

Feb. 24, 2016

Re: [Pharo-dev] search query?

by Tudor Girba

Hi, Indeed, the ghost text is wrong. It is a plain wildcard type of search. E.g.: - prefix* - *postfix - *middle* I already fixed it in the latest Glamour and GT. Cheers, Doru > On Feb 24, 2016, at 6:59 PM, stepharo <stepharo(a)free.fr> wrote: > > Hi > > in the debugger we get a search and I wonder what it is. > I type true, each > and nothing happens (well I do not get the methods list). > I think that the ghost text is misleading since we should/can only type > selectors. > > > <egjabhgf..png> -- www.tudorgirba.com www.feenk.com "Value is always contextual."

Feb. 24, 2016

Re: [Pharo-dev] [Pharo-users] help needed for testing the order in spotter

by Esteban Lorenzano

right now feels a lot better than before. also the explicit (visible) keybingins to filter are a great addition :) Esteban > On 24 Feb 2016, at 19:34, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Thanks. Indeed, I agree with you. In fact, this is what we did, and then I was told that people would rather want to discuss beforehand :). So, actually, this was a little experiment. > > The thing is that we do not want to disturb people, but we need the feedback to improve fast. So, right now it looks like the only real way to get feedback is to push the changes. This has the tendency to create some annoyance, but we are trying to react as fast as we can to limit it. I hope this will be Ok with everyone. > > Cheers, > Doru > > >> On Feb 24, 2016, at 7:29 PM, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: >> >> Hi Doru, >> >> I don't see a better way to have beta-testers than having your code on the pharo alpha image ;) >> You will have very soon feedback and then you can iterate. >> >> Cheers, >> Christophe >> > > -- > www.tudorgirba.com > www.feenk.com > > "Speaking louder won't make the point worthier." > >

Feb. 24, 2016

Re: [Pharo-dev] Spotter changes broke CodePanel

by Stephan Eggermont

On 24-02-16 19:37, Tudor Girba wrote: > Hi, > > Could you provide a fully loadable sample to look at this? Just load NewUI from the configuration browser. Stephan

Feb. 24, 2016

Re: [Pharo-dev] Spotter changes broke CodePanel

by Tudor Girba

Hi, Could you provide a fully loadable sample to look at this? Cheers, Doru > On Feb 24, 2016, at 11:52 AM, Stephan Eggermont <stephan(a)stack.nl> wrote: > > I used to do > > CodePanel class>>spot > GTSpotterMorph new > extent: (World width / 3.25 @ (World height / 2.25)) asIntegerPoint; > spotterModel: ((GTSpotter new) > processorsFilter: (CodePanelProcessorFilter new > configuredWith: [ :aProcessor | aProcessor > actLogic: [ :aMethod :step | > step exit. > aMethod ifNil: [ self new openInWindowLabeled: 'Code panel' ] > ifNotNil: [ |panel| > panel := self new. > panel openInWindowLabeled: 'Code panel'. > panel newCardFor: aMethod.]]; > candidatesLimit: 50 ])); > openCenteredInWorld > > That now (since at least 50596) an interesting Brick error. > Do I need to change my code? > > Stephan > > > <PharoDebug.log> -- www.tudorgirba.com www.feenk.com "Being happy is a matter of choice."

Feb. 24, 2016

Re: [Pharo-dev] [Pharo-users] help needed for testing the order in spotter

by Tudor Girba

Hi, Thanks. Indeed, I agree with you. In fact, this is what we did, and then I was told that people would rather want to discuss beforehand :). So, actually, this was a little experiment. The thing is that we do not want to disturb people, but we need the feedback to improve fast. So, right now it looks like the only real way to get feedback is to push the changes. This has the tendency to create some annoyance, but we are trying to react as fast as we can to limit it. I hope this will be Ok with everyone. Cheers, Doru > On Feb 24, 2016, at 7:29 PM, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > Hi Doru, > > I don't see a better way to have beta-testers than having your code on the pharo alpha image ;) > You will have very soon feedback and then you can iterate. > > Cheers, > Christophe > -- www.tudorgirba.com www.feenk.com "Speaking louder won't make the point worthier."

Feb. 24, 2016

ReÂ : Re: [Pharo-users] help needed for testing the order in spotter

by Christophe Demarey

Hi Doru, I don't see a better way to have beta-testers than having your code on the pharo alpha image ;) You will have very soon feedback and then you can iterate. Cheers, Christophe

Feb. 24, 2016

[pharo-project/pharo-core]

by GitHub

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

Feb. 24, 2016

[pharo-project/pharo-core] 4a36b4: 50610

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 4a36b431071a12a261972903db068263009cf5a9 https://github.com/pharo-project/pharo-core/commit/4a36b431071a12a261972903… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-24 (Wed, 24 Feb 2016) Changed paths: M Refactoring-Critics.package/RBSentNotImplementedRule.class/definition.st R Refactoring-Critics.package/RBSentNotImplementedRule.class/instance/accessing/implementorsCache.st M Refactoring-Critics.package/RBSentNotImplementedRule.class/instance/accessing/implementorsExists_.st R Refactoring-Critics.package/RBSentNotImplementedRule.class/instance/private/resetImplementorsCache.st R Refactoring-Critics.package/RBSentNotImplementedRule.class/instance/running/checkClass_.st A Rubric.package/RubEditingArea.class/instance/initialize-release/beForSmalltalkCodeInClass_.st A Rubric.package/RubScrolledTextMorph.class/instance/initialize-release/beForSmalltalkCodeInClass_.st M Rubric.package/RubSmalltalkCodeMode.class/definition.st M Rubric.package/RubSmalltalkCodeMode.class/instance/shout/classOrMetaClass_.st A Rubric.package/RubSmalltalkCodeMode.class/instance/shout/updateStyler.st M Rubric.package/RubSmalltalkCodeMode.class/instance/shout/withShoutStyler.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50609.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50610.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50609.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50610.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A SmartSuggestions.package/SugsProcessBrowserContext.class/README.md A SmartSuggestions.package/SugsProcessBrowserContext.class/definition.st A SmartSuggestions.package/SugsProcessBrowserContext.class/instance/refactoring/sourceTextArea.st A SmartSuggestions.package/SugsProcessBrowserContext.class/instance/selection/selectedClass.st A SmartSuggestions.package/SugsProcessBrowserContext.class/instance/selection/selectedMethod.st A SmartSuggestions.package/SugsTranscriptContext.class/README.md A SmartSuggestions.package/SugsTranscriptContext.class/definition.st A SmartSuggestions.package/SugsTranscriptContext.class/instance/refactoring/selectedClass.st A SmartSuggestions.package/SugsTranscriptContext.class/instance/refactoring/selectedMethod.st A SmartSuggestions.package/SugsTranscriptContext.class/instance/refactoring/sourceTextArea.st M SmartSuggestions.package/extension/DiffMorph/instance/sugsContext.st A SmartSuggestions.package/extension/ProcessBrowser/instance/sugsContext.st A SmartSuggestions.package/extension/ThreadSafeTranscript/instance/sugsContext.st M Spec-MorphicAdapters.package/MorphicTextAdapter.class/instance/private/setEditingModeFor_withBehavior_.st M Spec-MorphicAdapters.package/MorphicTextAdapter.class/instance/spec protocol/classOrMetaClass_.st A Tool-ProcessBrowser.package/ProcessBrowser.class/instance/accessing/methodText.st M Tool-ProcessBrowser.package/ProcessBrowser.class/instance/accessing/selectedMethod.st M Tool-ProcessBrowser.package/ProcessBrowser.class/instance/accessing/stackListIndex_.st M Tool-ProcessBrowser.package/ProcessBrowser.class/instance/stack list/changeStackListTo_.st M Tool-ProcessBrowser.package/ProcessBrowser.class/instance/views/build.st Log Message: ----------- 50610 17683 but right button (menu) is broken in process browser https://pharo.fogbugz.com/f/cases/17683 17688 speedup RBSentNotImplementedRule https://pharo.fogbugz.com/f/cases/17688 17065 Transcript has no context menu https://pharo.fogbugz.com/f/cases/17065 17684 highlighting broken in message list (senders off / implementors of) https://pharo.fogbugz.com/f/cases/17684 http://files.pharo.org/image/50/50610.zip

Feb. 24, 2016