November 2013 - Pharo-users

Re: [Pharo-users] [FEEDBACK] Install Pharo on MacOSX

by Manfred KrÃ¶hnert

Hi Damien, the new version looks great (see new screenshot). Actually, it seems like I get this toolbar for every read-only directory I open. Maybe this is a setting I turned on long time ago and forgot by now that it exists. Thanks a lot, Manfred [image: Inline image 1] On Thu, Nov 7, 2013 at 3:24 PM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > > On Tue, Nov 5, 2013 at 6:50 PM, Manfred KrÃ¶hnert < > mkroehnert42(a)googlemail.com> wrote: > >> Just a minor issue with the DMG itself. >> When I opened it on OS X 10.6.8 the lower text was cut off by the window. >> See attached image. >> > > > Would you please try the new dmg? > > > https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Mac-Package/18/art… > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without losing > enthusiasm." > Winston Churchill >

Nov. 7, 2013

A simple an basic calculator built with Spec

by nacho

Hi, I wanted to share with those you could be interested a project I did to learn a little about Spec in Pharo 3. It's a simple and very basic calculator. There code is all commented and I even include a little tutorial on how I build the UI. There are a number of issues however that I have to figure out being the most important a way to get the text displayed to be right-aligned. Also error handling and other...my point was just to focus on Spec. If you are interested you can get it here: MCHttpRepository location: 'http://ss3.gemstone.com/ss/Specalc' user: '' password: '' and then Calculator new openWithSpec. best regards Nacho ----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://forum.world.st/A-simple-an-basic-calculator-built-with-Spec-tp471992… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 7, 2013

[FEEDBACK] [FIX] Cannot locate the sources file named /Applications/PharoV20.sources.

by Damien Cassou

Dear Mac OS X users, could you load this slice from Pharo30Inbox in a Pharo 3.0 image, save your image, and launch it again. SLICE-Issue-12092-Pharo-cant-find-sources-files-when-embedded-in-an-app-application-DamienCassou.2 Do you still have the error "Cannot locate the sources file named /Applications/PharoV20.sources" ? Thanks -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Nov. 7, 2013

Re: [Pharo-users] Repository of petit parser

by Norbert Hartl

Am 07.11.2013 um 16:25 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > > On Thu, Nov 7, 2013 at 3:39 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > Btw. how is the ConfigurationOfPetitParser supposed to work? I loaded the one from the moose repo. Looking at it I need to use at least 1.6 because earlier versions have still Lukasâ repositories configured. But if I load 1.6 and try to use Versionner it shows me that I have 1.8-snapshot loaded. Is this a problem of versionner because of the use of snapshotocello it canât find version numbers in the version methods? So even if Iâm willing to use the 1.8-snapshot version I canât because I want to load only the core and not the rest of the universe but the groups are missing in 1.8-snapshot while being there in 1.7-snapshot. > > I would be glad if someone could shed some light how this should work and why it needs all the added complexity. > > There is no light other than what you described above. If you want to generate a manual version, you can do that at any time. The current Moose process is to use Snapshotcello and we are unlikely to move away from it in the near future. Diego has a proposal for extending Snapshotcello to preserve the configuration structure, but until that is finished, we live with what we have. Of course, contributions are more than welcome. > > > My advize would be to separate metacello configurations for the different uses of it. I do the same with my own projects because it causes less trouble. A ConfigurationOfPetitParser and a separate ConfigurationOfPetitGui that introduces dependencies to glamour et al. would save some headaches for people that are only interested in PetitParser. > > Thanks for the advice. That is precisely what I meant about people wanting to commit to do things :). There are many ways to make things flexible, but they all come with associated effort. If someone offers to put the effort into it, it would be great. Sure. If we can agree about separating the gui and parser part in different metacello configs Iâm most likely in. But I like to have an agreement first. And if we are at it we could at leat put the parser part into a separate repository. You might leave the gui part in moose for the time being. This way it would be made very easy to integrate petit parser in pharo or â¦. Norbert > > Norbert > > > Am 07.11.2013 um 13:13 schrieb Norbert Hartl <norbert(a)hartl.name>: > >> >> >> Am 07.11.2013 um 12:12 schrieb Tudor Girba <tudor(a)tudorgirba.com>: >> >>> Hi, >>> >>> I think you missed my point. I know I can technically load the code from multiple places :). >>> >> I know you know. I couldn't miss the point because for me there is none :) >>> For Moose, PetitParser is an important component that is being developed by the team. Up to now, we did that, hence it made perfect sense to have it in the Moose team repository and in our responsibility. >>> >> Agreed. I have just a different view. I'm using petit parser since 2 1/2 years and to me it never made any sense moving it into moose :) >>> Moving is no problem, as long as we ensure that others actually do something, and that the development does not go in strange directions (which I agree it is unlikely). As I said, it would be great to see PetitParser in the Pharo image and be used by Opal. >> >> Ok, no need to argue. Nothing is carved in stone. I just like to say that I would prefer petit parser breaking loose from moose. >> >> Norbert >>> >>> >>> >>> On Thu, Nov 7, 2013 at 11:58 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> Am 07.11.2013 um 11:46 schrieb Tudor Girba <tudor(a)tudorgirba.com>: >>> >>>> Hi, >>>> >>>> It is in the Moose repository because Moose was essentially the first larger user (besides Helvetia) since its inception (more than 3 years now), and because the development of PetitParser was taken care of by the Moose team. >>>> >>> Being a user of a software is not a good reason to tie it to it. Ask Stef ;) It is nice if the moose team took (and takes) care for it. But you can take care in another repository as well. I think petit parser is an important and standalone package that has nothing to do with moose. Putting this inside another project just weakens the included project. >>> >>>> If others want to contribute (and even integrate into Pharo), it would be great and then we should move it. But, moving should come with commitment. This is an important piece in Moose and we need it to stay working and compatible with Moose requirements. >>>> >>> That is what metacello is for. Refer to the versions you need and you are off the races. As you are one of those who maintains it you are even in the position to _not_ integrate every other change. So if the write restriction to petit parser (being in the moose repo) is the solution we should talk. >>> >>> Norbert >>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> >>>> >>>> On Thu, Nov 7, 2013 at 11:19 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> >>>> Am 07.11.2013 um 11:07 schrieb Stephan Eggermont <stephan(a)stack.nl>: >>>> >>>> > The official repository of PetitParser is >>>> > Moose/PetitParser >>>> > on smalltalkhub >>>> > >>>> thanks. >>>> >>>> > http://forum.world.st/moving-petitparser-to-smalltalkhub-td4671840.html >>>> > >>>> Well, this is not a good place IMHO. A more independent but official repo would be nice. >>>> >>>> Norbert >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Every thing has its own flow" >>> >>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Nov. 7, 2013

Re: [Pharo-users] Repository of petit parser

by Tudor Girba

Hi, On Thu, Nov 7, 2013 at 3:39 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > Btw. how is the ConfigurationOfPetitParser supposed to work? I loaded the > one from the moose repo. Looking at it I need to use at least 1.6 because > earlier versions have still Lukasâ repositories configured. But if I load > 1.6 and try to use Versionner it shows me that I have 1.8-snapshot loaded. > Is this a problem of versionner because of the use of snapshotocello it > canât find version numbers in the version methods? So even if Iâm willing > to use the 1.8-snapshot version I canât because I want to load only the > core and not the rest of the universe but the groups are missing in > 1.8-snapshot while being there in 1.7-snapshot. > > I would be glad if someone could shed some light how this should work and > why it needs all the added complexity. > There is no light other than what you described above. If you want to generate a manual version, you can do that at any time. The current Moose process is to use Snapshotcello and we are unlikely to move away from it in the near future. Diego has a proposal for extending Snapshotcello to preserve the configuration structure, but until that is finished, we live with what we have. Of course, contributions are more than welcome. > My advize would be to separate metacello configurations for the different > uses of it. I do the same with my own projects because it causes less > trouble. A ConfigurationOfPetitParser and a separate > ConfigurationOfPetitGui that introduces dependencies to glamour et al. > would save some headaches for people that are only interested in > PetitParser. > Thanks for the advice. That is precisely what I meant about people wanting to commit to do things :). There are many ways to make things flexible, but they all come with associated effort. If someone offers to put the effort into it, it would be great. Cheers, Doru > Norbert > > > Am 07.11.2013 um 13:13 schrieb Norbert Hartl <norbert(a)hartl.name>: > > > > Am 07.11.2013 um 12:12 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > Hi, > > I think you missed my point. I know I can technically load the code from > multiple places :). > > I know you know. I couldn't miss the point because for me there is none :) > > For Moose, PetitParser is an important component that is being developed > by the team. Up to now, we did that, hence it made perfect sense to have it > in the Moose team repository and in our responsibility. > > Agreed. I have just a different view. I'm using petit parser since 2 1/2 > years and to me it never made any sense moving it into moose :) > > Moving is no problem, as long as we ensure that others actually do > something, and that the development does not go in strange directions > (which I agree it is unlikely). As I said, it would be great to see > PetitParser in the Pharo image and be used by Opal. > > > Ok, no need to argue. Nothing is carved in stone. I just like to say that > I would prefer petit parser breaking loose from moose. > > Norbert > > > > > On Thu, Nov 7, 2013 at 11:58 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> Am 07.11.2013 um 11:46 schrieb Tudor Girba <tudor(a)tudorgirba.com>: >> >> Hi, >> >> It is in the Moose repository because Moose was essentially the first >> larger user (besides Helvetia) since its inception (more than 3 years now), >> and because the development of PetitParser was taken care of by the Moose >> team. >> >> Being a user of a software is not a good reason to tie it to it. Ask Stef >> ;) It is nice if the moose team took (and takes) care for it. But you can >> take care in another repository as well. I think petit parser is an >> important and standalone package that has nothing to do with moose. Putting >> this inside another project just weakens the included project. >> >> If others want to contribute (and even integrate into Pharo), it would be >> great and then we should move it. But, moving should come with commitment. >> This is an important piece in Moose and we need it to stay working and >> compatible with Moose requirements. >> >> That is what metacello is for. Refer to the versions you need and you are >> off the races. As you are one of those who maintains it you are even in the >> position to _not_ integrate every other change. So if the write restriction >> to petit parser (being in the moose repo) is the solution we should talk. >> >> Norbert >> >> Cheers, >> Doru >> >> >> >> >> On Thu, Nov 7, 2013 at 11:19 AM, Norbert Hartl <norbert(a)hartl.name>wrote: >> >>> >>> Am 07.11.2013 um 11:07 schrieb Stephan Eggermont <stephan(a)stack.nl>: >>> >>> > The official repository of PetitParser is >>> > Moose/PetitParser >>> > on smalltalkhub >>> > >>> thanks. >>> >>> > >>> http://forum.world.st/moving-petitparser-to-smalltalkhub-td4671840.html >>> > >>> Well, this is not a good place IMHO. A more independent but official >>> repo would be nice. >>> >>> Norbert >>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 7, 2013

Re: [Pharo-users] Spec - Tutorial Series

by Benjamin

Really nice tutorial :) If I were you, I would based it on Pharo 3.0 more than 2.0. Why ? Because your tutorial will be outdated quite soon (in a couple on months) when 3.0 will be released. Our you could try to use the latest Spec version at least since the one shipped in 2.0 is old and out-dated :P But itâs always cool to see people writing things about my work :) Once again, really nice tuto, and I like the way you write, keep going :) Ben On 07 Nov 2013, at 16:01, btc(a)openinworld.com wrote: > Bahman Movaqar wrote: >> Hi all, >> >> I'm writing a series of tutorials for Spec for beginners like myself and >> I'd really appreciate any input on the material. >> The first episode is done: http://www.bahmanm.com/blogs/spec-part-1-basics >> >> > Thanks Bahman. I like your writing style and theme. The code snippets are well presented. What platform is your blog hosted on? > > Some feedback... > > ----------- > > Not sure if you should be prompting people to dirty the Spec package by using example category Spec-Tutorial. Even though there is currently no such a package, one day there might be. Perhaps using category My-Spec-Tutorial would be better alternative. > > ---------------- > > > further radio buttons setup is done in setupTitleRadioButtons: > looks like it should lose the colon at the end of the method name > > ------------- > An alternative to the nested IF statements in MyFirstWindow>>userTitle... > > If you extend RadioButtonGroup with... > RadioButtonGroup>>selected > ^buttons detect: [:b | b state ]. > > and add instance variable 'radioButtonGroup' to MyFirstWindow > > and in MyFirstWindow>>setupTitleRadioButtons do.... > radioButtonGroup := RadioButtonGroup new > > then you could have... > MyFirstWindow>>userTitle > ^ radioButtonGroup selected label > > Then again, for someone completely new to Smalltalk, the nested IF statements might be more familiar. So perhaps leave that part as it is, then describe how to refactor the code to be more 'Pharo' like. You might say... "at the time I did this, the RadioButtonGroup class was missing a method to return the selected button, but it was simple to extend the library with the following...." > > Note that I tested this on Pharo3, but I expect Pharo 2 would be the same for this case. > > cheers -ben > > >

Nov. 7, 2013

Re: [Pharo-users] Why won't my Pharo download run?

by PBK Research

OK. I opened a command line prompt, cd to Pharo 2.0 directory (created in today's download), enter 'pharo.exe pharo2.0.image'. Same result - immediate failure. I had previously changed the association of the image file to the newly downloaded pharo.exe. So I think I must be using the VM in today's download. _____ From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Igor Stasenko Sent: 07 November 2013 14:48 To: Any question about pharo is welcome Subject: Re: [Pharo-users] Why won't my Pharo download run? On 7 November 2013 15:31, PBK Research <peter(a)pbkresearch.co.uk> wrote: Thanks. I am using the latest one-click distribution of Pharo, downloaded today from the Pharo website. Presumably that should have the latest VM? yes, but if .image file extension associated with wrong version of VM binary, which you installed previously (as you mentioned), it won't automagically use proper one. unless you run vm from command line e.g.: pharo.exe myimage.image or change the association to use different vm. _____ From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Igor Stasenko Sent: 07 November 2013 13:53 To: Any question about pharo is welcome Subject: Re: [Pharo-users] Why won't my Pharo download run? On 7 November 2013 14:18, PBK Research <peter(a)pbkresearch.co.uk> wrote: Hello! I have a problem with running Pharo 2.0 on one of my machines. I have two machines, both running Windows XP with SP3. On one of them I have a successful load of Pharo (actually it's a distribution of the Moose system, but that is just an application built on Pharo 2.0). This loads successfully when I double click on pharo.exe. On the other machine, the same action produces an immediate message: 'Pharo.exe has encountered a problem and needs to close'. Just in case this was some problem with Moose, I have just downloaded the latest one-click installation of Pharo 2.0 for Windows. This displays exactly the same behaviour - an immediate fail when I try to start it. I have tried to work out what may be different between the two machines. The one which will run Pharo has an Intel Celeron processor, the other an AMD Athlon XP (yes, they are both pretty ancient!), but I can't see why that should make any difference. The one curious thing is that Windows Explorer displays the type of the Pharo2.0.image file as 'Squeak image file'. There is an old version of Squeak installed on that machine; could that have any effect? I am a bit flummoxed by all this. Does anyone have any suggestions about how to diagnose the problem? If you using too old VM , it simply does not supports an image format, which pharo 2.0 uses. But there could be different reasons.. a first step towards to solution is to use VM for pharo, which we maintain and use.. Many thanks Peter Kenny -- Best regards, Igor Stasenko. -- Best regards, Igor Stasenko.

Nov. 7, 2013

Re: [Pharo-users] Spec - Tutorial Series

by btc＠openinworld.com

Bahman Movaqar wrote: > Hi all, > > I'm writing a series of tutorials for Spec for beginners like myself and > I'd really appreciate any input on the material. > The first episode is done: http://www.bahmanm.com/blogs/spec-part-1-basics > > Thanks Bahman. I like your writing style and theme. The code snippets are well presented. What platform is your blog hosted on? Some feedback... ----------- Not sure if you should be prompting people to dirty the Spec package by using example category Spec-Tutorial. Even though there is currently no such a package, one day there might be. Perhaps using category My-Spec-Tutorial would be better alternative. ---------------- > further radio buttons setup is done in setupTitleRadioButtons: looks like it should lose the colon at the end of the method name ------------- An alternative to the nested IF statements in MyFirstWindow>>userTitle... If you extend RadioButtonGroup with... RadioButtonGroup>>selected ^buttons detect: [:b | b state ]. and add instance variable 'radioButtonGroup' to MyFirstWindow and in MyFirstWindow>>setupTitleRadioButtons do.... radioButtonGroup := RadioButtonGroup new then you could have... MyFirstWindow>>userTitle ^ radioButtonGroup selected label Then again, for someone completely new to Smalltalk, the nested IF statements might be more familiar. So perhaps leave that part as it is, then describe how to refactor the code to be more 'Pharo' like. You might say... "at the time I did this, the RadioButtonGroup class was missing a method to return the selected button, but it was simple to extend the library with the following...." Note that I tested this on Pharo3, but I expect Pharo 2 would be the same for this case. cheers -ben

Nov. 7, 2013

Re: [Pharo-users] Why won't my Pharo download run?

by ClÃ©ment Bera

Hey, Yeah it might be as there's Squeak installed that the image tries to be run with the old squeak VM instead of the pharo VM. Then it fails with old VMs. 2013/11/7 Igor Stasenko <siguctua(a)gmail.com> > > > > On 7 November 2013 14:18, PBK Research <peter(a)pbkresearch.co.uk> wrote: > >> Hello! >> >> I have a problem with running Pharo 2.0 on one of my machines. I have two >> machines, both running Windows XP with SP3. On one of them I have a >> successful load of Pharo (actually it's a distribution of the Moose system, >> but that is just an application built on Pharo 2.0). This loads >> successfully when I double click on pharo.exe. On the other machine, the >> same action produces an immediate message: 'Pharo.exe has encountered a >> problem and needs to close'. Just in case this was some problem with Moose, >> I have just downloaded the latest one-click installation of Pharo 2.0 for >> Windows. This displays exactly the same behaviour - an immediate fail when >> I try to start it. >> >> I have tried to work out what may be different between the two machines. >> The one which will run Pharo has an Intel Celeron processor, the other an >> AMD Athlon XP (yes, they are both pretty ancient!), but I can't see why >> that should make any difference. The one curious thing is that Windows >> Explorer displays the type of the Pharo2.0.image file as 'Squeak image >> file'. There is an old version of Squeak installed on that machine; could >> that have any effect? >> >> I am a bit flummoxed by all this. Does anyone have any suggestions about >> how to diagnose the problem? >> >> > > If you using too old VM , it simply does not supports an image format, > which pharo 2.0 uses. > But there could be different reasons.. a first step towards to solution is > to use VM for pharo, which we maintain and use.. > > > >> Many thanks >> >> Peter Kenny >> > > > > -- > Best regards, > Igor Stasenko. >

Nov. 7, 2013

Re: [Pharo-users] Spec - Nested Layouts

by ClÃ©ment Bera

2013/11/7 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> > Just a general remark: you should try as much as possible to avoid hard > coding width/height :) > > there are some methods on ComposableModel you could use like buttonHeight > toolbarHeight etc. that you should use instead :) > > > Ben > > On 07 Nov 2013, at 13:22, Bahman Movaqar <Bahman(a)BahmanM.com> wrote: > > On 11/07/2013 12:45, ClÃ©ment Bera wrote: > > Hey, > > I don't know what you want exactly. > > You can do: > > spec > <spec> > ^ SpecLayout composed > newRow: [:row | > row > newColumn: [ :col | > col > add: #list width: 135; > add: #description ] ]; > yourself > > and nest that as many times as you want (but I don't know if this was > your question). > > > I just tried this one and it works (see the code below) BUT, the code is > so hard to read and understand just for 3 rows and 7 widgets! > > <code> > defaultSpec > ^ SpecLayout composed > newColumn: [ :mainColumn | > mainColumn > newRow: [ :nameRow | > nameRow > add: #labelName; > add: #textName ] > height: 25. > mainColumn > newRow: [ :titleRow | > titleRow > add: #labelTitle; > newRow: [ :titleRadioRow | > titleRadioRow > add: #radioMr; > add: #radioMrs; > add: #radioMs ] ] > height: 25. > mainColumn newRow: [ :buttonRow | buttonRow add: > #buttonGreet ] height: 25 ]; > yourself > </code> > > Am I doing it right? > > I guess this is right. But I think you need to generate this layout out of collections, not to write it. > > > Another feature is: > > debuggerSpec > <spec: #default> > ^ SpecLayout composed > add: #inspector withSpec: #debuggerSpec; > yourself > > #inspector being the instance variable name that holds a subclass of > ComposableModel that defines class side #debuggerSpec, which answers a > SpecLayout. > > > Does this mean that for every table cell I have to create a new class? > > Yeah well I was just pointing out all the choices you had. Depending on what you want to do you could have a class hierarchy similar to this: SpecTable AbstractSpecColumn SpecColumnA SpecColumnB AbstractSpecCell SpecCellA SpecCellB SpecTable having column, column having cells. But this may not be the best choice. Now that you caught my interest, I tried to do a table. I put it in attachment the result. It is a .st file, so drag and drop it in your image, then click file in entire file. Then try to run 'SpecTable new', it opens a table with 3 columns and 5 rows, with no complex layout method. All the code is in SpecTable (Cmd+f,Cmd+c to find a class in nautilus or write the class name in workspace then select it and press Cmd+m), in the method protocol table logic. It's like 6 methods. However: - vertical splitters are not sync. - I don't know how to color the border of each cell to make it beautiful. Of course you need to polish it ... I hope it helped you :) > Not sure if this helped. > > All of these questions are for your tutorials ? > > > > > 2013/11/7 Bahman Movaqar <Bahman(a)bahmanm.com> > >> Hi all, >> >> Is it possible to nest layouts in Spec? For example can I combine >> `SpecColumnLayout` and `SpecRowLayout` together? >> >> > -- > Bahman Movaqar (http://BahmanM.com <http://bahmanm.com/>) > > ERP Evaluation, Implementation & Deployment Consultant > PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) > -- > Bahman Movaqar (http://BahmanM.com <http://bahmanm.com/>) > > ERP Evaluation, Implementation & Deployment Consultant > PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) > > >

Nov. 7, 2013