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

[pharo-project/pharo-core] b609c1: 60316

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: b609c15965d52acf119f3912127d7d6c9925fbfd https://github.com/pharo-project/pharo-core/commit/b609c15965d52acf119f3912… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-12-05 (Mon, 05 Dec 2016) Changed paths: A GT-InspectorExtensions-Core.package/extension/Collection/instance/gtCollectionSizeThreshold.st M GT-InspectorExtensions-Core.package/extension/Collection/instance/gtDisplayOn_.st M GT-InspectorExtensions-Core.package/extension/SequenceableCollection/instance/gtInspectorItemsIn_.st M GT-SpotterExtensions-Core.package/extension/Collection/instance/spotterItemsFor_.st M Rubric.package/RubSmalltalkCodeMode.class/class/menu/menuOn_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60315.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60316.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60315.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60316.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/TextModel.class/instance/api/accept_notifying_.st Log Message: ----------- 60316 19418 Spec TextModel editor has broken cancel operation after first accept https://pharo.fogbugz.com/f/cases/19418 19413 GTInspector/Debugger do not work for large/ toolarge intervals https://pharo.fogbugz.com/f/cases/19413 19420 redu menu item is wrong and not working for rubric https://pharo.fogbugz.com/f/cases/19420 http://files.pharo.org/image/60/60316.zip

Dec. 5, 2016

Re: [Pharo-dev] OCASTTranslator forValue/forEffect

by Nicolai Hess

2016-12-05 8:51 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com>: > Translate AST to byte codes? > (For opal, this first creates the intermediate representation (IR), but yes translating from AST to (finally) byte codes) > One for the case when we don't care of the result (we will pop it off the > stack), we just want the effect. > Ok. > The other case when we want to keep the resulting value on the stack. > Who decides which to use, when do I know that I need to use, the effect translator only or the value translator? > > 2016-12-05 8:47 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> Hi, >> >> I need a short description for what the OCASTTranslator subclasses >> OCASTTranslatorForEffect >> OCASTTranslatorForValue >> are. >> >> I don't fully understand the usage. >> >> thanks in advance >> Nicolai >> >> >

Dec. 5, 2016

Re: [Pharo-dev] OCASTTranslator forValue/forEffect

by ClÃ©ment Bera

On Mon, Dec 5, 2016 at 8:51 AM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > Translate AST to byte codes? > One for the case when we don't care of the result (we will pop it off the > stack), we just want the effect. > The other case when we want to keep the resulting value on the stack. > It translates AST to Opal's IR. And yes one uses one or the other if one wants only the effect and don't care about the result or if one cares about the result and the effect. > > 2016-12-05 8:47 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> Hi, >> >> I need a short description for what the OCASTTranslator subclasses >> OCASTTranslatorForEffect >> OCASTTranslatorForValue >> are. >> >> I don't fully understand the usage. >> >> thanks in advance >> Nicolai >> >> >

Dec. 5, 2016

Re: [Pharo-dev] OCASTTranslator forValue/forEffect

by Nicolas Cellier

Translate AST to byte codes? One for the case when we don't care of the result (we will pop it off the stack), we just want the effect. The other case when we want to keep the resulting value on the stack. 2016-12-05 8:47 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > Hi, > > I need a short description for what the OCASTTranslator subclasses > OCASTTranslatorForEffect > OCASTTranslatorForValue > are. > > I don't fully understand the usage. > > thanks in advance > Nicolai > >

Dec. 5, 2016

OCASTTranslator forValue/forEffect

by Nicolai Hess

Hi, I need a short description for what the OCASTTranslator subclasses OCASTTranslatorForEffect OCASTTranslatorForValue are. I don't fully understand the usage. thanks in advance Nicolai

Dec. 5, 2016

R: Re: New to Pharo; a bunch of questions.

by dario.trussardi

Frp Inviato da smartphone Samsung Galaxy.-------- Messaggio originale --------Da: Ben Coman <btc(a)openinworld.com> Data: 02/10/2016 16:19 (GMT+01:00) A: Pharo Development List <pharo-dev(a)lists.pharo.org> Oggetto: Re: [Pharo-dev] New to Pharo; a bunch of questions. On Sun, Oct 2, 2016 at 8:10 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > Hi, > > a) creating a class is message send like any other... and the returned value is the newly created class. > > So you can do > > locellClass := Object subclass: #LOCell. > locellClass compile: 'myMethod'. > > b) Alternatively (what I usually do), is `#MyClass asClass` (or Smalltalk classNamed: #MyClass). > > Note that using the former (`asClass`) is (justly) frowned upon when used in regular code, but it is perfectly fine in Playground. (Just like 'MyPackage' asPackage, etc.) > > As for distribution (which you've mentioned in another mail), I write code like this in my startup scripts, e.g. https://github.com/peteruhnak/pharo-scripts/blob/master/config/5.0/roassal-… > > Likewise you can just file-out a method, class, or package(s) and send that to another person, who can just file it in. > > Final note regarding your string operations... try to avoid using comma to concat many strings, using stream is preferable (from both performance and readability), e.g. The performance aspect is not absolute and depends on usage... http://forum.world.st/Stream-instead-of-string-concatenation-td4856891.html http://forum.world.st/When-to-use-a-stream-for-concatenating-text-td4811093… cheers -ben > > LOCell compile: (String streamContents: [ :stream | >Â Â Â Â Â Â Â Â stream >Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â nextPutAll: 'initialize'; cr; >Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â nextPutAll: 'Â Â Â super initialize.'; cr. > ]). > > Also Pharo understands multiline strings just fine, so you can do this: > > LOCell compile: 'initialize >Â Â Â Â super initialize. >Â Â Â Â self label: ''''. >Â Â Â Â self borderWidth: 2' > > > If you need to specify parameters, take a look at String>>format: > > 'Today is {1}.' format: {Date today}. > 'Today is {date}.' format: (Dictionary with: #date->Date today). > > Peter > > > On Sat, Oct 01, 2016 at 12:39:26PM -0700, CodeDmitry wrote: >> >> ([ >>Â Â Â Â LOCell compile: >>Â Â Â Â Â Â Â Â 'initialize', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â super initialize.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â self label: ''''.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â self borderWidth: 2.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â bounds := (0@0) corner: (16@16).', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â offColor := Color paleYellow.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â onColor := Color paleBlue darker.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â self useSquareCorners.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â self turnOff.' >> ] value). >> >> ([ >>Â Â Â Â LOGame compile: >>Â Â Â Â Â Â Â Â 'cellsPerSide', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â ^10' >> ] value). >> >> ([ >>Â Â Â Â LOGame compile: >>Â Â Â Â Â Â Â Â 'toggleNeighboursOfCellAt: i at: j', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â (i > 1) ifTrue: [', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â (cells at: i - 1 at: j) toggleState.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â ].', (String cr), >>Â Â Â Â Â Â Â Â (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â (i < self cellsPerSide) ifTrue: [', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â (cells at: i + 1 at: j) toggleState.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â ].', (String cr), >>Â Â Â Â Â Â Â Â (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â (j > 1) ifTrue: [', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â (cells at: i at: j - 1) toggleState.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â ].', (String cr), >>Â Â Â Â Â Â Â Â (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â (j < self cellsPerSide) ifTrue: [', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â (cells at: i at: j + 1) toggleState.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â ].' >> ] value). >> >> ([ >>Â Â Â Â LOGame compile: >>Â Â Â Â Â Â Â Â 'newCellAt: i at: j', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â | c origin | ', (String cr), >>Â Â Â Â Â Â Â Â (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â c := LOCell new.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â origin := self innerBounds origin.', (String cr), >>Â Â Â Â Â Â Â Â (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â self addMorph: c.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â ', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â c position: ([', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â | x_index y_index c_width c_height |', (String cr), >>Â Â Â Â Â Â Â Â (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â x_index := i - 1.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â y_index := j - 1.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â c_width := c width.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â c_height := c height.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â ', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â (x_index * c_width)@(y_index * c_height) + origin', (String >> cr), >>Â Â Â Â Â Â Â Â 'Â Â Â ] value).', (String cr), >>Â Â Â Â Â Â Â Â (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â c mouseAction: [', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â self toggleNeighboursOfCellAt: i at: j.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â ].', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â ^ c.', (String cr) >> ] value). >> >> ([ >>Â Â Â Â LOGame compile: >>Â Â Â Â Â Â Â Â 'initialize', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â | sampleCell width height n |', (String cr), >>Â Â Â Â Â Â Â Â (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â super initialize.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â n := self cellsPerSide.', (String cr), >>Â Â Â Â Â Â Â Â (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â sampleCell := LOCell new.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â width := sampleCell width.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â height := sampleCell height.', (String cr), >>Â Â Â Â Â Â Â Â (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â self bounds: ', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â ((5@5) extent:', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â Â Â Â Â (width * n)@(height * n) + ', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â Â Â Â Â (2 * (self borderWidth))).', (String cr), >>Â Â Â Â Â Â Â Â (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â cells := Matrix new: n tabulate: [:i :j |', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â Â Â Â Â self newCellAt: i at: j.', (String cr), >>Â Â Â Â Â Â Â Â 'Â Â Â ].' >> ] value). >> >> >> >> >> -- >> View this message in context: http://forum.world.st/New-to-Pharo-a-bunch-of-questions-tp4917701p4917707.h… >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >

Dec. 4, 2016

Re: [Pharo-dev] Seaside / Getting Started

by Nicolai Hess

2016-12-04 1:33 GMT+01:00 Paul DeBruicker <pdebruic(a)gmail.com>: > the seaside list is here: > > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > Ah, seaside list, thanks for the hint :) Nicolai > > > > > > Nicolai Hess-3-2 wrote > > 2016-11-26 12:34 GMT+01:00 Nicolai Hess < > > > nicolaihess@ > > > >: > > > >> > >> > >> 2016-11-26 12:06 GMT+01:00 Nicolai Hess < > > > nicolaihess@ > > > >: > >> > >>> Hi, > >>> > >>> I am currently reviewing the Seaside chapter of "Pharo By Example 5". > >>> > >>> (more questions will follow) > >>> > >> > >> More questions: > >> From the book: "You can put Seaside into deployment mode using either > the > >> configuration page (navigate to the entry for the application and click > >> on > >> the Configure link) or click the Configure button in the toolbar." > >> > >> I see this configuration linke: > >> (configure_environment.PNG) > >> but disabling the development toolbar option, does not seem to make any > >> difference: > >> (configer_development.PNG) > >> (even after starting a new session). > >> > >> the only way I found is to remove the inherited tool decoration > >> tool_decoration.PNG > >> > >> From the book:"You can also set the mode globally by evaluating > >> WAGlobalConfiguration setDeploymentMode or WAGlobalConfiguration > >> setDevelopmentMode." > >> But there is now WAGlobalConfiguration, not even any implementor for a > >> "deploymentmode" message > >> > >> > > > > Any one? > > > > > > -- > View this message in context: http://forum.world.st/Seaside- > Getting-Started-tp4924834p4925651.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Dec. 4, 2016

Re: [Pharo-dev] Seaside / Getting Started

by Paul DeBruicker

the seaside list is here: http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside Nicolai Hess-3-2 wrote > 2016-11-26 12:34 GMT+01:00 Nicolai Hess < > nicolaihess@ > >: > >> >> >> 2016-11-26 12:06 GMT+01:00 Nicolai Hess < > nicolaihess@ > >: >> >>> Hi, >>> >>> I am currently reviewing the Seaside chapter of "Pharo By Example 5". >>> >>> (more questions will follow) >>> >> >> More questions: >> From the book: "You can put Seaside into deployment mode using either the >> configuration page (navigate to the entry for the application and click >> on >> the Configure link) or click the Configure button in the toolbar." >> >> I see this configuration linke: >> (configure_environment.PNG) >> but disabling the development toolbar option, does not seem to make any >> difference: >> (configer_development.PNG) >> (even after starting a new session). >> >> the only way I found is to remove the inherited tool decoration >> tool_decoration.PNG >> >> From the book:"You can also set the mode globally by evaluating >> WAGlobalConfiguration setDeploymentMode or WAGlobalConfiguration >> setDevelopmentMode." >> But there is now WAGlobalConfiguration, not even any implementor for a >> "deploymentmode" message >> >> > > Any one? -- View this message in context: http://forum.world.st/Seaside-Getting-Started-tp4924834p4925651.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Dec. 4, 2016

Re: [Pharo-dev] Seaside / Getting Started

by Nicolai Hess

2016-11-26 12:34 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > 2016-11-26 12:06 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> Hi, >> >> I am currently reviewing the Seaside chapter of "Pharo By Example 5". >> >> (more questions will follow) >> > > More questions: > From the book: "You can put Seaside into deployment mode using either the > configuration page (navigate to the entry for the application and click on > the Configure link) or click the Configure button in the toolbar." > > I see this configuration linke: > (configure_environment.PNG) > but disabling the development toolbar option, does not seem to make any > difference: > (configer_development.PNG) > (even after starting a new session). > > the only way I found is to remove the inherited tool decoration > tool_decoration.PNG > > From the book:"You can also set the mode globally by evaluating > WAGlobalConfiguration setDeploymentMode or WAGlobalConfiguration > setDevelopmentMode." > But there is now WAGlobalConfiguration, not even any implementor for a > "deploymentmode" message > > Any one?

Dec. 3, 2016

Re: [Pharo-dev] how to find projects on github

by Dale Henrichs

You can narrow your search to Smalltalk language projects with this search: iceberg language:Smalltalk One hit ... Dale On 12/3/16 8:10 AM, Stephane Ducasse wrote: > We should have a registration mechanism or sharing all some tags. > > On Sat, Dec 3, 2016 at 2:32 PM, philippe.back(a)highoctane.be > <mailto:philippe.back@highoctane.be> <philippe.back(a)gmail.com > <mailto:philippe.back@gmail.com>> wrote: > > Project on github or not, if it is added to the catalog with a > configuration one should find it. > > Now if it is on github maybe a tool opening a web browser on the > project page could be handy. > > Phil > > Le 3 dÃ©c. 2016 13:50, "Stephane Ducasse" <stepharo.self(a)gmail.com > <mailto:stepharo.self@gmail.com>> a Ã©crit : > > I prefer that it works for you. may be I did something strange. > > On Wed, Nov 30, 2016 at 9:41 PM, Sven Van Caekenberghe > <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: > > Yes, you are evil; for me it is the 3rd hit: > > > But the project misses a top level description ... > >> On 30 Nov 2016, at 21:31, stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>> wrote: >> >> Hi >> >> I said to nicolas that I should use my super evil power >> to break iceberg >> as requested by him. So I tried. >> >> So I went to github and I typed >> iceberg pharo >> pharo iceberg >> passerini >> iceberg >> then I browsed pharo-core and related and I could not >> find anything. >> >> I miss the smalltalkhub.com/list >> <http://smalltalkhub.com/list> >> >> >> Stef >> >> -- >> > > >

Dec. 3, 2016