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

Re: [Pharo-dev] Protrammatic selection in Glamour

by Martin McClure

On 10/02/2016 02:03 PM, Andrei Chis wrote: > The #selection: message of a presentation should update the selection. > Let me know if it doesn't work as expected for you. Thanks for the confirmation. I'd tried that, but it didn't seem to do anything. Let me experiment to make sure I'm doing what I think I'm doing. -Martin > > On Sun, Oct 2, 2016 at 9:15 PM, Martin McClure <martin(a)hand2mouse.com > <mailto:martin@hand2mouse.com>> wrote: > > Is there a way in Glamour to programmatically select an item in a > list or tree presentation? (That is, having the same effect as > clicking on the item.) I'm using the Glamour in Pharo 5. > > Thanks, > > -Martin > >

Oct. 2, 2016

Re: [Pharo-dev] Protrammatic selection in Glamour

by Andrei Chis

The #selection: message of a presentation should update the selection. Let me know if it doesn't work as expected for you. Cheers, Andrei On Sun, Oct 2, 2016 at 9:15 PM, Martin McClure <martin(a)hand2mouse.com> wrote: > Is there a way in Glamour to programmatically select an item in a list or > tree presentation? (That is, having the same effect as clicking on the > item.) I'm using the Glamour in Pharo 5. > > Thanks, > > -Martin > >

Oct. 2, 2016

DNU: WeakArray>>#copyGrownBy:

by Aliaksei Syrel

Pharo 6.0 Latest update: #60246 [image: Inline images 1] Cheers, Alex

Oct. 2, 2016

Protrammatic selection in Glamour

by Martin McClure

Is there a way in Glamour to programmatically select an item in a list or tree presentation? (That is, having the same effect as clicking on the item.) I'm using the Glamour in Pharo 5. Thanks, -Martin

Oct. 2, 2016

Re: [Pharo-dev] New to Pharo; a bunch of questions.

by stepharo

Better use the fileout menu you will get all the code of your class/package inside a file. Stef Le 2/10/16 Ã 12:02, CodeDmitry a Ã©crit : > It's just nice to have a standalone code that I can give to my friends that > they can read and run to create the structure without having to setup > everything themselves, but at the same time not needing to use a package. A > standalone script is quite elegant for situations like that, since it well > encapsulates the automation without forcing people to understand packaging. > > > > -- > View this message in context: http://forum.world.st/New-to-Pharo-a-bunch-of-questions-tp4917701p4917764.h… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Oct. 2, 2016

Re: [Pharo-dev] New to Pharo; a bunch of questions.

by Ben Coman

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. >> >

Oct. 2, 2016

compiling code on background / in parallel

by Peter Uhnak

Hi, can anyone think of some inherent danger to performing code compilation on background? E.g. [ cls := Object subclass: #Something. cls addInstVarNamed: #myVar. cls addInstVarNamed: #myVar2. cls addInstVarNamed: #myVar3. cls compile: 'method'. cls compile: 'myVar ^ myVar'. cls compile: 'myVar3 ^ myVar3'. cls removeInstVarNamed: #myVar3. ] fork. Parallel operations on the same class are not an issue for me, but I don't know if this can lead to some eventual corruption (because Pharo assumes that e.g. changes file is locked etc.). Or e.g. installing new project/package on the background while I countinue doing my work (=writing code). Thanks, Peter

Oct. 2, 2016

Re: [Pharo-dev] New to Pharo; a bunch of questions.

by Peter Uhnak

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. 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. >

Oct. 2, 2016

Re: [Pharo-dev] New to Pharo; a bunch of questions.

by CodeDmitry

It's just nice to have a standalone code that I can give to my friends that they can read and run to create the structure without having to setup everything themselves, but at the same time not needing to use a package. A standalone script is quite elegant for situations like that, since it well encapsulates the automation without forcing people to understand packaging. -- View this message in context: http://forum.world.st/New-to-Pharo-a-bunch-of-questions-tp4917701p4917764.h… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 2, 2016

Re: [Pharo-dev] New to Pharo; a bunch of questions.

by Dimitris Chloupis

This a problem I have long identified with Smalltalk that Pharo inherits. The fact that workspace is disconnected from System Browser. But I never bothered fixing because of other priorities. Personally I am suprised you ask why one would want a more close connection between System Browser and Workspace/Playground , isn't it obvious it would speed up workflow considerably ? My workaround has been not to use Playground at all and instead work directly with System Browser. I use playground only to trigger class execution. Even that is not necessary because of the script pragma which makes possible to trigger execution directly from System Browser. This is not just a problem of Workspace only , all tools inside Smaltalkl are disconnected with exception of inspector and debugger . The king of integration and the best example of how to connect a tool with others is GTSpotter. Of course that is also what makes GTSpotter so popular. On Sun, 2 Oct 2016 at 08:19, stepharo <stepharo(a)free.fr> wrote: > But why do you want that? Why do you want to code everything in the > playground? > > > Le 1/10/16 Ã 21:58, CodeDmitry a Ã©crit : > > Thanks Peter! I admit I couldnt really dynamically add methods to a > class at > > runtime since I was doing it as follows: > > > > ([ > > (LOCell class) methodDict > > at: #mouseAction > > put: ((LOCell class) compile: > > mouseAction: a > > ^ mouseAction := a > > ). > > ] value). > > > > Which caused constant harassment by Pharo until I typed: > > > > (LOCell class) removeAllKeys. > > > > or > > > > (LOCell class) removeKey: #mouseAction. > > > > I'll try your method in a bit to see if it works better. > > But you are using black magic incantation instead of using the class > browser > So do not complain if you shoot in your feet in the future. > > I would not code like that because you will just get frustrated and you > will > think pharo is bad while we are all using hyper fast and safe and we > keep black magic > for the place we want it. > > Stef > > > > > > > > > > > > -- > > View this message in context: > http://forum.world.st/New-to-Pharo-a-bunch-of-questions-tp4917701p4917706.h… > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > > > >

Oct. 2, 2016