Pharo-users

By thread

pharo-users@lists.pharo.org

April 2014

76 participants
540 messages

Re: [Pharo-users] create instance var accesors from menu (Pharo 3.0)

by Camille Teruel

In the browser, right-click on the class in question, then Refactoring -> Class Refactoring -> Generate Accessors The little "h, a" indicate that the keyboard shortcut is mod+h+a where mod is your OS-specific modifier key for Pharo shortcuts (ctrl on linux and windows, command on osx). On 1 avr. 2014, at 17:46, Roelof Wobben <r.wobben(a)home.nl> wrote: > Hello, > > On squeeze 3.9 you can make them with a menu. > > Is there a simular way I can do the same in Pharo 3.0 ? > > Roelof >

April 1, 2014

create instance var accesors from menu (Pharo 3.0)

by Roelof Wobben

Hello, On squeeze 3.9 you can make them with a menu. Is there a simular way I can do the same in Pharo 3.0 ? Roelof

April 1, 2014

Re: [Pharo-users] lasergame question

by Roelof Wobben

April 1, 2014

Re: [Pharo-users] lasergame question

by Ben Coman

April 1, 2014

Re: [Pharo-users] lasergame question

by Ben Coman

April 1, 2014

Re: [Pharo-users] lasergame question

by Camille Teruel

On 1 avr. 2014, at 16:50, Roelof Wobben <r.wobben(a)home.nl> wrote: > Nicolai Hess schreef op 1-4-2014 16:44: >> 2014-04-01 16:21 GMT+02:00 Roelof Wobben <r.wobben(a)home.nl>: >> Camille Teruel schreef op 1-4-2014 15:08: >> >> On 1 avr. 2014, at 14:52, Roelof Wobben <r.wobben(a)home.nl> wrote: >> >> Hello, >> Hello, >> >> Im on this page now: http://squeak.preeminent.org/tut2007/html/017.html >> >> I do not understand one thing. >> >> Where do I put the initialize "script" >> #initialize is not a script, it's a method. When an object is instantiated (for ex with: MyObject new) #initialize is automatically sent to it. >> This is the place to put your newly created object in a correct initial state. >> In your class, you just define a protocol named for example "initialization" where you put all the initialization-related methods. >> Note that protocols have no meaning, i.e. they don't change how your objects behave, they're just here to help you classify >> the methods of a class by concerns. >> So the tutorial tell you to create two methods: #initialize that is automatically called after an object has been instantiated and #initializeActiveSegments where you >> put some other initialization logic, that's all. >> >> When I put it on the initializeActiveSegments then initialize get not found. >> Sorry, I don't understand. >> >> Or must I make a seperate protocol named ActiveSegments for it. >> No use the same protocol "initialization" or "initialize-release" or whatever. >> >> >> Oke, >> >> I changed it so I have this : >> >> Laser-Game-Model >> with as classes: >> - BlankCell >> - Grid >> - MirrorCell >> -TargetCell >> >> >> BlankCell has the following protocols: >> - initializing-release >> - testing >> >> Initializing - release contains the following methods: >> - initialize >> - initializeActiveSegments >> >> testing contains the following methods: >> isOn >> isOff >> >> but when I run the test-runner I see this : MessageNotUnderstood : BlankCell >> activeSegments. >> >> Roelof >> >> >> >> >> >> Then you missed the last step on http://squeak.preeminent.org/tut2007/html/016.html >> Select "create instance var accessors" from the second popup menu. >> >> >> > > > I also did. > See this : > > Object subclass: #BlankCell > instanceVariableNames: 'activeSegments' > classVariableNames: '' > category: 'Laser-Game-Model' This message just serve as a class definition, it basically says "I want a class named BlankCell, subclass of Object, with one instance variable named activeSegments, in the category Laser-Game-Model". But, it says nothing about BlankCell methods. So as Nicolai pointed out, you forgot to do the last step of page 16. It will create two methods for accessing the instance variable activeSegments: First an accessor method: BlankCell>>activeSegments ^ activeSegments And a mutator (you should rename the argument to better convey the intent) BlankCell>>activeSegments: anObject activeSegments := anObject > > Roelof >

April 1, 2014

Re: [Pharo-users] lasergame question

by Ben Coman

Roelof Wobben wrote: > Camille Teruel schreef op 1-4-2014 15:08: >> On 1 avr. 2014, at 14:52, Roelof Wobben <r.wobben(a)home.nl> wrote: >> >>> Hello, >> Hello, >> >>> Im on this page now: http://squeak.preeminent.org/tut2007/html/017.html >>> >>> I do not understand one thing. >>> >>> Where do I put the initialize "script" >> #initialize is not a script, it's a method. When an object is >> instantiated (for ex with: MyObject new) #initialize is automatically >> sent to it. >> This is the place to put your newly created object in a correct >> initial state. >> In your class, you just define a protocol named for example >> "initialization" where you put all the initialization-related methods. >> Note that protocols have no meaning, i.e. they don't change how your >> objects behave, they're just here to help you classify >> the methods of a class by concerns. >> So the tutorial tell you to create two methods: #initialize that is >> automatically called after an object has been instantiated and >> #initializeActiveSegments where you >> put some other initialization logic, that's all. >> >>> When I put it on the initializeActiveSegments then initialize get >>> not found. >> Sorry, I don't understand. >> >>> Or must I make a seperate protocol named ActiveSegments for it. >> No use the same protocol "initialization" or "initialize-release" or >> whatever. >> > > Oke, > > I changed it so I have this : > > Laser-Game-Model > with as classes: > - BlankCell > - Grid > - MirrorCell > -TargetCell > > > BlankCell has the following protocols: > - initializing-release > - testing > > Initializing - release contains the following methods: > - initialize > - initializeActiveSegments > > testing contains the following methods: > isOn > isOff > > but when I run the test-runner I see this : MessageNotUnderstood : > BlankCell >> activeSegments. > > Roelof Now first as an aside, I'll just mention something that caught me out when I went through this tutorial when I was quite new to Smalltalk, which is paying attention to whether you are defining methods on the instance-side or the class-side, as indicated by which of the <instance> or <class> button is highlighted. Now for BlankCell, if you select protocol --all-- do you see a method #activeSegments ? The lack of that method is the cause of the MessageNotUnderstood. Looking at the previous page it says "Add an instance variable "activeSegments" and "We will use Squeak's built-in tools to create accessors for this new instance variable" I would say something went wrong there. Consider the last snapshot of page 16. cheers -ben

April 1, 2014

Re: [Pharo-users] lasergame question

by Camille Teruel

On 1 avr. 2014, at 16:39, Roelof Wobben <r.wobben(a)home.nl> wrote: > Camille Teruel schreef op 1-4-2014 16:34: >> >> On 1 avr. 2014, at 16:21, Roelof Wobben <r.wobben(a)home.nl> wrote: >> >>> Camille Teruel schreef op 1-4-2014 15:08: >>>> On 1 avr. 2014, at 14:52, Roelof Wobben <r.wobben(a)home.nl> wrote: >>>> >>>>> Hello, >>>> Hello, >>>> >>>>> Im on this page now: http://squeak.preeminent.org/tut2007/html/017.html >>>>> >>>>> I do not understand one thing. >>>>> >>>>> Where do I put the initialize "script" >>>> #initialize is not a script, it's a method. When an object is instantiated (for ex with: MyObject new) #initialize is automatically sent to it. >>>> This is the place to put your newly created object in a correct initial state. >>>> In your class, you just define a protocol named for example "initialization" where you put all the initialization-related methods. >>>> Note that protocols have no meaning, i.e. they don't change how your objects behave, they're just here to help you classify >>>> the methods of a class by concerns. >>>> So the tutorial tell you to create two methods: #initialize that is automatically called after an object has been instantiated and #initializeActiveSegments where you >>>> put some other initialization logic, that's all. >>>> >>>>> When I put it on the initializeActiveSegments then initialize get not found. >>>> Sorry, I don't understand. >>>> >>>>> Or must I make a seperate protocol named ActiveSegments for it. >>>> No use the same protocol "initialization" or "initialize-release" or whatever. >>>> >>> >>> Oke, >>> >>> I changed it so I have this : >>> >>> Laser-Game-Model >>> with as classes: >>> - BlankCell >>> - Grid >>> - MirrorCell >>> -TargetCell >>> >>> >>> BlankCell has the following protocols: >>> - initializing-release >>> - testing >>> >>> Initializing - release contains the following methods: >>> - initialize >>> - initializeActiveSegments >>> >>> testing contains the following methods: >>> isOn >>> isOff >>> >>> but when I run the test-runner I see this : MessageNotUnderstood : BlankCell >> activeSegments. >> >> This error means "instances of BlankCell does not understand the message #activeSegments" that's all, this part of your program is not implemented yet. >> > > Im not agree with you according to the tutorial on this page : http://squeak.preeminent.org/tut2007/html/019.html there is a error with isOn and isOff. There is no way to be agree or not with that, MessageNotUnderstood is an error thrown when a message is ..., well, ... not understood. So no method named activeSegments is defined in BlankCell hierarchy, it's as simple as that. > #activeSegments schould be implemented by now. Well according to the DNU error, it is not. So I guess you missed some step in the tutorial. > > Roelof >

April 1, 2014

Re: [Pharo-users] lasergame question

by Roelof Wobben

April 1, 2014

Re: [Pharo-users] lasergame question

by Nicolai Hess

2014-04-01 16:21 GMT+02:00 Roelof Wobben <r.wobben(a)home.nl>: > Camille Teruel schreef op 1-4-2014 15:08: > > On 1 avr. 2014, at 14:52, Roelof Wobben <r.wobben(a)home.nl> wrote: >> >> Hello, >>> >> Hello, >> >> Im on this page now: http://squeak.preeminent.org/tut2007/html/017.html >>> >>> I do not understand one thing. >>> >>> Where do I put the initialize "script" >>> >> #initialize is not a script, it's a method. When an object is >> instantiated (for ex with: MyObject new) #initialize is automatically sent >> to it. >> This is the place to put your newly created object in a correct initial >> state. >> In your class, you just define a protocol named for example >> "initialization" where you put all the initialization-related methods. >> Note that protocols have no meaning, i.e. they don't change how your >> objects behave, they're just here to help you classify >> the methods of a class by concerns. >> So the tutorial tell you to create two methods: #initialize that is >> automatically called after an object has been instantiated and >> #initializeActiveSegments where you >> put some other initialization logic, that's all. >> >> When I put it on the initializeActiveSegments then initialize get not >>> found. >>> >> Sorry, I don't understand. >> >> Or must I make a seperate protocol named ActiveSegments for it. >>> >> No use the same protocol "initialization" or "initialize-release" or >> whatever. >> >> > Oke, > > I changed it so I have this : > > Laser-Game-Model > with as classes: > - BlankCell > - Grid > - MirrorCell > -TargetCell > > > BlankCell has the following protocols: > - initializing-release > - testing > > Initializing - release contains the following methods: > - initialize > - initializeActiveSegments > > testing contains the following methods: > isOn > isOff > > but when I run the test-runner I see this : MessageNotUnderstood : > BlankCell >> activeSegments. > > Roelof > > > > > Then you missed the last step on http://squeak.preeminent.org/tut2007/html/016.html Select "create instance var accessors" from the second popup menu.

April 1, 2014

Jump to page: