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

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

by Benjamin

Such a UI can be achieve with a MorphTreeMorph (therefor with a TreeModel in Spec). Maybe I should create a TableModel in addition since a TreeModel for this is a bit magic :) Ben On 07 Nov 2013, at 10:04, ClÃ©ment Bera <bera.clement(a)gmail.com> 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. > > 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. > > Ben can advise you on how to implement that. > > <Screen Shot 2013-11-07 at 10.00.55 AM.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) > > >

Nov. 7, 2013

Re: [Pharo-users] Spec - TextModel whenTextIsAccepted

by Benjamin

Somehow itâs true. And you could try it :) But while doing Spec I also fixed a lot of bugs in the morphic widgets themselves :) Try with the latest spec, and tell me :P Ben On 07 Nov 2013, at 05:38, Bahman Movaqar <Bahman(a)BahmanM.com> wrote: > On 11/06/2013 20:35, Benjamin wrote: >> Ok :) >> >> These methods only exists in Pharo 3.0 :) > > Hmm...I don't understand. Please correct me if I'm wrong but I thought Spec is a UI library, so it doesn't matter if I'm using it in Pharo 2.0 or 3.0 as long as I have the correct version of Spec. > >> >> >> On 06 Nov 2013, at 08:38, Bahman Movaqar <Bahman(a)BahmanM.com> wrote: >> >>> On 11/06/2013 11:07, Benjamin wrote: >>>> In which version of Pharo are you working ? >>> >>> Pharo2.0 >>> Latest update: #20607 >>> >>>> >>>> On 06 Nov 2013, at 08:31, Bahman Movaqar <Bahman(a)BahmanM.com> wrote: >>>> >>>>> On 11/06/2013 10:56, Benjamin wrote: >>>>>> On 06 Nov 2013, at 08:21, Bahman Movaqar <Bahman(a)BahmanM.com >>>>>> <mailto:Bahman@BahmanM.com>> wrote: >>>>>> >>>>>>> On 11/06/2013 10:41, Benjamin wrote: >>>>>>>> This is the expected behaviour :) >>>>>>> >>>>>>> Oh! A bit unorthodox, specially considering the shortcut (CTRL+S) >>>>>>> --I was expecting something like ENTER :-) >>>>>> >>>>>> There is also acceptOnCr :) >>>>> >>>>> That clearly shows I have to work on my "exploration" skills :-) >>>>> >>>>>> >>>>>>> >>>>>>>> But what you can do (and actually what you wanna do) is to accept >>>>>>>> the text at each keyStroke :) >>>>>>>> >>>>>>>>> initializePresenter >>>>>>>>> self instantiateModels: #( >>>>>>>>> textName TextModel >>>>>>>>> labelGreeting LabelModel >>>>>>>>> buttonGreet ButtonModel >>>>>>>>> ). >>>>>>>>> labelGreeting text: ''. >>>>>>>>> buttonGreet label: 'Greet Me!'; disable. >>>>>>>> >>>>>>>> should be turned into: >>>>>>>> >>>>>>>> #initializePresenter >>>>>>>> textName := self newTextInput. >>>>>>>> labelGreeting := self newLabel. >>>>>>>> buttonGreet := self newButton. >>>>>>> >>>>>>> Would you please explain the RHS of the statements? I don't >>>>>>> understand `self newTextInput`. >>>>>> >>>>>> Itâs equivalent to self instantiateModels: #(textName >>>>>> TextInputFieldModel). >>>>>> It simply creates a new sub model for you :) >>>>> >>>>> Hmm...Pharo rejects those lines, e.g. with "Unknown select >>>>> newTextInput". I guess I'm sub-classing the wrong class. Here's my >>>>> class definition: >>>>> >>>>> <code> >>>>> ComposableModel subclass: #FirstSpec >>>>> instanceVariableNames: 'textName labelGreeting buttonGreet' >>>>> classVariableNames: '' >>>>> poolDictionaries: '' >>>>> category: 'Bahman-Spec' >>>>> </code> >>>>> >>>>>> >>>>>>> >>>>>>>> >>>>>>>> labelGreeting text: ''. >>>>>>>> buttonGreet label: 'Greet Me!'; disable. >>>>>>>> textName autoAccept: true. >>>>>>> >>>>>>> It's certainly no big deal but I'm just curious; any special reason >>>>>>> why `autoAccept` doesn't default to true? >>>>>> >>>>>> Thatâs actually a good question :) >>>>>> I guess the answer is historical :) >>>>> >>>>> Ancestral remains, huh? :-) >>>>> >>>>>> >>>>>>> >>>>>>>> On 06 Nov 2013, at 06:05, Bahman Movaqar <Bahman(a)BahmanM.com >>>>>>>> <mailto:Bahman@BahmanM.com>> wrote: >>>>>>>> >>>>>>>>> Hi all, >>>>>>>>> >>>>>>>>> I'm writing a simple graphical version of the legendary "Hello, >>>>>>>>> world". I have a window with a text field, a button and a label. >>>>>>>>> What I'm trying to do is to make the button (which is initially >>>>>>>>> disabled) enabled upon user entering text. However, it seems that >>>>>>>>> the user first must "Accept" the text for the action to be fired. >>>>>>>>> >>>>>>>>> Here's some snippets of code: >>>>>>>>> >>>>>>>>> <code> >>>>>>>>> initializePresenter >>>>>>>>> textName whenTextChanged: [ >>>>>>>>> buttonGreet enable ]. >>>>>>>>> buttonGreet action: [ >>>>>>>>> labelGreeting text: 'Hello, ', textName text, '!'. >>>>>>>>> buttonGreet disable ]. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> initializeWidgets >>>>>>>>> self instantiateModels: #( >>>>>>>>> textName TextModel >>>>>>>>> labelGreeting LabelModel >>>>>>>>> buttonGreet ButtonModel >>>>>>>>> ). >>>>>>>>> >>>>>>>>> labelGreeting text: ''. >>>>>>>>> buttonGreet label: 'Greet Me!'; disable. >>>>>>>>> </code> >>>>>>>>> >>>>>>>>> What am I doing wrong? >>>>>>>>> >>>>>>>>> TIA, >>>>>>>>> >>>>>>>>> PS: I have tried `whenTextChanged` to no avail --it shows the same >>>>>>>>> behaviour. >>>>>>> > > -- > 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 Tudor Girba

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. 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. 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] Repository of petit parser

by Norbert Hartl

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

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. 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 <mailto:Bahman@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

Re: [Pharo-users] Repository of petit parser

by Stephan Eggermont

The official repository of PetitParser is Moose/PetitParser on smalltalkhub http://forum.world.st/moving-petitparser-to-smalltalkhub-td4671840.html

Nov. 7, 2013

Re: [Pharo-users] Repository of petit parser

by Jan KurÅ¡

Hi, https://ci.inria.fr/moose/job/petitparser/ Or PBE2 says: Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; package: 'ConfigurationOfPetitParser'; load. (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault. Hope it helps, I use the first option. Cheers, Jan On Thu, Nov 7, 2013 at 10:10 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > Looking at smalltalkhub there are plenty of PetitParser repos to find but > none that looks official. So which is considered official? I still had > Lukasâ repo in my config but the server seems to be down so I noticed. > > Norbert >

Nov. 7, 2013

Re: [Pharo-users] Repository of petit parser

by Camillo Bruni

If we open an official one, given the importance of petitparser, it should be under PharoExtras. On 2013-11-07, at 10:10, Norbert Hartl <norbert(a)hartl.name> wrote: > Looking at smalltalkhub there are plenty of PetitParser repos to find but none that looks official. So which is considered official? I still had Lukasâ repo in my config but the server seems to be down so I noticed. > > Norbert

Nov. 7, 2013

Re: [Pharo-users] Spec - Tutorial Series

by kilon alios

well done, this is indeed a very good tutorial and more than welcomed, thank you :) I twitted it :) On Thu, Nov 7, 2013 at 11:30 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On 07 Nov 2013, at 10:08, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > I'm glad you are doing that :). > > Marcus could you tweet about this blog on the Pharo tweeter account > > > Yes, I will do that (i put it in the queue, I do one per day max :-) > > ? So many people are waiting for more tutorials on Spec. > > > 2013/11/7 Bahman Movaqar <Bahman(a)bahmanm.com> > >> 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 >> >> -- >> Bahman Movaqar (http://BahmanM.com <http://bahmanm.com/>) >> >> ERP Evaluation, Implementation & Deployment Consultant >> PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) >> >> >> > >

Nov. 7, 2013

Re: [Pharo-users] Spec - Tutorial Series

by Marcus Denker

On 07 Nov 2013, at 10:08, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > I'm glad you are doing that :). > > Marcus could you tweet about this blog on the Pharo tweeter account Yes, I will do that (i put it in the queue, I do one per day max :-) > ? So many people are waiting for more tutorials on Spec. > > > 2013/11/7 Bahman Movaqar <Bahman(a)bahmanm.com> > 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 > > -- > 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 ClÃ©ment Bera

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

Nov. 7, 2013

Repository of petit parser

by Norbert Hartl

Looking at smalltalkhub there are plenty of PetitParser repos to find but none that looks official. So which is considered official? I still had Lukasâ repo in my config but the server seems to be down so I noticed. Norbert

Nov. 7, 2013

Re: [Pharo-users] Spec - Tutorial Series

by ClÃ©ment Bera

I'm glad you are doing that :). Marcus could you tweet about this blog on the Pharo tweeter account ? So many people are waiting for more tutorials on Spec. 2013/11/7 Bahman Movaqar <Bahman(a)bahmanm.com> > 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 > > -- > 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 ClÃ©ment Bera

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. 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. Ben can advise you on how to implement that. [image: Images intÃ©grÃ©es 1] 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) > > >

Nov. 7, 2013

Re: [Pharo-users] Spec - Text alignment in LabelModel

by ClÃ©ment Bera

Hey, I'm not sure this is the good way to do it, but you can store in your labelModel a Text instead of a String: myComposableModel label text: 'someString' asText. Then you can add attribute to the text: myComposableModel label text addAttribute: TextColor red. myComposableModel label text addAttribute: TextAlignment rightFlush. Try first with TextColor red, because for TextAlignment rightFlush there might be other reason it does not work (i.e. the label model has the width of the text, so modifying the alignment will not modify anything). Best, 2013/11/7 nacho <0800nacho(a)gmail.com> > Hi, > After spending almost two hours digging into Spec I couldn't figure out how > to change the alignment of the text in LabelModel. As I'm building a simple > calculator, the text has to be right-aligned. The default is > left-alginement > which makes the calculator display look weird. > Any help would be much appreciated. > best regards > Nacho > > > > > > ----- > Nacho > Smalltalker apprentice. > Buenos Aires, Argentina. > -- > View this message in context: > http://forum.world.st/Spec-Text-alignment-in-LabelModel-tp4719750.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Nov. 7, 2013