November 2013 - Pharo-users

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

by Damien Cassou

On Tue, Nov 5, 2013 at 12:10 PM, Mark Bestley <news{(a)bestley.co.uk> wrote: > This is due to Gatekeeper I think. I managed to open it by choosing Open > in the right click menu in Finder. see > <http://support.apple.com/kb/ht5290> I think you need to sign the app thank you for the reference. I will have a look. I wanted to put the application on the Mac App Store, but it looks I would have to pay Apple and I don't want to. Hope your solution doesn't require that. > The Launcher looks for and save images in ~/Library/Preferences/Pharo > This is wrong it should be ~/Library/Application/Support/Pharo for > general use, there is a case for using ~/Library/Containers to fit in > with Apple's sandboxing. I wanted to do that already. Thanks for the directory names. Do you have an url where Apple discusses such directories? > Or better allow us to chnage the directory That's on my todo. As always, I need help. This is the kind of change people can do easily (the preference mechanism is already in place). So, if you want to hack on the launcher, this would be a good start. > The icons are odd, trying to get a new Pharo 3 image it says hit refresh > icon which took me some time to find. Although I am bad at all icons so > might just be me. It's not just you. I see 2 solutions: - have a menu item to refresh when right clicking on the "hit refresh button" message. - automatically download the content when expanding the tree. -- 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

Why won't my Pharo download run?

by PBK Research

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? Many thanks Peter Kenny

Nov. 7, 2013

Re: [Pharo-users] Spec - Nested Layouts

by Benjamin

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? > >> >> 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? > >> 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) >> >> ERP Evaluation, Implementation & Deployment Consultant >> PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) >> -- >> Bahman Movaqar (http://BahmanM.com) >> >> ERP Evaluation, Implementation & Deployment Consultant >> PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)

Nov. 7, 2013

Re: [Pharo-users] Spec - Nested Layouts

by Bahman Movaqar

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? > > 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? > Not sure if this helped. > > All of these questions are for your tutorials ? > > > > > 2013/11/7 Bahman Movaqar <Bahman(a)bahmanm.com <mailto:Bahman@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) > > ERP Evaluation, Implementation & Deployment Consultant > PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) > -- > Bahman Movaqar (http://BahmanM.com) > > ERP Evaluation, Implementation & Deployment Consultant > PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)

Nov. 7, 2013

Re: [Pharo-users] Repository of petit parser

by Norbert Hartl

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

Nov. 7, 2013

Re: [Pharo-users] Repository of petit parser

by Tudor Girba

Hi, I think you missed my point. I know I can technically load the code from multiple places :). 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. 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. Cheers, Doru 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"

Nov. 7, 2013

Re: [Pharo-users] Spec - Grid/Table Layout

by Benjamin

On 07 Nov 2013, at 12:04, Bahman Movaqar <Bahman(a)BahmanM.com> wrote: > On 11/07/2013 12:34, ClÃ©ment Bera wrote: >> Hello, >> >> Actually I had the same problem, I think the best widget that exists for that right now is MultiColumnListModel. >> >> For example, in the senders window (in attachment), the top panel is a MultiColumnListModel. You can have as many lines and as many columns as you want. > > Great. Now I have to check if I can put widgets in those "lines" and "columns" instead of just text? > >> >> We do not have yet a tableLayout, but we miss it. If you plan to implement it, we will be interested in integrating it into Pharo. > > No way! At least currently :-) I'm just too inexperienced for such serious stuff Thatâs a good way to learn :P Ben > >> >> Ben can advise you on how to implement that. >> >> <Mail Attachment.png> >> >> >> 2013/11/7 Bahman Movaqar <Bahman(a)bahmanm.com> >> Hi all, >> >> Is there a grid/table layout available in Spec? Something like an HTML >> table or Swing's GridLayout? If not, how may I achieve such a >> functionality? >> >> I'd appreciate any hints/pointers. >> >> -- >> Bahman Movaqar (http://BahmanM.com) >> >> ERP Evaluation, Implementation & Deployment Consultant >> PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) >> >> >> > > > -- > Bahman Movaqar (http://BahmanM.com) > > ERP Evaluation, Implementation & Deployment Consultant > PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)

Nov. 7, 2013

Re: [Pharo-users] Spec - Grid/Table Layout

by Bahman Movaqar

On 11/07/2013 12:34, ClÃ©ment Bera wrote: > Hello, > > Actually I had the same problem, I think the best widget that exists > for that right now is MultiColumnListModel. > > For example, in the senders window (in attachment), the top panel is a > MultiColumnListModel. You can have as many lines and as many columns > as you want. Great. Now I have to check if I can put widgets in those "lines" and "columns" instead of just text? > > We do not have yet a tableLayout, but we miss it. If you plan to > implement it, we will be interested in integrating it into Pharo. No way! At least currently :-) I'm just too inexperienced for such serious stuff > > Ben can advise you on how to implement that. > > Images intÃ©grÃ©es 1 > > > 2013/11/7 Bahman Movaqar <Bahman(a)bahmanm.com <mailto:Bahman@bahmanm.com>> > > Hi all, > > Is there a grid/table layout available in Spec? Something like an > HTML > table or Swing's GridLayout? If not, how may I achieve such a > functionality? > > I'd appreciate any hints/pointers. > > -- > Bahman Movaqar (http://BahmanM.com) > > ERP Evaluation, Implementation & Deployment Consultant > PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com > <http://keyserver2.pgp.com>) > > > -- Bahman Movaqar (http://BahmanM.com) ERP Evaluation, Implementation & Deployment Consultant PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)

Nov. 7, 2013

Re: [Pharo-users] Repository of petit parser

by Norbert Hartl

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"

Nov. 7, 2013

Re: [Pharo-users] Spec - Nested Layouts

by Benjamin

Cool :) I think what Clement answered is what you wanted :) Alos, see the other thread, you can do table by tweaking a TreeModel :) Ben On 07 Nov 2013, at 11:08, 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. > > Right. I had a feeling that I'd asked it the wrong way :-) > > What I'd like to know is that can I mimic a table layout by nesting column and row layouts? > >> >> 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). >> >> 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. >> >> Not sure if this helped. > > Thanks. I'll give this a try and let you know. > >> >> All of these questions are for your tutorials ? > > Yes. Actually I'm trying to build a UI for Fossil DVCS with Pharo. And in the meantime, I document what I learn hoping it will save somebody else's time :-) > >> >> >> 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? >> >> TIA, >> > > -- > Bahman Movaqar (http://BahmanM.com) > > ERP Evaluation, Implementation & Deployment Consultant > PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)

Nov. 7, 2013