May 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Trying to use Rubric in Nautilus ....

by Alain Plantec

Maybe you should use RubSmalltalkMethodEditorModel (one have also RubSmalltalkScriptEditorModel). Have a look at RubWorkspaceExample to see how it can be used. Alain > On 12 mai 2015, at 16:40, stepharo <stepharo(a)free.fr> wrote: > > Hi > > we are trying with Franck Warlouzet to use Rubric in Nautilus > and we saw that getMenuSelector is missing. > > on: aModel text: aGetTextSelector accept: aSetTextSelector readSelection: aReadSelectionSelector menu: aGetMenuSelector > self getTextSelector: aGetTextSelector. > self setTextSelector: aSetTextSelector. > self getSelectionSelector: aReadSelectionSelector. > "self getMenuSelector: aGetMenuSelector." > self on: aModel > > > Alain > > we are trying to adapt > > buildCodePane > > sourceTextArea := self textMorphClass > on: self > text: #sourceCodeFrom: > accept: #compileSource:notifying: > readSelection: #contentsSelectionFrom: > menu: #sourceCodeMenu:shifted:. > > sourceTextArea > askBeforeDiscardingEdits: true; > vResizing: #spaceFill; > hResizing: #spaceFill; > font: StandardFonts codeFont; > spaceFillWeight: 3; > on: #keyStroke send: #keyStroke:fromSourceCodeMorph: to: self. > > self setSourceCodeShorcutsTo: sourceTextArea. > ^ sourceTextArea > > to use Rubric > > buildCodePane > > widget := RubScrolledTextMorph new. > widget > on: self > text: #sourceCodeFrom: > accept: #compileSource:notifying: > readSelection: #contentsSelectionFrom: > menu: #sourceCodeMenu:shifted:. > widget > beWrapped; > beForSmalltalkCode; > withLineNumbers; > setText: self sourceCode; > getTextSelector: #halt. > ^ widget > > > And now we do not get how the widget can be notified when a new method is selected. > > Alain :) > >

May 12, 2015

Trying to use Rubric in Nautilus ....

by stepharo

Hi we are trying with Franck Warlouzet to use Rubric in Nautilus and we saw that getMenuSelector is missing. on: aModel text: aGetTextSelector accept: aSetTextSelector readSelection: aReadSelectionSelector menu: aGetMenuSelector self getTextSelector: aGetTextSelector. self setTextSelector: aSetTextSelector. self getSelectionSelector: aReadSelectionSelector. "self getMenuSelector: aGetMenuSelector." self on: aModel Alain we are trying to adapt buildCodePane sourceTextArea := self textMorphClass on: self text: #sourceCodeFrom: accept: #compileSource:notifying: readSelection: #contentsSelectionFrom: menu: #sourceCodeMenu:shifted:. sourceTextArea askBeforeDiscardingEdits: true; vResizing: #spaceFill; hResizing: #spaceFill; font: StandardFonts codeFont; spaceFillWeight: 3; on: #keyStroke send: #keyStroke:fromSourceCodeMorph: to: self. self setSourceCodeShorcutsTo: sourceTextArea. ^ sourceTextArea to use Rubric buildCodePane widget := RubScrolledTextMorph new. widget on: self text: #sourceCodeFrom: accept: #compileSource:notifying: readSelection: #contentsSelectionFrom: menu: #sourceCodeMenu:shifted:. widget beWrapped; beForSmalltalkCode; withLineNumbers; setText: self sourceCode; getTextSelector: #halt. ^ widget And now we do not get how the widget can be notified when a new method is selected. Alain :)

May 12, 2015

Re: [Pharo-dev] Package comments

by Ben Coman

Try to have it so users don't have to delete much, just extend what is there. On Tue, May 12, 2015 at 2:10 AM, Kasper Osterbye <kasper(a)itu.dk> wrote: > Sergio Fedi and I are now working on this. > > As part of the work, we need a "default package comment", akin the the > default class comment. The class comment is inspired by CRC idea. > Translating CRC to a PRC, we suggest the following, and ask for comments > from the community. As I believe we will by the end of the year have a > inworld pillar renderer which is fairly stable, the default PRC template > could be: > 'Please comment me using the following ""template"", ''inspired'' by Class > Responsibility Collaborator (CRC) design: > 'inspired'' by Class Responsibility Collaborator (CRC) design, written in first-person narrative: > > !Package XXX, part of (reference to main package if one exist) > one line description: For example, I'm xxx package, containing the > hierarchy > of visitor objects. > One line description: I'm Xyz package, providing widgets that ... (Leave "Part of package" for Collaborators (see below) ) > > ;Responsibiliies > :Three sentences about my main responsibility, what I'm doing, what classes > do I offer. > (Three sentences is not much to talk about all the package's classes. How about...) I offer services for ... > ;Collaborators :State my related packages, and which classes are the ones used from the > outside of the package. > I'm part of Abc package ... My related packages are ... My entry points are ... > !!Public API > - message one in class one > - message two in class two > - what is the way to use this package. > > One simple example is simply gorgeous. Or refer to which package is the > main package if there are several packages in play > > !!Internal Representation and Key Implementation Points. > > -Implementation Points, in particular references to classes with good class > comments.' > > Will this work? > > Nice initiative. cheers -ben

May 12, 2015

Re: [Pharo-dev] On Missing Class: Why not describe error?

by Damien Pollet

I just faced that trying to load variableByteSubclasses of NBExternalStructâ¦ somehow I managed to not immediately give up with the whole thingâ¦ but seriously this is a real efficient way to instantly reach my frustration limit. On 11 May 2015 at 21:59, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Sean P. DeNigris wrote > > Any reason not to make it... > > Issue 15524: CodeImport: Better info on non-existent behavior > https://pharo.fogbugz.com/default.asp?15524 > > Fix in inbox: > > SLICE-Issue-15524-CodeImport-Better-info-on-non-existent-behavior-SeanDeNigris.1 > > - Put which class and which label in the error message > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/On-Missing-Class-Why-not-describe-error-tp4825681p482… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

May 12, 2015

[pharo-project/pharo-core]

by GitHub

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

May 12, 2015

[pharo-project/pharo-core] a8f0b5: 50044

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: a8f0b58e4d6cde18536abffa4b33b41a41aefe23 https://github.com/pharo-project/pharo-core/commit/a8f0b58e4d6cde18536abffa… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-05-12 (Tue, 12 May 2015) Changed paths: A AST-Core.package/RBConfigurableFormatter.class/instance/public interface/containerWidth_.st A AST-Core.package/RBNullFormatter.class/README.md A AST-Core.package/RBNullFormatter.class/definition.st A AST-Core.package/RBNullFormatter.class/instance/public interface/containerWidth_.st A AST-Core.package/RBNullFormatter.class/instance/public interface/format_.st R AST-Core.package/RBParseErrorNode.class/instance/accessing/isFaulty.st A AST-Core.package/RBParseErrorNode.class/instance/converting/asSyntaxErrorNotification.st A AST-Core.package/RBParseErrorNode.class/instance/testing/isFaulty.st M AST-Core.package/RBProgramNode.class/class/accessing/formatterClass.st M AST-Core.package/RBProgramNode.class/instance/accessing/formattedCode.st A AST-Core.package/RBProgramNode.class/instance/accessing/formattedCodeWithMaxLineLength_.st M CodeImport.package/MethodDeclaration.class/instance/importing/handleMissingBehavior.st M FileSystem-Disk.package/WindowsStore.class/instance/converting/printPath_on_.st A FileSystem-Tests-Disk.package/WindowsStoreTest.class/instance/testing/testPrintString.st A OpalCompiler-Core.package/OCASTTranslator.class/instance/visitor/visitParseErrorNode_.st A OpalCompiler-Core.package/OCASTTranslatorForEffect.class/instance/visitor-double dispatching/visitParseErrorNode_.st A OpalCompiler-Tests.package/OCCompileWithFailureTest.class/README.md A OpalCompiler-Tests.package/OCCompileWithFailureTest.class/definition.st A OpalCompiler-Tests.package/OCCompileWithFailureTest.class/instance/tests/testEvalSimpleMethodWithError.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50043.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50044.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50043.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50044.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50044 15526 Code generation for ASTs with syntax errors https://pharo.fogbugz.com/f/cases/15526 15527 creation of RBNullFormatter in AST-Core https://pharo.fogbugz.com/f/cases/15527 15524 CodeImport: Better Error Info On Non-existent Behavior https://pharo.fogbugz.com/f/cases/15524 15519 error on printString for FileReference https://pharo.fogbugz.com/f/cases/15519 http://files.pharo.org/image/50/50044.zip

May 12, 2015

Re: [Pharo-dev] Pharo Screencast By a Ruby Guy

by Sean P. DeNigris

Tudor Girba-2 wrote > I think he did a marvelous job for a newcomer. +1. For me, he cut straight the most important thing - the power of a live environment - all the technical details are secondary. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-Screencast-By-a-Ruby-Guy-tp4825891p4825960.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 12, 2015

Installing trait blow the method def in hierarchy

by Yuriy Tymchuk

Hi, Iâve noticed that if you install a trait on a class and a trait defines explicit requirement method, and this method is defined in a super class, it is being looked up during execution through #explicitRequirement method. It was slowing down my execution by almost 20%. Is there a special way to use a Trait to avoid that, or itâs work-in-progress solution? Uko

May 12, 2015

Re: [Pharo-dev] Pharo Screencast By a Ruby Guy

by Tudor Girba

Indeed, this is a major area for Pharo that requires significant overhaul :) Cheers, Doru On Tue, May 12, 2015 at 11:56 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > > On 12 May 2015, at 11:44, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > >> On 11 May 2015, at 23:49, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > >> > >> > http://devblog.avdi.org/2015/05/11/in-which-i-make-you-hate-ruby-in-7-minut… > > > > Not a perfect demo (he could have run the tests from within the > browser), but nice to see how (some) outsiders think about Pharo > > Which brings us to the conclusion, that we have to improve improve dx for > TDD :) > > Uko > > > > >> ----- > >> Cheers, > >> Sean > >> -- > >> View this message in context: > http://forum.world.st/Pharo-Screencast-By-a-Ruby-Guy-tp4825891.html > >> Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >> > > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

May 12, 2015

Re: [Pharo-dev] Pharo Screencast By a Ruby Guy

by Yuriy Tymchuk

> On 12 May 2015, at 11:44, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 11 May 2015, at 23:49, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> http://devblog.avdi.org/2015/05/11/in-which-i-make-you-hate-ruby-in-7-minut… > > Not a perfect demo (he could have run the tests from within the browser), but nice to see how (some) outsiders think about Pharo Which brings us to the conclusion, that we have to improve improve dx for TDD :) Uko > >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/Pharo-Screencast-By-a-Ruby-Guy-tp4825891.html >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > >

May 12, 2015