- Pharo-users - lists.pharo.org

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