- Pharo-dev - lists.pharo.org

Idea for playground

by Yuriy Tymchuk

Hi, sometimes when I play in playground in order to achieve something I can go 10 levels deep or even more. Maybe we can implement an option to somehow construct one script from all executed parts, so then this script can be turned into a method or so on. Uko

April 28, 2015

Re: [Pharo-dev] [Issue tracker] what about old issues?

by Peter UhnÃ¡k

> > 666 open issues >> > The tracker is telling us that old issues are evil. :) -> automatically put them on âclosed, timeoutâ >> -> send a mail to the original submitter AND pharo-dev >> > Maybe in the opposite order? After a period [year] send mail and if no response within a week or two then close it.

April 28, 2015

Pharo 50 has old Rubric Repo

by Sean P. DeNigris

Should be http://smalltalkhub.com/mc/Pharo/Rubric/main/, not Alain's ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-50-has-old-Rubric-Repo-tp4822586.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 28, 2015

[pharo-project/pharo-core]

by GitHub

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

April 28, 2015

[pharo-project/pharo-core] 46ecd2: 50017

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 46ecd285add710a4703568f6814a021905d87e4a https://github.com/pharo-project/pharo-core/commit/46ecd285add710a4703568f6… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-28 (Tue, 28 Apr 2015) Changed paths: R Graphics-Resources.package/extension/ThemeIcons/instance/paintTabIconContents.st R Polymorph-Widgets.package/ThemeIcons.class/instance/accessing - icons/paintTabIcon.st R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/as yet unclassified/tagExec.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tagging/tagExec.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testLinkWithCondition.st M Reflectivity-Tests.package/ReflectivityExamples.class/instance/examples/exampleMethod.st R Reflectivity.package/MetaLink.class/instance/ast/asLiteralNode.st M Reflectivity.package/MetaLink.class/instance/ast/hook.st A Reflectivity.package/extension/Object/instance/asLiteralNode.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script625.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script626.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50016.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50017.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Shout.package/SHTextStylerST80.class/class/style table/attributesFor_pixelHeight_.st Log Message: ----------- 50017 15426 SHRBTextStyler does not work for all predefined styles https://pharo.fogbugz.com/f/cases/15426 15427 Link Condition: Test + fix conditions for links https://pharo.fogbugz.com/f/cases/15427 15259 Remove paintTabIcon https://pharo.fogbugz.com/f/cases/15259 http://files.pharo.org/image/50/50017.zip

April 28, 2015

[Reflectivity] tiny step: conditions for links

by Marcus Denker

Hi, Now with Pharo5 started, I will try to at least do a tiny increment regularly again on Reflectivity (and hopefully larger ones, too). Today: tiny fix: Link condition is working. The idea is that a meta link can have a condition which is compiled into the code. This tiny change makes it work again: testLinkWithCondition | sendNode link condition | condition := false. sendNode := (ReflectivityExamples>>#exampleMethod) ast body statements first value. link := MetaLink new condition: [condition]; metaObject: self; selector: #tagExec. sendNode link: link. self assert: sendNode hasMetalink. self assert: (ReflectivityExamples>>#exampleMethod) class = ReflectiveMethod. self assert: (tag isNil). self assert: (ReflectivityExamples new exampleMethod = 5). self assert: (tag isNil). condition := true. self assert: (ReflectivityExamples new exampleMethod = 5). self assert: (tag = #yes). This is fixed in #50017 (test is green). Next step: when *changing* the condition object (e.g. to true or false or a different block), we need to re-generate code. ==> we need #invalidate on the MetaLink and call it on #condition:. This is the next step for (hopefully) tomorrow. Marcus

April 28, 2015

Re: [Pharo-dev] [Issue tracker] what about old issues?

by Nicolai Hess

2015-04-28 17:44 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > Hi, > > we have 666 open issues on the issue tracker. > > It seems that older issues do not get looked at muchâ¦ the question is what > to do: the more open issues we have, > the less likely they will ever be looked at. > > I would like to > > -> automatically put them on âclosed, timeoutâ > -> send a mail to the original submitter AND pharo-dev > +1 > > This way people can just re-open important issues, but those issues where > the submitter does not care > and nobody else, either, would be closed after one yearâ¦ > (This would e.g. include lots of issues that got fixed in the meantimeâ¦ or > non-important âit would be niceâ > issues, or those where nobody (eve the submitter) understands what this is > about anymoreâ¦) > > Marcus >

April 28, 2015

[Issue tracker] what about old issues?

by Marcus Denker

Hi, we have 666 open issues on the issue tracker. It seems that older issues do not get looked at muchâ¦ the question is what to do: the more open issues we have, the less likely they will ever be looked at. I would like to -> automatically put them on âclosed, timeoutâ -> send a mail to the original submitter AND pharo-dev This way people can just re-open important issues, but those issues where the submitter does not care and nobody else, either, would be closed after one yearâ¦ (This would e.g. include lots of issues that got fixed in the meantimeâ¦ or non-important âit would be niceâ issues, or those where nobody (eve the submitter) understands what this is about anymoreâ¦) Marcus

April 28, 2015

Re: [Pharo-dev] sometimes Shout changes the selection during styling

by Andrei Chis

Ok. I'll make a slice, at latest by tomorrow afternoon. Cheers, Andrei On Tue, Apr 28, 2015 at 4:45 PM, Ben Coman <btc(a)openinworld.com> wrote: > I was waiting for others to chime in, but they can do that on the issue > once code is there to review. I'd say its worth pushing it through to that > point at least. If you do it, I'll review and then we can call for a second > reviewer. > > Actually, semantically the following may be better... > > DelayWaitTimeout>>waitOnCompletion:onTimeout: > > called from... > > Semaphore>>waitTimeoutSeconds:onCompletion:onTimeout: > > cheers -ben > > > > On Tue, Apr 28, 2015 at 8:12 PM, Andrei Chis <chisvasileandrei(a)gmail.com> > wrote: > >> I made an issue: >> https://pharo.fogbugz.com/f/cases/15422/SHTextStyler-styleInBackgroundProce… >> >> Then do we add waitTimeoutSeconds:ifSignalled:ifTimedOut: to the >> Semaphore class? >> >> On Mon, Apr 27, 2015 at 6:33 PM, Andrei Chis <chisvasileandrei(a)gmail.com> >> wrote: >> >>> That would work for me. Styling the text if the process doing the >>> styling did not finish or is stuck does not feel as the right thing to do. >>> >>> On Mon, Apr 27, 2015 at 6:25 PM, Ben Coman <btc(a)openinworld.com> wrote: >>> >>>> >>>> >>>> On Mon, Apr 27, 2015 at 8:41 PM, Andrei Chis < >>>> chisvasileandrei(a)gmail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> In the glamour debugger that we use in moose we are now having the >>>>> following problem: >>>>> - the selection of a PluggableTextMorph is, quite randomly , changed >>>>> during styling. >>>>> >>>>> If I revert the fix for issue 15240 >>>>> <https://pharo.fogbugz.com/f/cases/15240> then it works ok. >>>>> Also if I change in SHTextStyler>>#styleInBackgroundProcess: from >>>>> >>>>> sem waitTimeoutSeconds: 5. >>>>> view ifNotNil: [ view stylerStyledInBackground: text ] >>>>> >>>>> to: >>>>> >>>>> (sem waitTimeoutSeconds: 5) ifFalse: [ >>>>> view ifNotNil: [ view stylerStyledInBackground: text ] ] >>>>> >>>>> it works ok. In the second snippet we only do the styling if the >>>>> styler completed. >>>>> >>>>> >>>>> If I look at the senders of styleInBackgroundProcess: there is another >>>>> strange issue. >>>>> First PluggableTextMorph>>#setText: calls either style: >>>>> or styleInBackgroundProcess:, depending in the size of the text. >>>>> Then, PluggableTextMorph>>#setText: >>>>> calls PluggableTextMorph>>#setTextBasic:, which calls >>>>> PluggableTextMorph>>#hasUnacceptedEdits: which in turn >>>>> calls again styleInBackgroundProcess:. >>>>> So when you set the text if the size of the text is small Shout will >>>>> try to style the text with and without a background process. If you call >>>>> hasUnacceptedEdits: >>>>> manually when initializing the morph then three processes will be >>>>> started for doing the styling. >>>>> >>>>> Removing the calls to styleInBackgroundProcess: from >>>>> PluggableTextMorph>>#hasUnacceptedEdits: and >>>>> PluggableTextMorph>>#basicHasUnacceptedEdits:. >>>>> also solves the problem with the changing selection. >>>>> >>>>> Cheers, >>>>> Andrei >>>>> >>>> >>>> Perhaps we should have... >>>> >>>> sem >>>> waitTimeoutSeconds: 5 >>>> ifSignalled: [ view ifNotNil: [ view stylerStyledInBackground: >>>> text ] ] >>>> ifTimedOut: [ "do nothing" ]. >>>> >>>> cheers -ben >>>> >>> >>> >> > > >

April 28, 2015

[Pharo5] Code Reviewers needed!

by Marcus Denker

Hi, With Pharo5 starting to pick up steam, we need people to help commenting /testing fixes: https://pharo.fogbugz.com/f/filters/45/Review Marcus

April 28, 2015