October 2013 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Proper way of handling multiple exception sections

by Camille Teruel

On 25 oct. 2013, at 13:34, Norbert Hartl <norbert(a)hartl.name> wrote: > Iâm thinking about what would be the proper/least annoying way of having multiple exception sections. If I have a code block that can emit two different exceptions is the only way doing it > > [ [ ... ] > on: Exception1 > do: [ â¦ ] ] > on: Exception2 > do: [ â¦ ] You can handle multiple exceptions like that: [ ... ] on: Exception1, Exception2 do: [ :err | ... ] But there is only one handling block. If you need to have two different handling blocks, I once though of a solution where you would write things like that: [ ... ] exceptionHandler on: Exception1 do: [ ... ]; on: Exception2 do: [ ... ]; execute. The #exceptionHandler message would answer an ExceptionHandler on the block that would be able to manage multiple handling blocks. Something like that: ExceptionHandler >> on: anExceptionClass do: aBlock handlingBlock at: anExceptionClass put: aBlock ExceptionHandler>> handlingBlockFor: anExceptionClass anExceptionClass ifNil: [ ^ nil ]. ^ handlingBlock at: anExceptionClass ifAbsent: [ self handlingBlockFor: anExceptionClass superclass ] ExceptionHandler >>#execute block on: Error do: [ :error | (self handlingBlockFor: error class) ifNil: [ error pass ] ifNotNil: [ :handlingBlock | handlingBlock value ] ] > on:do: just calls a primitive that marks the context being an exception handler. What is called in the image when the stack is scanned to find an exception handler? I think its ContextPart>>#findNextHandlerContextStarting > > thanks, > > Norbert

Oct. 25, 2013

Re: [Pharo-users] Proper way of handling multiple exception sections

by Igor Stasenko

On 25 October 2013 13:34, Norbert Hartl <norbert(a)hartl.name> wrote: > Iâm thinking about what would be the proper/least annoying way of having > multiple exception sections. If I have a code block that can emit two > different exceptions is the only way doing it > > [ [ ... ] > on: Exception1 > do: [ â¦ ] ] > on: Exception2 > do: [ â¦ ] > > on:do: just calls a primitive that marks the context being an exception > handler. What is called in the image when the stack is scanned to find an > exception handler? > > Look at MethodContext exception handling category. Not sure if this answer can satisfies you, because the code there is hard to read and hard to debug. > thanks, > > Norbert > -- Best regards, Igor Stasenko.

Oct. 25, 2013

Proper way of handling multiple exception sections

by Norbert Hartl

Iâm thinking about what would be the proper/least annoying way of having multiple exception sections. If I have a code block that can emit two different exceptions is the only way doing it [ [ ... ] on: Exception1 do: [ â¦ ] ] on: Exception2 do: [ â¦ ] on:do: just calls a primitive that marks the context being an exception handler. What is called in the image when the stack is scanned to find an exception handler? thanks, Norbert

Oct. 25, 2013

Re: [Pharo-users] Spec Question

by Benjamin

On 25 Oct 2013, at 11:34, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> wrote: > Hi, > > I tested it it without hurrying today. > Using Cmd+s with 'whenTextIsAccepted:' works both on Pharo 2.0 and 3.0. > Unfortunately I exchanged the TextModel with TextInputFieldModel where it did not work. > > However, using 'whenTextChanged:' does not work or at least not how I expect it to work. > From the naming I would that this message gets triggered, once something was typed into the textfield. > But apparently it doesn't get triggered at all in my case (Pharo 2.0 and 3.0). > Any ideas? Right now, I canât see why Must probably the event is not triggered, or not at the correct moment Ben > Best, > Manfred > > > > > > On Thu, Oct 24, 2013 at 2:35 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Ok :) > > Thank you, and see you tomorrow :P > > Ben > > On 24 Oct 2013, at 14:34, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> wrote: > >> Yes, I can do that but it'll have to wait until tomorrow. >> Will report back, soon. >> >> Thanks for the help so far, >> Manfred >> >> >> >> >> On Thu, Oct 24, 2013 at 2:29 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> Can you try in 3.0, since Spec changed *a lot* in the meantime >> >> Ben >> >> On 24 Oct 2013, at 14:25, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> wrote: >> >>> Hello Ben and ClÃ©ment, >>> >>> thanks for the quick reply. >>> But even when I hit Cmd+s the Text of the label stays the same and the button is not enabled. >>> No matter if I use 'whenTextChanged:' or 'whenTextIsAccepted:'. >>> >>> I only tested this in the Pharo 2.0 image. >>> >>> Best, >>> Manfred >>> >>> >>> >>> >>> >>> >>> On Thu, Oct 24, 2013 at 2:22 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >>> Hey, >>> >>> Accepting a text usually means the is compiled. To accept a text, right click on it, then click accept in the contextual menu (at the bottom). You can also do it with Cmd+s on Mac. >>> >>> Try again and tell us if the #whenTextIsAccepted: works fine in your image or not. >>> >>> Best, >>> >>> >>> >>> 2013/10/24 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> >>> Text is accepted when you âsaveâ it (cmd+s) >>> >>> Ben >>> >>> On 24 Oct 2013, at 14:05, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> wrote: >>> >>>> Hi everyone, >>>> >>>> I finally got around to check back on a Spec question that popped up about two weeks ago. >>>> >>>> At that time I was giving Spec a first try and gathered information from a couple of sources. >>>> One of them was the draft chapter about Spec from the Pharo for the Enterprise book. >>>> >>>> https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Spec/Sp… >>>> >>>> The example has the following method: >>>> >>>> TestSpec>>initializePresenter >>>> example whenTextIsAccepted: [ changes text: 'The text Changed'. acceptChanges enable ]. >>>> >>>> This should change the text of the 'changes' LabelModel when the text in the 'example' TextModel is accepted. >>>> >>>> >>>> >>>> >>>> >>>> >>>> Now, there the issue for me was that the Label text did not change once when I typed text into the presented textfield. >>>> Even when I changed the method from 'whenTextIsAccepted:' to 'whenTextChanged:'. >>>> Is this intended or is this an issue with Spec? >>>> >>>> Also, it is not clear to me what 'accepting' text means (maybe I didn't look thoroughly enough). >>>> The method comment just states that it is called when the text is accepted. >>>> Which is kind of self referential ;-) >>>> >>>> The OS X Pharo versions I used for testing where newly downloaded Pharo 2.0 and 3.0 from about 2 weeks ago. >>>> They were downloaded from here: >>>> http://files.pharo.org/platform/Pharo2.0-mac.zip >>>> http://files.pharo.org/platform/Pharo3.0-mac.zip >>>> >>>> Best, >>>> Manfred >>> >>> >>> >> >> > >

Oct. 25, 2013

Re: [Pharo-users] Spec Question

by Manfred KrÃ¶hnert

Hi, I tested it it without hurrying today. Using Cmd+s with 'whenTextIsAccepted:' works both on Pharo 2.0 and 3.0. Unfortunately I exchanged the TextModel with TextInputFieldModel where it did not work. However, using 'whenTextChanged:' does not work or at least not how I expect it to work. >From the naming I would that this message gets triggered, once something was typed into the textfield. But apparently it doesn't get triggered at all in my case (Pharo 2.0 and 3.0). Any ideas? Best, Manfred On Thu, Oct 24, 2013 at 2:35 PM, Benjamin < benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Ok :) > > Thank you, and see you tomorrow :P > > Ben > > On 24 Oct 2013, at 14:34, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> > wrote: > > Yes, I can do that but it'll have to wait until tomorrow. > Will report back, soon. > > Thanks for the help so far, > Manfred > > > > > On Thu, Oct 24, 2013 at 2:29 PM, Benjamin < > benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> Can you try in 3.0, since Spec changed *a lot* in the meantime >> >> Ben >> >> On 24 Oct 2013, at 14:25, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> >> wrote: >> >> Hello Ben and ClÃ©ment, >> >> thanks for the quick reply. >> But even when I hit Cmd+s the Text of the label stays the same and the >> button is not enabled. >> No matter if I use 'whenTextChanged:' or 'whenTextIsAccepted:'. >> >> I only tested this in the Pharo 2.0 image. >> >> Best, >> Manfred >> >> >> >> >> >> >> On Thu, Oct 24, 2013 at 2:22 PM, ClÃ©ment Bera <bera.clement(a)gmail.com>wrote: >> >>> Hey, >>> >>> Accepting a text usually means the is compiled. To accept a text, right >>> click on it, then click accept in the contextual menu (at the bottom). You >>> can also do it with Cmd+s on Mac. >>> >>> Try again and tell us if the #whenTextIsAccepted: works fine in your >>> image or not. >>> >>> Best, >>> >>> >>> >>> 2013/10/24 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> >>> >>>> Text is accepted when you âsaveâ it (cmd+s) >>>> >>>> Ben >>>> >>>> On 24 Oct 2013, at 14:05, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> >>>> wrote: >>>> >>>> Hi everyone, >>>> >>>> I finally got around to check back on a Spec question that popped up >>>> about two weeks ago. >>>> >>>> At that time I was giving Spec a first try and gathered information >>>> from a couple of sources. >>>> One of them was the draft chapter about Spec from the Pharo for the >>>> Enterprise book. >>>> >>>> >>>> https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Spec/Sp… >>>> >>>> The example has the following method: >>>> >>>> TestSpec>>initializePresenter >>>> example whenTextIsAccepted: [ changes text: 'The text Changed'. acceptChanges enable ]. >>>> >>>> >>>> This should change the text of the 'changes' LabelModel when the text in the 'example' TextModel is accepted. >>>> >>>> >>>> >>>> >>>> Now, there the issue for me was that the Label text did not change once >>>> when I typed text into the presented textfield. >>>> Even when I changed the method from 'whenTextIsAccepted:' to >>>> 'whenTextChanged:'. >>>> Is this intended or is this an issue with Spec? >>>> >>>> Also, it is not clear to me what 'accepting' text means (maybe I didn't >>>> look thoroughly enough). >>>> The method comment just states that it is called when the text is >>>> accepted. >>>> Which is kind of self referential ;-) >>>> >>>> The OS X Pharo versions I used for testing where newly downloaded Pharo >>>> 2.0 and 3.0 from about 2 weeks ago. >>>> They were downloaded from here: >>>> http://files.pharo.org/platform/Pharo2.0-mac.zip >>>> http://files.pharo.org/platform/Pharo3.0-mac.zip >>>> >>>> Best, >>>> Manfred >>>> >>>> >>>> >>> >> >> > >

Oct. 25, 2013

Arduino package extra files

by Bernat Romagosa

Hi list, After successfully installing the Arduino package, I noticed this Getting Started text: *After installing the Arduino packages by evaluating...* * * * ConfigurationOfArduino load.* * * *...you'll need a couple extra support files in order to be able to upload programs to your Arduino board. You can download them from here:* * * * http://www.mediafire.com/?1rep41uygl4rpf1* * * *Extract the contents of that file in the same directory where you have your Pharo image.* But the mediafire link is broken. Where can I get the extra support files? Thanks! Bernat. -- Bernat Romagosa.

Oct. 25, 2013

Re: [Pharo-users] Three copies of JSON-ul.35 on Smalltalkhub

by StÃ©phane Ducasse

I have problem to add people : Torsten and you to pharoextras I mentioned it to Nicolas. He is looking at it. Stef On Oct 24, 2013, at 6:26 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Hi Stef, > > Will you please add me to the PharoExtras/JSON repo? > > > Thanks > > Paul > > > > On Oct 23, 2013, at 2:09 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> >> On Oct 23, 2013, at 10:25 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >> >>> There are (at least) three locations of the JSON-ul.35 package on Smalltalkhub. >>> >>> Here: >>> http://smalltalkhub.com/#!/~NicolasPetton/JSON/ >>> >>> here: >>> http://smalltalkhub.com/#!/~PharoExtras/JSON/ >>> >>> and here: >>> http://smalltalkhub.com/#!/~pdebruic/JSONg >>> >>> >>> >>> I've also unknowingly duplicated Stef's efforts at making a ConfigurationOfJSON again here: >>> >>> http://smalltalkhub.com/#!/~pdebruic/JSONg (but this version includes the JSON port to Gemstone) >>> >>> >>> Which of the above should we treat as the canonical JSON repository? >> >> If you want to have access to the PharoExtras just ask. >> I like the idea that a team can maintain a set of used libraries. >>> >>> >>> Thanks >>> >>> >>> Paul >> >> > >

Oct. 25, 2013

Re: [Pharo-users] Pharo 2.0 with RFBServer with -headless

by Srikumar Karaikudi Subramanian

Following up .. Almost as soon as I'd written this up, I realized I hadn't tried one thing ... and that worked :) 1. I took the base image from get.pharo.org that I was using on the server, 2. Launched pharo using Pharo2.0.app on that image (with GUI), 3. Installed RFB using the "Gofer" part of the command in my previous mail, 4. Started the RFB server by running the RFB server part of the script, 5. Did "save and quit", 6. Uploaded the new image to my server, 7. Ran in it headless mode. Now it works! ... but I'm still at a loss to explain why this worked but the following steps done entirely on the server via scripts didn't - 1. Save and quit after just installing RFB (the "Gofer" part). 2. Save and quit after starting the RFB server. 3. Run the resultant image in -headless mode. It looks like I had to get the image to be modified by Pharo2.0.app in order for this to work. Hope this helps someone else struggling with the same thing. Best, -Kumar On 25 Oct, 2013, at 8:54 AM, Srikumar Karaikudi Subramanian <srikumarks(a)gmail.com> wrote: > Hi, > > Since this is my first post, I'd first like to say Pharo rocks! > After quite a bit of search for a server-side programming environment > that I can live with, I landed on Pharo/Zinc+family and went > "this is it!" for my project which is like a wiki for music > notation. > > I'm trying to setup a pharo+zinc server with RFB installed on a VPS > so I can access it through VNC ("Chicken of the VNC" on MacOS 10.8.5). > I'm only get a static image of the pharo environment when I connect > and I don't get any interactivity at all. One other poster [1] who > mentioned this also posted that the problem was solved with a > later version of squeak, which I didn't have any luck with since I don't > have X configured on my server. > > Much appreciate any tips. > > I got pharo from get.pharo.org and cloned the image using "save". > I run the following script on the cloned image with > the "-headless" flag (I tried with and without the flag.) > > "----begin code---" > Gofer it > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfRFB'; > load. > (Smalltalk at: #ConfigurationOfRFB) load. > > (RFBServer current) > allowEmptyPasswords: false; > allowRemoteConnections: false; > allowInteractiveConnections: true; > allowZRLE: true; > setFullPassword: 'my password'; > start: 0. > > [1 hour asDelay wait] repeat. > "----end code----" > > One other point - if I save an image after loading the RFB package > (using "Smalltalk snapshot: true andQuit: true.") and then > launch with a script that only starts the server, I get a static black screen > instead and not even the static image. So I don't understand why > there should be a behaviour difference between the two as well. > > Regards to all, > -Kumar > > [1] http://groups.yahoo.com/neo/groups/squeak/conversations/topics/141662

Oct. 25, 2013

Pharo 2.0 with RFBServer with -headless

by Srikumar Karaikudi Subramanian

Hi, Since this is my first post, I'd first like to say Pharo rocks! After quite a bit of search for a server-side programming environment that I can live with, I landed on Pharo/Zinc+family and went "this is it!" for my project which is like a wiki for music notation. I'm trying to setup a pharo+zinc server with RFB installed on a VPS so I can access it through VNC ("Chicken of the VNC" on MacOS 10.8.5). I'm only get a static image of the pharo environment when I connect and I don't get any interactivity at all. One other poster [1] who mentioned this also posted that the problem was solved with a later version of squeak, which I didn't have any luck with since I don't have X configured on my server. Much appreciate any tips. I got pharo from get.pharo.org and cloned the image using "save". I run the following script on the cloned image with the "-headless" flag (I tried with and without the flag.) "----begin code---" Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfRFB'; load. (Smalltalk at: #ConfigurationOfRFB) load. (RFBServer current) allowEmptyPasswords: false; allowRemoteConnections: false; allowInteractiveConnections: true; allowZRLE: true; setFullPassword: 'my password'; start: 0. [1 hour asDelay wait] repeat. "----end code----" One other point - if I save an image after loading the RFB package (using "Smalltalk snapshot: true andQuit: true.") and then launch with a script that only starts the server, I get a static black screen instead and not even the static image. So I don't understand why there should be a behaviour difference between the two as well. Regards to all, -Kumar [1] http://groups.yahoo.com/neo/groups/squeak/conversations/topics/141662

Oct. 25, 2013

Re: [Pharo-users] Reset Spec #openWorldWithSpec:

by Benjamin

euuuuh Basically what is done when you open a spec as world is that the background color changed, all the morph are closed, and the spec is specified to take all the space. So to revert it, I think you *only* need to close the spec morph, set the background color to white, and voilÃ Ben On 24 Oct 2013, at 18:51, btc(a)openinworld.com wrote: > > Message #openWorldWithSpec: sets a Spec entity to take up the whole World. How can that be reverted? ...to set the World back to the state delivered with a virgin Pharo image? > > cheers -ben >

Oct. 24, 2013

Re: [Pharo-users] Three copies of JSON-ul.35 on Smalltalkhub

by Paul DeBruicker

pdebruic Thanks Damien! On Oct 24, 2013, at 9:30 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Thu, Oct 24, 2013 at 6:26 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >> Will you please add me to the PharoExtras/JSON repo? > > > what is your login please? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Oct. 24, 2013

Reset Spec #openWorldWithSpec:

by btc＠openinworld.com

Message #openWorldWithSpec: sets a Spec entity to take up the whole World. How can that be reverted? ...to set the World back to the state delivered with a virgin Pharo image? cheers -ben

Oct. 24, 2013

Re: [Pharo-users] Three copies of JSON-ul.35 on Smalltalkhub

by Damien Cassou

On Thu, Oct 24, 2013 at 6:26 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Will you please add me to the PharoExtras/JSON repo? what is your login please? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 24, 2013

Re: [Pharo-users] Three copies of JSON-ul.35 on Smalltalkhub

by Paul DeBruicker

Hi Stef, Will you please add me to the PharoExtras/JSON repo? Thanks Paul On Oct 23, 2013, at 2:09 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Oct 23, 2013, at 10:25 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > >> There are (at least) three locations of the JSON-ul.35 package on Smalltalkhub. >> >> Here: >> http://smalltalkhub.com/#!/~NicolasPetton/JSON/ >> >> here: >> http://smalltalkhub.com/#!/~PharoExtras/JSON/ >> >> and here: >> http://smalltalkhub.com/#!/~pdebruic/JSONg >> >> >> >> I've also unknowingly duplicated Stef's efforts at making a ConfigurationOfJSON again here: >> >> http://smalltalkhub.com/#!/~pdebruic/JSONg (but this version includes the JSON port to Gemstone) >> >> >> Which of the above should we treat as the canonical JSON repository? > > If you want to have access to the PharoExtras just ask. > I like the idea that a team can maintain a set of used libraries. >> >> >> Thanks >> >> >> Paul > >

Oct. 24, 2013

Has anyone tried?

by Friedrich Dominicus

To use PetitParser for XSD Parsing and generation of Smalltalk code based on this Parsing? Regards Friedrich

Oct. 24, 2013

Re: [Pharo-users] Tip: Recovering a broken image

by Bernat Romagosa

Yes, but you'll have the opportunity to fix whatever broke it before saving and opening the image again. 2013/10/24 Sven Van Caekenberghe <sven(a)stfx.eu> > Yes, I understand - I read that, but the next time you start your new > recover.image they will run again, no ? Resulting in the same problem as > the original image, or not ? > > On 24 Oct 2013, at 14:34, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> > wrote: > > > Because: > > > > âUnlike #saveAs: do not transfer the default execution to the new image." > > > > So the startup and shutdown scripts won't be executed :) > > > > (Or that's what I understood) > > On Oct 24, 2013 1:54 PM, "Sven Van Caekenberghe" <sven(a)stfx.eu> wrote: > > Hi Bernat, > > > > Interesting, I never heard of #backupTo: > > > > But if recover.image is a copy of MyImage.image, and that last one > failed to start up, why then would the copy not have the same problem ? > > > > Sven > > > > On 24 Oct 2013, at 13:32, Bernat Romagosa < > tibabenfortlapalanca(a)gmail.com> wrote: > > > > > Hi list, > > > > > > I've just recovered a broken image that crashed upon startup. There > was some problem with a SerialPort that stayed open and tried to write/read > into a physical port that didn't exist no more, or something of the sort. > > > > > > So here's the magic line: > > > > > > $ bin/myVm shared/MyImage.image eval "SmalltalkImage backupTo: > 'recover'" > > > > > > This makes a copy of the image into a new image called > "recover.image", but as the documentation states: > > > > > > Unlike #saveAs: do not transfer the default execution to the new image. > > > > > > So there you go! > > > > > > Hope it helps someone else. :) > > > > > > -- > > > Bernat Romagosa. > > > > > > > -- Bernat Romagosa.

Oct. 24, 2013

Re: [Pharo-users] Tip: Recovering a broken image

by Sven Van Caekenberghe

Yes, I understand - I read that, but the next time you start your new recover.image they will run again, no ? Resulting in the same problem as the original image, or not ? On 24 Oct 2013, at 14:34, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: > Because: > > âUnlike #saveAs: do not transfer the default execution to the new image." > > So the startup and shutdown scripts won't be executed :) > > (Or that's what I understood) > On Oct 24, 2013 1:54 PM, "Sven Van Caekenberghe" <sven(a)stfx.eu> wrote: > Hi Bernat, > > Interesting, I never heard of #backupTo: > > But if recover.image is a copy of MyImage.image, and that last one failed to start up, why then would the copy not have the same problem ? > > Sven > > On 24 Oct 2013, at 13:32, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: > > > Hi list, > > > > I've just recovered a broken image that crashed upon startup. There was some problem with a SerialPort that stayed open and tried to write/read into a physical port that didn't exist no more, or something of the sort. > > > > So here's the magic line: > > > > $ bin/myVm shared/MyImage.image eval "SmalltalkImage backupTo: 'recover'" > > > > This makes a copy of the image into a new image called "recover.image", but as the documentation states: > > > > Unlike #saveAs: do not transfer the default execution to the new image. > > > > So there you go! > > > > Hope it helps someone else. :) > > > > -- > > Bernat Romagosa. > >

Oct. 24, 2013

Re: [Pharo-users] Spec Question

by Benjamin

Ok :) Thank you, and see you tomorrow :P Ben On 24 Oct 2013, at 14:34, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> wrote: > Yes, I can do that but it'll have to wait until tomorrow. > Will report back, soon. > > Thanks for the help so far, > Manfred > > > > > On Thu, Oct 24, 2013 at 2:29 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Can you try in 3.0, since Spec changed *a lot* in the meantime > > Ben > > On 24 Oct 2013, at 14:25, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> wrote: > >> Hello Ben and ClÃ©ment, >> >> thanks for the quick reply. >> But even when I hit Cmd+s the Text of the label stays the same and the button is not enabled. >> No matter if I use 'whenTextChanged:' or 'whenTextIsAccepted:'. >> >> I only tested this in the Pharo 2.0 image. >> >> Best, >> Manfred >> >> >> >> >> >> >> On Thu, Oct 24, 2013 at 2:22 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> Hey, >> >> Accepting a text usually means the is compiled. To accept a text, right click on it, then click accept in the contextual menu (at the bottom). You can also do it with Cmd+s on Mac. >> >> Try again and tell us if the #whenTextIsAccepted: works fine in your image or not. >> >> Best, >> >> >> >> 2013/10/24 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> >> Text is accepted when you âsaveâ it (cmd+s) >> >> Ben >> >> On 24 Oct 2013, at 14:05, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> wrote: >> >>> Hi everyone, >>> >>> I finally got around to check back on a Spec question that popped up about two weeks ago. >>> >>> At that time I was giving Spec a first try and gathered information from a couple of sources. >>> One of them was the draft chapter about Spec from the Pharo for the Enterprise book. >>> >>> https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Spec/Sp… >>> >>> The example has the following method: >>> >>> TestSpec>>initializePresenter >>> example whenTextIsAccepted: [ changes text: 'The text Changed'. acceptChanges enable ]. >>> >>> This should change the text of the 'changes' LabelModel when the text in the 'example' TextModel is accepted. >>> >>> >>> >>> >>> >>> Now, there the issue for me was that the Label text did not change once when I typed text into the presented textfield. >>> Even when I changed the method from 'whenTextIsAccepted:' to 'whenTextChanged:'. >>> Is this intended or is this an issue with Spec? >>> >>> Also, it is not clear to me what 'accepting' text means (maybe I didn't look thoroughly enough). >>> The method comment just states that it is called when the text is accepted. >>> Which is kind of self referential ;-) >>> >>> The OS X Pharo versions I used for testing where newly downloaded Pharo 2.0 and 3.0 from about 2 weeks ago. >>> They were downloaded from here: >>> http://files.pharo.org/platform/Pharo2.0-mac.zip >>> http://files.pharo.org/platform/Pharo3.0-mac.zip >>> >>> Best, >>> Manfred >> >> >> > >

Oct. 24, 2013

Re: [Pharo-users] Tip: Recovering a broken image

by Bernat Romagosa

Because: âUnlike #saveAs: do not transfer the default execution to the new image." So the startup and shutdown scripts won't be executed :) (Or that's what I understood) On Oct 24, 2013 1:54 PM, "Sven Van Caekenberghe" <sven(a)stfx.eu> wrote: > Hi Bernat, > > Interesting, I never heard of #backupTo: > > But if recover.image is a copy of MyImage.image, and that last one failed > to start up, why then would the copy not have the same problem ? > > Sven > > On 24 Oct 2013, at 13:32, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> > wrote: > > > Hi list, > > > > I've just recovered a broken image that crashed upon startup. There was > some problem with a SerialPort that stayed open and tried to write/read > into a physical port that didn't exist no more, or something of the sort. > > > > So here's the magic line: > > > > $ bin/myVm shared/MyImage.image eval "SmalltalkImage backupTo: 'recover'" > > > > This makes a copy of the image into a new image called "recover.image", > but as the documentation states: > > > > Unlike #saveAs: do not transfer the default execution to the new image. > > > > So there you go! > > > > Hope it helps someone else. :) > > > > -- > > Bernat Romagosa. > > >

Oct. 24, 2013

Re: [Pharo-users] Spec Question

by Manfred KrÃ¶hnert

Yes, I can do that but it'll have to wait until tomorrow. Will report back, soon. Thanks for the help so far, Manfred On Thu, Oct 24, 2013 at 2:29 PM, Benjamin < benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Can you try in 3.0, since Spec changed *a lot* in the meantime > > Ben > > On 24 Oct 2013, at 14:25, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> > wrote: > > Hello Ben and ClÃ©ment, > > thanks for the quick reply. > But even when I hit Cmd+s the Text of the label stays the same and the > button is not enabled. > No matter if I use 'whenTextChanged:' or 'whenTextIsAccepted:'. > > I only tested this in the Pharo 2.0 image. > > Best, > Manfred > > > > > > > On Thu, Oct 24, 2013 at 2:22 PM, ClÃ©ment Bera <bera.clement(a)gmail.com>wrote: > >> Hey, >> >> Accepting a text usually means the is compiled. To accept a text, right >> click on it, then click accept in the contextual menu (at the bottom). You >> can also do it with Cmd+s on Mac. >> >> Try again and tell us if the #whenTextIsAccepted: works fine in your >> image or not. >> >> Best, >> >> >> >> 2013/10/24 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> >> >>> Text is accepted when you âsaveâ it (cmd+s) >>> >>> Ben >>> >>> On 24 Oct 2013, at 14:05, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> >>> wrote: >>> >>> Hi everyone, >>> >>> I finally got around to check back on a Spec question that popped up >>> about two weeks ago. >>> >>> At that time I was giving Spec a first try and gathered information from >>> a couple of sources. >>> One of them was the draft chapter about Spec from the Pharo for the >>> Enterprise book. >>> >>> >>> https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Spec/Sp… >>> >>> The example has the following method: >>> >>> TestSpec>>initializePresenter >>> example whenTextIsAccepted: [ changes text: 'The text Changed'. acceptChanges enable ]. >>> >>> >>> This should change the text of the 'changes' LabelModel when the text in the 'example' TextModel is accepted. >>> >>> >>> >>> Now, there the issue for me was that the Label text did not change once >>> when I typed text into the presented textfield. >>> Even when I changed the method from 'whenTextIsAccepted:' to >>> 'whenTextChanged:'. >>> Is this intended or is this an issue with Spec? >>> >>> Also, it is not clear to me what 'accepting' text means (maybe I didn't >>> look thoroughly enough). >>> The method comment just states that it is called when the text is >>> accepted. >>> Which is kind of self referential ;-) >>> >>> The OS X Pharo versions I used for testing where newly downloaded Pharo >>> 2.0 and 3.0 from about 2 weeks ago. >>> They were downloaded from here: >>> http://files.pharo.org/platform/Pharo2.0-mac.zip >>> http://files.pharo.org/platform/Pharo3.0-mac.zip >>> >>> Best, >>> Manfred >>> >>> >>> >> > >

Oct. 24, 2013

Re: [Pharo-users] Spec Question

by Benjamin

Can you try in 3.0, since Spec changed *a lot* in the meantime Ben On 24 Oct 2013, at 14:25, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> wrote: > Hello Ben and ClÃ©ment, > > thanks for the quick reply. > But even when I hit Cmd+s the Text of the label stays the same and the button is not enabled. > No matter if I use 'whenTextChanged:' or 'whenTextIsAccepted:'. > > I only tested this in the Pharo 2.0 image. > > Best, > Manfred > > > > > > > On Thu, Oct 24, 2013 at 2:22 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Hey, > > Accepting a text usually means the is compiled. To accept a text, right click on it, then click accept in the contextual menu (at the bottom). You can also do it with Cmd+s on Mac. > > Try again and tell us if the #whenTextIsAccepted: works fine in your image or not. > > Best, > > > > 2013/10/24 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > Text is accepted when you âsaveâ it (cmd+s) > > Ben > > On 24 Oct 2013, at 14:05, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> wrote: > >> Hi everyone, >> >> I finally got around to check back on a Spec question that popped up about two weeks ago. >> >> At that time I was giving Spec a first try and gathered information from a couple of sources. >> One of them was the draft chapter about Spec from the Pharo for the Enterprise book. >> >> https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Spec/Sp… >> >> The example has the following method: >> >> TestSpec>>initializePresenter >> example whenTextIsAccepted: [ changes text: 'The text Changed'. acceptChanges enable ]. >> >> This should change the text of the 'changes' LabelModel when the text in the 'example' TextModel is accepted. >> >> >> >> >> Now, there the issue for me was that the Label text did not change once when I typed text into the presented textfield. >> Even when I changed the method from 'whenTextIsAccepted:' to 'whenTextChanged:'. >> Is this intended or is this an issue with Spec? >> >> Also, it is not clear to me what 'accepting' text means (maybe I didn't look thoroughly enough). >> The method comment just states that it is called when the text is accepted. >> Which is kind of self referential ;-) >> >> The OS X Pharo versions I used for testing where newly downloaded Pharo 2.0 and 3.0 from about 2 weeks ago. >> They were downloaded from here: >> http://files.pharo.org/platform/Pharo2.0-mac.zip >> http://files.pharo.org/platform/Pharo3.0-mac.zip >> >> Best, >> Manfred > > >

Oct. 24, 2013

Re: [Pharo-users] Spec Question

by Manfred KrÃ¶hnert

Hello Ben and ClÃ©ment, thanks for the quick reply. But even when I hit Cmd+s the Text of the label stays the same and the button is not enabled. No matter if I use 'whenTextChanged:' or 'whenTextIsAccepted:'. I only tested this in the Pharo 2.0 image. Best, Manfred On Thu, Oct 24, 2013 at 2:22 PM, ClÃ©ment Bera <bera.clement(a)gmail.com>wrote: > Hey, > > Accepting a text usually means the is compiled. To accept a text, right > click on it, then click accept in the contextual menu (at the bottom). You > can also do it with Cmd+s on Mac. > > Try again and tell us if the #whenTextIsAccepted: works fine in your > image or not. > > Best, > > > > 2013/10/24 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > >> Text is accepted when you âsaveâ it (cmd+s) >> >> Ben >> >> On 24 Oct 2013, at 14:05, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> >> wrote: >> >> Hi everyone, >> >> I finally got around to check back on a Spec question that popped up >> about two weeks ago. >> >> At that time I was giving Spec a first try and gathered information from >> a couple of sources. >> One of them was the draft chapter about Spec from the Pharo for the >> Enterprise book. >> >> >> https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Spec/Sp… >> >> The example has the following method: >> >> TestSpec>>initializePresenter >> example whenTextIsAccepted: [ changes text: 'The text Changed'. acceptChanges enable ]. >> >> >> This should change the text of the 'changes' LabelModel when the text in the 'example' TextModel is accepted. >> >> >> Now, there the issue for me was that the Label text did not change once >> when I typed text into the presented textfield. >> Even when I changed the method from 'whenTextIsAccepted:' to >> 'whenTextChanged:'. >> Is this intended or is this an issue with Spec? >> >> Also, it is not clear to me what 'accepting' text means (maybe I didn't >> look thoroughly enough). >> The method comment just states that it is called when the text is >> accepted. >> Which is kind of self referential ;-) >> >> The OS X Pharo versions I used for testing where newly downloaded Pharo >> 2.0 and 3.0 from about 2 weeks ago. >> They were downloaded from here: >> http://files.pharo.org/platform/Pharo2.0-mac.zip >> http://files.pharo.org/platform/Pharo3.0-mac.zip >> >> Best, >> Manfred >> >> >> >

Oct. 24, 2013

Re: [Pharo-users] Spec Question

by ClÃ©ment Bera

Hey, Accepting a text usually means the is compiled. To accept a text, right click on it, then click accept in the contextual menu (at the bottom). You can also do it with Cmd+s on Mac. Try again and tell us if the #whenTextIsAccepted: works fine in your image or not. Best, 2013/10/24 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > Text is accepted when you âsaveâ it (cmd+s) > > Ben > > On 24 Oct 2013, at 14:05, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> > wrote: > > Hi everyone, > > I finally got around to check back on a Spec question that popped up about > two weeks ago. > > At that time I was giving Spec a first try and gathered information from a > couple of sources. > One of them was the draft chapter about Spec from the Pharo for the > Enterprise book. > > > https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Spec/Sp… > > The example has the following method: > > TestSpec>>initializePresenter > example whenTextIsAccepted: [ changes text: 'The text Changed'. acceptChanges enable ]. > > > This should change the text of the 'changes' LabelModel when the text in the 'example' TextModel is accepted. > > Now, there the issue for me was that the Label text did not change once > when I typed text into the presented textfield. > Even when I changed the method from 'whenTextIsAccepted:' to > 'whenTextChanged:'. > Is this intended or is this an issue with Spec? > > Also, it is not clear to me what 'accepting' text means (maybe I didn't > look thoroughly enough). > The method comment just states that it is called when the text is accepted. > Which is kind of self referential ;-) > > The OS X Pharo versions I used for testing where newly downloaded Pharo > 2.0 and 3.0 from about 2 weeks ago. > They were downloaded from here: > http://files.pharo.org/platform/Pharo2.0-mac.zip > http://files.pharo.org/platform/Pharo3.0-mac.zip > > Best, > Manfred > > >

Oct. 24, 2013

Re: [Pharo-users] Spec Question

by Benjamin

Text is accepted when you âsaveâ it (cmd+s) Ben On 24 Oct 2013, at 14:05, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> wrote: > Hi everyone, > > I finally got around to check back on a Spec question that popped up about two weeks ago. > > At that time I was giving Spec a first try and gathered information from a couple of sources. > One of them was the draft chapter about Spec from the Pharo for the Enterprise book. > > https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Spec/Sp… > > The example has the following method: > > TestSpec>>initializePresenter > example whenTextIsAccepted: [ changes text: 'The text Changed'. acceptChanges enable ]. > > This should change the text of the 'changes' LabelModel when the text in the 'example' TextModel is accepted. > > Now, there the issue for me was that the Label text did not change once when I typed text into the presented textfield. > Even when I changed the method from 'whenTextIsAccepted:' to 'whenTextChanged:'. > Is this intended or is this an issue with Spec? > > Also, it is not clear to me what 'accepting' text means (maybe I didn't look thoroughly enough). > The method comment just states that it is called when the text is accepted. > Which is kind of self referential ;-) > > The OS X Pharo versions I used for testing where newly downloaded Pharo 2.0 and 3.0 from about 2 weeks ago. > They were downloaded from here: > http://files.pharo.org/platform/Pharo2.0-mac.zip > http://files.pharo.org/platform/Pharo3.0-mac.zip > > Best, > Manfred

Oct. 24, 2013

Spec Question

by Manfred KrÃ¶hnert

Hi everyone, I finally got around to check back on a Spec question that popped up about two weeks ago. At that time I was giving Spec a first try and gathered information from a couple of sources. One of them was the draft chapter about Spec from the Pharo for the Enterprise book. https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Spec/Sp… The example has the following method: TestSpec>>initializePresenter example whenTextIsAccepted: [ changes text: 'The text Changed'. acceptChanges enable ]. This should change the text of the 'changes' LabelModel when the text in the 'example' TextModel is accepted. Now, there the issue for me was that the Label text did not change once when I typed text into the presented textfield. Even when I changed the method from 'whenTextIsAccepted:' to 'whenTextChanged:'. Is this intended or is this an issue with Spec? Also, it is not clear to me what 'accepting' text means (maybe I didn't look thoroughly enough). The method comment just states that it is called when the text is accepted. Which is kind of self referential ;-) The OS X Pharo versions I used for testing where newly downloaded Pharo 2.0 and 3.0 from about 2 weeks ago. They were downloaded from here: http://files.pharo.org/platform/Pharo2.0-mac.zip http://files.pharo.org/platform/Pharo3.0-mac.zip Best, Manfred

Oct. 24, 2013