November 2013 - Pharo-users

Re: [Pharo-users] Spec - TextModel whenTextIsAccepted

by Bahman Movaqar

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. 6, 2013

Re: [Pharo-users] Spec - TextModel whenTextIsAccepted

by Benjamin

On 06 Nov 2013, at 08:21, Bahman Movaqar <Bahman(a)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 :) > >> 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 :) > >> >> 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 :) Ben > >> On 06 Nov 2013, at 06:05, Bahman Movaqar <Bahman(a)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. 6, 2013

Re: [Pharo-users] Spec - TextModel whenTextIsAccepted

by Bahman Movaqar

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 :-) > 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`. > > 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? > 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. 6, 2013

Re: [Pharo-users] Spec - TextModel whenTextIsAccepted

by Benjamin

This is the expected behaviour :) 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. labelGreeting text: ''. buttonGreet label: 'Greet Me!'; disable. textName autoAccept: true. Keep me in touch :) Ben On 06 Nov 2013, at 06:05, Bahman Movaqar <Bahman(a)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. 6, 2013

Re: [Pharo-users] Adjusting the size of a window using Spec

by Benjamin

You just need to override the method #initialExtent It should return a point structured like this: width@height :) Ben On 06 Nov 2013, at 01:50, nacho <0800nacho(a)gmail.com> wrote: > Continuing with my testing to learn Spec, I'm trying to build a really basic > calculator. > So far I managed to build the basic UI. However, I'm having some trouble at > getting it displayed at the correct size. I don't know how to change the > window that is opened when #ClassName new openWithSpec > It seems that all the examples are opened with the same size. > The image on the left is the "default" one, the one on the right is what I > would like to get. > I've tried by changing the width: of the column but that doesn't change the > size of the window. > I'm kind of stuck! > > thanks > cheers > Nacho > <http://forum.world.st/file/n4719478/calc.jpg> > > > > ----- > Nacho > Smalltalker apprentice. > Buenos Aires, Argentina. > -- > View this message in context: http://forum.world.st/Adjusting-the-size-of-a-window-using-Spec-tp4719478.h… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Nov. 6, 2013

Re: [Pharo-users] rawSourceRanges in Encoder class question

by Marcus Denker

Hello, In Pharo3, we replace the *whole* stuff by something new which is much easier to understand. So In Pharo3, all this is not used (Encoder, the old AST, Parser (subclass(!) of Scanner)â¦ The first update of Pharo4 will be to remove the old compiler and then take the opportunity to clean up the compiler API considerably (the old Compiler then will be available as a loadable package, but only for third-party tools like SLANG, not in a state where it could replace the new infrastructure, as the API changes will not be portable without huge changes). So question: do you need to use the old Compiler? A quick overview can be found here: http://marcusdenker.de/publications/Bera13a-OpalIWST.pdf One nice thing (I think) is that we replaced the source code mapping infrastructure completely with one based on the RB AST / Opal IR. It is (at least for me) much cleaner and easier to understand. And it is especially easier to hack. Marcus On 06 Nov 2013, at 02:27, Gabriel Bursztyn <gabrielbursztyn(a)hotmail.com> wrote: > Hi guys, I am new in this list. > I have a question related to the sourceRanges dictionary in Encoder class. I can see every compiled method has each corresponding methodNode, which is an instance of a ParseNode child class. Every methodNode is formed by different parts represented by other classes also children of ParseNode, like AssignmentNode or MessageNode. > when you decompile the method into the MethodNode, the Encoder instance saves the intervals corresponding to each of these parts. It not saves all the parts, just the AssignmentNode, MessageNode and ReturnNode. (other intervals like the ones corresponding to TempVariableNodes for instance are not saved). The weird thing is that it saves the intervals for the MessageNodes but for some reason they do not corresponds to the positions in the sourceText method (property of MethodNode). I read that this sourceRanges is used for debugging purposes, and I hadn't issues debugging my code. I do not know if it is a bug or I do not understand well the Parser class. > I am using Pharo 2.0 and this code is also in squeak and cuis versions as well. > Example: > > I have created an example class with the following method: > ExampleClass>>#method1: > method1 > | a | > a := 1 + (2 * 3). > ^ a > > --- So if i inspect the rawSourceRanges:.. > (ExampleClass>>#method1) methodNode rawSourceRanges, I have a dictionary with the following keys: > a := 1 + (2 * 3). (AssignmentNode) --> 19 to 30 (so if i extract the characters from 19 to 30 in the sourceText I obtain the AssignmentNode text) > 1 + (2 * 3) (MessageNode) --> 24 to 30 > 2 * 3 - (MessageNode) --> 28 to 29 ( it is not logic to have an interval for 2 characters if 2*3 (without spaces) has 3 characters. > ^ a (ReturnNode) --> 34 to 35. > > > So the ASsignmentNode and ReturnNode have their corresponding sourceText interval but from MessageNodes, I cannot see the same. > Can anyone of you explain me why or if it is a bug? > If you would like to watch a little more, the sourceRanges is filled in the Encoder class, when the Parser is parsing a method. > > thanks

Nov. 6, 2013

Spec - TextModel whenTextIsAccepted

by Bahman Movaqar

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. 6, 2013

rawSourceRanges in Encoder class question

by Gabriel Bursztyn

Hi guys, I am new in this list.I have a question related to the sourceRanges dictionary in Encoder class. I can see every compiled method has each corresponding methodNode, which is an instance of a ParseNode child class. Every methodNode is formed by different parts represented by other classes also children of ParseNode, like AssignmentNode or MessageNode. when you decompile the method into the MethodNode, the Encoder instance saves the intervals corresponding to each of these parts. It not saves all the parts, just the AssignmentNode, MessageNode and ReturnNode. (other intervals like the ones corresponding to TempVariableNodes for instance are not saved). The weird thing is that it saves the intervals for the MessageNodes but for some reason they do not corresponds to the positions in the sourceText method (property of MethodNode). I read that this sourceRanges is used for debugging purposes, and I hadn't issues debugging my code. I do not know if it is a bug or I do not understand well the Parser class.I am using Pharo 2.0 and this code is also in squeak and cuis versions as well.Example: I have created an example class with the following method:ExampleClass>>#method1:method1 | a | a := 1 + (2 * 3). ^ a --- So if i inspect the rawSourceRanges:.. (ExampleClass>>#method1) methodNode rawSourceRanges, I have a dictionary with the following keys: a := 1 + (2 * 3). (AssignmentNode) --> 19 to 30 (so if i extract the characters from 19 to 30 in the sourceText I obtain the AssignmentNode text) 1 + (2 * 3) (MessageNode) --> 24 to 30 2 * 3 - (MessageNode) --> 28 to 29 ( it is not logic to have an interval for 2 characters if 2*3 (without spaces) has 3 characters. ^ a (ReturnNode) --> 34 to 35. So the ASsignmentNode and ReturnNode have their corresponding sourceText interval but from MessageNodes, I cannot see the same. Can anyone of you explain me why or if it is a bug? If you would like to watch a little more, the sourceRanges is filled in the Encoder class, when the Parser is parsing a method. thanks

Nov. 6, 2013

Adjusting the size of a window using Spec

by nacho

Continuing with my testing to learn Spec, I'm trying to build a really basic calculator. So far I managed to build the basic UI. However, I'm having some trouble at getting it displayed at the correct size. I don't know how to change the window that is opened when #ClassName new openWithSpec It seems that all the examples are opened with the same size. The image on the left is the "default" one, the one on the right is what I would like to get. I've tried by changing the width: of the column but that doesn't change the size of the window. I'm kind of stuck! thanks cheers Nacho <http://forum.world.st/file/n4719478/calc.jpg> ----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://forum.world.st/Adjusting-the-size-of-a-window-using-Spec-tp4719478.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 6, 2013

Re: [Pharo-users] Pharo 3.0.0.dmg for Mac OSX

by Joachim Tuchel

Bruce, Try opening it once with ctrl+click and answer the following answer withYES. The DMg most probably is okay, this is a new OS X feature. Joachim Am 05.11.2013 um 19:03 schrieb Bruce Prior <b.prior(a)ieee.org>: > Hi Damien, > I tried your .dmg file on my iMac running OS 10.9 (Mavericks). It didn't work. The error message is "Pharo.app is damaged and can't be opened." A second download and retry gave the same result.

Nov. 5, 2013