Re: [Pharo-users] SerialPlugin on MacOS

[Bernat Romagosa]

Thanks guys,

files.pharo.org is down right now

I'll try with a newer VM as soon as it's up again :)


2013/11/9 Stéphane Ducasse 

>
> On Nov 9, 2013, at 2:19 PM, Camillo Bruni  wrote:
>
> > Luc proposed a pull request on github
> > - got validated by travis
> > - I integrated it into the master branch
> > - I pushed the changes to the develop branch
> >
> > so the vmLatest should include the fixes
>
> I like the process and that esteban releases some steam :)
>
> Stef
>
> >
> > On 2013-11-09, at 13:56, Stéphane Ducasse 
> wrote:
> >> Esteban
> >>
> >> we should organize some sessions where you show to people what you are
> doing and see how we
> >> should distribute and share load.
> >>
> >> Stef
> >>
> >> On Nov 9, 2013, at 12:29 PM, Esteban Lorenzano 
> wrote:
> >>
> >>> Hi,
> >>>
> >>> it is "stable" but AFAIK it does not includes the latest fix for
> SerialPlugin.
> >>> So many things to do when I come back... :)
> >>>
> >>> Esteban
> >>>
> >>>
> >>> On Nov 5, 2013, at 8:27 AM, Bernat Romagosa <
> tibabenfortlapala...@gmail.com> wrote:
> >>>
>  Hi Luc,
> 
>  Smalltalk vm version reports:
> 
>  'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid:
> a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013
>  NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid:
> a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013
>  git://gitorious.org/cogvm/blessed.git Commit:
> 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100
> By: Esteban Lorenzano  Jenkins build #14535
>  '
> 
>  It's the one listed as "latest" at the downloads section in
> pharo-project.org
> 
>  Cheers,
>  Bernat.
> 
> 
>  2013/11/5 Luc Fabresse 
> 
> 
>  2013/11/5 Luc Fabresse 
>  Hi Bernat,
> 
>   Which VM version?
>   because MacOsX and Linux now use the same C part of the SerialPlugin.
>   So if it works on Linux, it be the same on OsX.
>   but I have not tried.
> 
>  yes we only use Linux here for serial stuff.
> 
> 
>  do you use the right protName?
> 
>  Cheers,
> 
>  Luc
> 
> 
>  2013/11/5 Bernat Romagosa 
>  Hi list,
> 
>  Developing a multi-platform application is not so easy when you have
> to deal with hardware it seems...
> 
>  So I'm having this PrimitiveFailed error on MacOS, using the latest
> stable VM listed on the pharo-project website on Pharo20:
> 
>  PrimitiveFailed: primitive
> #primWritePortByName:from:startingAt:count: in SerialPort failed
> 
>  The same code works fine both in Gnu/Linux and Win32, so I'm guessing
> it's a problem with the serial plugin included in this VM. Any ideas?
> 
>  Cheers,
>  Bernat.
> 
>  --
>  Bernat Romagosa.
> 
> 
> 
> 
> 
>  --
>  Bernat Romagosa.
> >>>
> >>
> >
> >
>
>
>


-- 
Bernat Romagosa.

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

[prova email]

Hi Ben, are you sure that the message "widgetDo:" is  the right one? It's not a 
message that my object looks to understand. Thanks in advance.Paolo

From: benjamin.vanryseghem.ph...@gmail.com
Date: Fri, 8 Nov 2013 14:34:18 +0100
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] Spec - Grid/Table Layout

It is definitely defined in TreeModel :)
Ben



On 08 Nov 2013, at 14:29, prova email  wrote:Very very 
very good Ben, thanks a lot. Last question: you use the "columns:" message, but 
it's not defined in TreeModel. You defined it hereMorphTreeAdapter>>#columns:   
columns: columns self widgetDo: [ :w |  
w columns: columns. w 
resizerChanged.   w updateList ]
in the brand new Class MorphTreeAdapter. What's the difference between define 
columns: here instead of in the TreeModel class?Great job and thank you!Paolo

From: benjamin.vanryseghem.ph...@gmail.com
Date: Fri, 8 Nov 2013 14:15:46 +0100
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] Spec - Grid/Table Layout

tree := TreeModel new.tree openWithSpec.
tree columns: (Arraywith: (MorphTreeColumn new rowMorphGetSelector: [:node 
| node item first asString asMorph ]; headerButtonLabel: 'Name' font: nil; 
yourself) with: (MorphTreeColumn new rowMorphGetSelector: [:node | node 
item second asString asMorph ]; headerButtonLabel: 'Last Name' font: nil; 
yourself)   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node 
item third asString asMorph ]; headerButtonLabel: 'Age' font: nil; yourself)
  with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item fourth 
asString asMorph ]; headerButtonLabel:  'Gender' font: nil; yourself) with: 
(MorphTreeColumn new rowMorphGetSelector: [:node | (ButtonModel new label: 'Yes 
we can') buildWithSpec hResizing: #spaceFill]; headerButtonLabel:  'Morph' 
font: nil; yourself)). tree roots: {   {'Benjamin'.'Van Ryseghem'.'26'.'M'}.   
{'Pamela'.'Anderson'.'Far too much'.'F'}} Ben
On 08 Nov 2013, at 14:05, prova email  wrote:Yes Ben, too 
much threads! That's why i'm a little bit confused! That's what i understood: 
i've got two roads-> use TreeModel as you did with Pamela Anderson or use the 
simple and nested SpecLayout (SpecLayout composed) as Clement did.If in your 
TreeModel i can put a RadioButtonModel or a ButtonModel or so on... we got the 
deal!
Paolo
From: benjamin.vanryseghem.ph...@gmail.com
Date: Fri, 8 Nov 2013 13:59:51 +0100
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] Spec - Grid/Table Layout

I guess too much threads :)
I answer this in another thread I think :P
the block provided to displayBlock:/rowMorphGetSelector: can return anything 
understanding asMorph.So you can return any custom morph there :)
I think the following work
tree columns: (Array 
with: (TreeColumnModel new displayBlock: [:node | node content first 
asString ]; headerLabel: 'Name'; yourself)
with: (TreeColumnModel new displayBlock: [:node | node content second 
asString ]; headerLabel: 'Last Name'; yourself)
with: (TreeColumnModel new displayBlock: [:node | node content third 
asString ]; headerLabel: 'Age'; yourself)
with: (TreeColumnModel new displayBlock: [:node | node content fourth 
asString ]; headerLabel: 'Gender'; yourself)  with: (TreeColumnModel new 
displayBlock: [:node | Morph new ]; headerLabel: ‘Morph'; yourself))
or
tree columns: (Arraywith: (MorphTreeColumn new rowMorphGetSelector: [:node 
| node item first asString asMorph ]; headerButtonLabel: 'Name' font: nil; 
yourself) with: (MorphTreeColumn new rowMorphGetSelector: [:node | node 
item second asString asMorph ]; headerButtonLabel: 'Last Name' font: nil; 
yourself)   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node 
item third asString asMorph ]; headerButtonLabel: 'Age' font: nil; yourself)
  with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item fourth 
asString asMorph ]; headerButtonLabel:  'Gender' font: nil; yourself) with: 
(MorphTreeColumn new rowMorphGetSelector: [:node | Morph new ]; 
headerButtonLabel:  'Morph' font: nil; yourself)).And you get something like
Ben
On 08 Nov 2013, at 13:45, prova email  wrote:Yes Clement, 
i've got your .st file. I saw it in Nested Layout thread. I file in it in Pharo 
and i see that is not as good as a fashion window is. Maybe Morphic is the 
right solution but, in that way, we are leaving the idea of Bahman, and the 2nd 
Spec Tuto is in danger!
However, you asked to Ben the same question that i did: can i put some widgets 
in these cells or only String? 
Thanks again!Paolo

From: bera.clem...@gmail.com
Date: Fri, 8 Nov 2013 12:51:06 +0100
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] Spec - Grid/Table Layout

Ben answered in another thread:
About table, I have an example which will be running soon in Pharo (the changes 
are waiting to be integrated)
tree := 

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

[Benjamin]

I am sure that Adapters understands widgetDo:
To which objects do you send this message ?

Ben

On 11 Nov 2013, at 11:08, prova email  wrote:

> Hi Ben, 
> are you sure that the message "widgetDo:" is  the right one? It's not a 
> message that my object looks to understand. 
> Thanks in advance.
> Paolo
> 
> From: benjamin.vanryseghem.ph...@gmail.com
> Date: Fri, 8 Nov 2013 14:34:18 +0100
> To: pharo-users@lists.pharo.org
> Subject: Re: [Pharo-users] Spec - Grid/Table Layout
> 
> It is definitely defined in TreeModel :)
> 
> Ben
> 
> On 08 Nov 2013, at 14:29, prova email  wrote:
> 
> Very very very good Ben, thanks a lot. Last question: you use the "columns:" 
> message, but it's not defined in TreeModel. You defined it here
> MorphTreeAdapter>>#columns:
>   columns: columns 
>self widgetDo: [ :w | 
>   w columns: columns. 
>   w resizerChanged. 
>   w updateList ]
> 
> in the brand new Class MorphTreeAdapter. What's the difference between define 
> columns: here instead of in the TreeModel class?
> Great job and thank you!
> Paolo
> 
> 
> From: benjamin.vanryseghem.ph...@gmail.com
> Date: Fri, 8 Nov 2013 14:15:46 +0100
> To: pharo-users@lists.pharo.org
> Subject: Re: [Pharo-users] Spec - Grid/Table Layout
> 
> tree := TreeModel new.
> tree openWithSpec.
> 
> tree columns: (Array 
>   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item 
> first asString asMorph ]; headerButtonLabel: 'Name' font: nil; yourself)
>   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item 
> second asString asMorph ]; headerButtonLabel: 'Last Name' font: nil; yourself)
>   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item 
> third asString asMorph ]; headerButtonLabel: 'Age' font: nil; yourself)
>   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item 
> fourth asString asMorph ]; headerButtonLabel:  'Gender' font: nil; yourself)
>   with: (MorphTreeColumn new rowMorphGetSelector: [:node | (ButtonModel 
> new label: 'Yes we can') buildWithSpec hResizing: #spaceFill]; 
> headerButtonLabel:  'Morph' font: nil; yourself)).
>   
> tree roots: {
>   {'Benjamin'.'Van Ryseghem'.'26'.'M'}.
>   {'Pamela'.'Anderson'.'Far too much'.'F'}
> } 
> 
> Ben
> 
> On 08 Nov 2013, at 14:05, prova email  wrote:
> 
> Yes Ben, too much threads! That's why i'm a little bit confused! That's what 
> i understood: i've got two roads-> use TreeModel as you did with Pamela 
> Anderson or use the simple and nested SpecLayout (SpecLayout composed) as 
> Clement did.
> If in your TreeModel i can put a RadioButtonModel or a ButtonModel or so 
> on... we got the deal!
> 
> Paolo
> 
> From: benjamin.vanryseghem.ph...@gmail.com
> Date: Fri, 8 Nov 2013 13:59:51 +0100
> To: pharo-users@lists.pharo.org
> Subject: Re: [Pharo-users] Spec - Grid/Table Layout
> 
> I guess too much threads :)
> 
> I answer this in another thread I think :P
> 
> the block provided to displayBlock:/rowMorphGetSelector: can return anything 
> understanding asMorph.
> So you can return any custom morph there :)
> 
> I think the following work
> 
> tree columns: (Array 
>   with: (TreeColumnModel new displayBlock: [:node | node content first 
> asString ]; headerLabel: 'Name'; yourself)
>   with: (TreeColumnModel new displayBlock: [:node | node content second 
> asString ]; headerLabel: 'Last Name'; yourself)
>   with: (TreeColumnModel new displayBlock: [:node | node content third 
> asString ]; headerLabel: 'Age'; yourself)
>   with: (TreeColumnModel new displayBlock: [:node | node content fourth 
> asString ]; headerLabel: 'Gender'; yourself)
>   with: (TreeColumnModel new displayBlock: [:node | Morph new ]; 
> headerLabel: ‘Morph'; yourself))
> 
> or
> 
> tree columns: (Array 
>   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item 
> first asString asMorph ]; headerButtonLabel: 'Name' font: nil; yourself)
>   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item 
> second asString asMorph ]; headerButtonLabel: 'Last Name' font: nil; yourself)
>   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item 
> third asString asMorph ]; headerButtonLabel: 'Age' font: nil; yourself)
>   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item 
> fourth asString asMorph ]; headerButtonLabel:  'Gender' font: nil; yourself)
>   with: (MorphTreeColumn new rowMorphGetSelector: [:node | Morph new ]; 
> headerButtonLabel:  'Morph' font: nil; yourself)).
> 
> And you get something like
> 
> 
> 
> Ben
> 
> On 08 Nov 2013, at 13:45, prova email  wrote:
> 
> Yes Clement, i've got your .st file. I saw it in Nested Layout thread. I file 
> in it in Pharo and i see that is not as good as a fashion window is. Maybe 
> Morphic is the right solution but, in that way, we are leaving the idea of 
> Bahman, and the 2nd Spe

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

[prova email]

I'm doing a TreeModel. As you know, widgetDo is not a message of TreeModel, 
that's why i was asking you if there something wrong. As i asked you in a old 
post, column: is not a message of TreeModel, so, where do i have to create that 
message? The following code means to me that i have to create column: into 
MorphTreeAdapter, a class that i haven't got into my Pharo 2.0.
MorphTreeAdapter>>#columns: columns: columns
 self widgetDo: [ :w |  w columns: columns. 
w resizerChanged.   w updateList 
]PaoloFrom: benjamin.vanryseghem.ph...@gmail.com
Date: Mon, 11 Nov 2013 12:03:13 +0100
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] Spec - Grid/Table Layout

I am sure that Adapters understands widgetDo:To which objects do you send this 
message ?

Ben



On 11 Nov 2013, at 11:08, prova email  wrote:Hi Ben, are 
you sure that the message "widgetDo:" is  the right one? It's not a message 
that my object looks to understand. Thanks in advance.Paolo

From: benjamin.vanryseghem.ph...@gmail.com
Date: Fri, 8 Nov 2013 14:34:18 +0100
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] Spec - Grid/Table Layout

It is definitely defined in TreeModel :)
Ben
On 08 Nov 2013, at 14:29, prova email  wrote:Very very 
very good Ben, thanks a lot. Last question: you use the "columns:" message, but 
it's not defined in TreeModel. You defined it hereMorphTreeAdapter>>#columns:   
columns: columns self widgetDo: [ :w |  
w columns: columns. w 
resizerChanged.   w updateList ]
in the brand new Class MorphTreeAdapter. What's the difference between define 
columns: here instead of in the TreeModel class?Great job and thank you!Paolo

From: benjamin.vanryseghem.ph...@gmail.com
Date: Fri, 8 Nov 2013 14:15:46 +0100
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] Spec - Grid/Table Layout

tree := TreeModel new.tree openWithSpec.
tree columns: (Arraywith: (MorphTreeColumn new rowMorphGetSelector: [:node 
| node item first asString asMorph ]; headerButtonLabel: 'Name' font: nil; 
yourself) with: (MorphTreeColumn new rowMorphGetSelector: [:node | node 
item second asString asMorph ]; headerButtonLabel: 'Last Name' font: nil; 
yourself)   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node 
item third asString asMorph ]; headerButtonLabel: 'Age' font: nil; yourself)
  with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item fourth 
asString asMorph ]; headerButtonLabel:  'Gender' font: nil; yourself) with: 
(MorphTreeColumn new rowMorphGetSelector: [:node | (ButtonModel new label: 'Yes 
we can') buildWithSpec hResizing: #spaceFill]; headerButtonLabel:  'Morph' 
font: nil; yourself)). tree roots: {   {'Benjamin'.'Van Ryseghem'.'26'.'M'}.   
{'Pamela'.'Anderson'.'Far too much'.'F'}} Ben
On 08 Nov 2013, at 14:05, prova email  wrote:Yes Ben, too 
much threads! That's why i'm a little bit confused! That's what i understood: 
i've got two roads-> use TreeModel as you did with Pamela Anderson or use the 
simple and nested SpecLayout (SpecLayout composed) as Clement did.If in your 
TreeModel i can put a RadioButtonModel or a ButtonModel or so on... we got the 
deal!
Paolo
From: benjamin.vanryseghem.ph...@gmail.com
Date: Fri, 8 Nov 2013 13:59:51 +0100
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] Spec - Grid/Table Layout

I guess too much threads :)
I answer this in another thread I think :P
the block provided to displayBlock:/rowMorphGetSelector: can return anything 
understanding asMorph.So you can return any custom morph there :)
I think the following work
tree columns: (Array 
with: (TreeColumnModel new displayBlock: [:node | node content first 
asString ]; headerLabel: 'Name'; yourself)
with: (TreeColumnModel new displayBlock: [:node | node content second 
asString ]; headerLabel: 'Last Name'; yourself)
with: (TreeColumnModel new displayBlock: [:node | node content third 
asString ]; headerLabel: 'Age'; yourself)
with: (TreeColumnModel new displayBlock: [:node | node content fourth 
asString ]; headerLabel: 'Gender'; yourself)  with: (TreeColumnModel new 
displayBlock: [:node | Morph new ]; headerLabel: ‘Morph'; yourself))
or
tree columns: (Arraywith: (MorphTreeColumn new rowMorphGetSelector: [:node 
| node item first asString asMorph ]; headerButtonLabel: 'Name' font: nil; 
yourself) with: (MorphTreeColumn new rowMorphGetSelector: [:node | node 
item second asString asMorph ]; headerButtonLabel: 'Last Name' font: nil; 
yourself)   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node 
item third asString asMorph ]; headerButtonLabel: 'Age' font: nil; yourself)
  with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item fourth 
asString asMorph ]; headerButtonLabel:  'Gender'

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

[Benjamin]

Now I get it :)

This is not supported in 2.0 in the sense that the Spec version shipped with 
Pharo 2.0 has evolved :)

You can try it in Pharo 3.0 :)

Ben

On 11 Nov 2013, at 12:08, prova email  wrote:

> I'm doing a TreeModel. As you know, widgetDo is not a message of TreeModel, 
> that's why i was asking you if there something wrong. As i asked you in a old 
> post, column: is not a message of TreeModel, so, where do i have to create 
> that message? The following code means to me that i have to create column: 
> into MorphTreeAdapter, a class that i haven't got into my Pharo 2.0.
> 
> MorphTreeAdapter>>#columns:
>   columns: columns 
>self widgetDo: [ :w | 
>   w columns: columns. 
>   w resizerChanged. 
>   w updateList ]
> Paolo
> From: benjamin.vanryseghem.ph...@gmail.com
> Date: Mon, 11 Nov 2013 12:03:13 +0100
> To: pharo-users@lists.pharo.org
> Subject: Re: [Pharo-users] Spec - Grid/Table Layout
> 
> I am sure that Adapters understands widgetDo:
> To which objects do you send this message ?
> 
> Ben
> 
> On 11 Nov 2013, at 11:08, prova email  wrote:
> 
> Hi Ben, 
> are you sure that the message "widgetDo:" is  the right one? It's not a 
> message that my object looks to understand. 
> Thanks in advance.
> Paolo
> 
> From: benjamin.vanryseghem.ph...@gmail.com
> Date: Fri, 8 Nov 2013 14:34:18 +0100
> To: pharo-users@lists.pharo.org
> Subject: Re: [Pharo-users] Spec - Grid/Table Layout
> 
> It is definitely defined in TreeModel :)
> 
> Ben
> 
> On 08 Nov 2013, at 14:29, prova email  wrote:
> 
> Very very very good Ben, thanks a lot. Last question: you use the "columns:" 
> message, but it's not defined in TreeModel. You defined it here
> MorphTreeAdapter>>#columns:
>   columns: columns 
>self widgetDo: [ :w | 
>   w columns: columns. 
>   w resizerChanged. 
>   w updateList ]
> 
> in the brand new Class MorphTreeAdapter. What's the difference between define 
> columns: here instead of in the TreeModel class?
> Great job and thank you!
> Paolo
> 
> 
> From: benjamin.vanryseghem.ph...@gmail.com
> Date: Fri, 8 Nov 2013 14:15:46 +0100
> To: pharo-users@lists.pharo.org
> Subject: Re: [Pharo-users] Spec - Grid/Table Layout
> 
> tree := TreeModel new.
> tree openWithSpec.
> 
> tree columns: (Array 
>   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item 
> first asString asMorph ]; headerButtonLabel: 'Name' font: nil; yourself)
>   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item 
> second asString asMorph ]; headerButtonLabel: 'Last Name' font: nil; yourself)
>   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item 
> third asString asMorph ]; headerButtonLabel: 'Age' font: nil; yourself)
>   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item 
> fourth asString asMorph ]; headerButtonLabel:  'Gender' font: nil; yourself)
>   with: (MorphTreeColumn new rowMorphGetSelector: [:node | (ButtonModel 
> new label: 'Yes we can') buildWithSpec hResizing: #spaceFill]; 
> headerButtonLabel:  'Morph' font: nil; yourself)).
>   
> tree roots: {
>   {'Benjamin'.'Van Ryseghem'.'26'.'M'}.
>   {'Pamela'.'Anderson'.'Far too much'.'F'}
> } 
> 
> Ben
> 
> On 08 Nov 2013, at 14:05, prova email  wrote:
> 
> Yes Ben, too much threads! That's why i'm a little bit confused! That's what 
> i understood: i've got two roads-> use TreeModel as you did with Pamela 
> Anderson or use the simple and nested SpecLayout (SpecLayout composed) as 
> Clement did.
> If in your TreeModel i can put a RadioButtonModel or a ButtonModel or so 
> on... we got the deal!
> 
> Paolo
> 
> From: benjamin.vanryseghem.ph...@gmail.com
> Date: Fri, 8 Nov 2013 13:59:51 +0100
> To: pharo-users@lists.pharo.org
> Subject: Re: [Pharo-users] Spec - Grid/Table Layout
> 
> I guess too much threads :)
> 
> I answer this in another thread I think :P
> 
> the block provided to displayBlock:/rowMorphGetSelector: can return anything 
> understanding asMorph.
> So you can return any custom morph there :)
> 
> I think the following work
> 
> tree columns: (Array 
>   with: (TreeColumnModel new displayBlock: [:node | node content first 
> asString ]; headerLabel: 'Name'; yourself)
>   with: (TreeColumnModel new displayBlock: [:node | node content second 
> asString ]; headerLabel: 'Last Name'; yourself)
>   with: (TreeColumnModel new displayBlock: [:node | node content third 
> asString ]; headerLabel: 'Age'; yourself)
>   with: (TreeColumnModel new displayBlock: [:node | node content fourth 
> asString ]; headerLabel: 'Gender'; yourself)
>   with: (TreeColumnModel new displayBlock: [:node | Morph new ]; 
> headerLabel: ‘Morph'; yourself))
> 
> or
> 
> tree columns: (Array 
>   with: (MorphTreeColumn new rowMorphGetSelect

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

[prova email]

As i imagined XD
From: benjamin.vanryseghem.ph...@gmail.com
Date: Mon, 11 Nov 2013 13:16:12 +0100
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] Spec - Grid/Table Layout

Now I get it :)
This is not supported in 2.0 in the sense that the Spec version shipped with 
Pharo 2.0 has evolved :)
You can try it in Pharo 3.0 :)
Ben



On 11 Nov 2013, at 12:08, prova email  wrote:I'm doing a 
TreeModel. As you know, widgetDo is not a message of TreeModel, that's why i 
was asking you if there something wrong. As i asked you in a old post, column: 
is not a message of TreeModel, so, where do i have to create that message? The 
following code means to me that i have to create column: into MorphTreeAdapter, 
a class that i haven't got into my Pharo 2.0.
MorphTreeAdapter>>#columns: columns: columns
 self widgetDo: [ :w |  w columns: columns. 
w resizerChanged.   w updateList 
]PaoloFrom: benjamin.vanryseghem.ph...@gmail.com
Date: Mon, 11 Nov 2013 12:03:13 +0100
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] Spec - Grid/Table Layout

I am sure that Adapters understands widgetDo:To which objects do you send this 
message ?
Ben
On 11 Nov 2013, at 11:08, prova email  wrote:Hi Ben, are 
you sure that the message "widgetDo:" is  the right one? It's not a message 
that my object looks to understand. Thanks in advance.Paolo

From: benjamin.vanryseghem.ph...@gmail.com
Date: Fri, 8 Nov 2013 14:34:18 +0100
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] Spec - Grid/Table Layout

It is definitely defined in TreeModel :)
Ben
On 08 Nov 2013, at 14:29, prova email  wrote:Very very 
very good Ben, thanks a lot. Last question: you use the "columns:" message, but 
it's not defined in TreeModel. You defined it hereMorphTreeAdapter>>#columns:   
columns: columns self widgetDo: [ :w |  
w columns: columns. w 
resizerChanged.   w updateList ]
in the brand new Class MorphTreeAdapter. What's the difference between define 
columns: here instead of in the TreeModel class?Great job and thank you!Paolo

From: benjamin.vanryseghem.ph...@gmail.com
Date: Fri, 8 Nov 2013 14:15:46 +0100
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] Spec - Grid/Table Layout

tree := TreeModel new.tree openWithSpec.
tree columns: (Arraywith: (MorphTreeColumn new rowMorphGetSelector: [:node 
| node item first asString asMorph ]; headerButtonLabel: 'Name' font: nil; 
yourself) with: (MorphTreeColumn new rowMorphGetSelector: [:node | node 
item second asString asMorph ]; headerButtonLabel: 'Last Name' font: nil; 
yourself)   with: (MorphTreeColumn new rowMorphGetSelector: [:node | node 
item third asString asMorph ]; headerButtonLabel: 'Age' font: nil; yourself)
  with: (MorphTreeColumn new rowMorphGetSelector: [:node | node item fourth 
asString asMorph ]; headerButtonLabel:  'Gender' font: nil; yourself) with: 
(MorphTreeColumn new rowMorphGetSelector: [:node | (ButtonModel new label: 'Yes 
we can') buildWithSpec hResizing: #spaceFill]; headerButtonLabel:  'Morph' 
font: nil; yourself)). tree roots: {   {'Benjamin'.'Van Ryseghem'.'26'.'M'}.   
{'Pamela'.'Anderson'.'Far too much'.'F'}} Ben
On 08 Nov 2013, at 14:05, prova email  wrote:Yes Ben, too 
much threads! That's why i'm a little bit confused! That's what i understood: 
i've got two roads-> use TreeModel as you did with Pamela Anderson or use the 
simple and nested SpecLayout (SpecLayout composed) as Clement did.If in your 
TreeModel i can put a RadioButtonModel or a ButtonModel or so on... we got the 
deal!
Paolo
From: benjamin.vanryseghem.ph...@gmail.com
Date: Fri, 8 Nov 2013 13:59:51 +0100
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] Spec - Grid/Table Layout

I guess too much threads :)
I answer this in another thread I think :P
the block provided to displayBlock:/rowMorphGetSelector: can return anything 
understanding asMorph.So you can return any custom morph there :)
I think the following work
tree columns: (Array 
with: (TreeColumnModel new displayBlock: [:node | node content first 
asString ]; headerLabel: 'Name'; yourself)
with: (TreeColumnModel new displayBlock: [:node | node content second 
asString ]; headerLabel: 'Last Name'; yourself)
with: (TreeColumnModel new displayBlock: [:node | node content third 
asString ]; headerLabel: 'Age'; yourself)
with: (TreeColumnModel new displayBlock: [:node | node content fourth 
asString ]; headerLabel: 'Gender'; yourself)  with: (TreeColumnModel new 
displayBlock: [:node | Morph new ]; headerLabel: ‘Morph'; yourself))
or
tree columns: (Arraywith: (MorphTreeColumn new rowMorphGetSelector: [:node 
| node item first asString asMorph ]; headerButtonLabel: 'Name' font: nil; 
yourself) with: (MorphTreeColumn new rowMorphGetSel

[Pharo-users] Fwd: Pharo download links are down.

[Arturo Zambrano]

Hi All,
sorry if it 's already reported: everything in
http://files.pharo.org/platform
is returning the following error message.


ERRORThe requested URL could not be retrieved
--

The following error was encountered while trying to retrieve the URL:
http://files.pharo.org/platform/Pharo2.0-linux.zip

*Connection to 128.93.162.72 failed.*

The system returned: *(111) Connection refused*

Re: [Pharo-users] Fwd: Pharo download links are down.

[kilon alios]

yeah scheduled maintenance , will be working tomorrow.


On Mon, Nov 11, 2013 at 6:40 PM, Arturo Zambrano
wrote:

>
> Hi All,
> sorry if it 's already reported: everything in
> http://files.pharo.org/platform
> is returning the following error message.
>
>
> ERRORThe requested URL could not be retrieved
> --
>
> The following error was encountered while trying to retrieve the URL:
> http://files.pharo.org/platform/Pharo2.0-linux.zip
>
> *Connection to 128.93.162.72 failed.*
>
> The system returned: *(111) Connection refused*
>
>
>

[Pharo-users] Spec - Disable auto-complete in text box

[Bahman Movaqar]

Hi all,

Is it possible to disable auto-completion in a text box?  I've tried
`textName isCodeCompletionAllowed: false` to no avail.  Am I doing it
wrong? Any other way to do it?

TIA,

-- 
Bahman Movaqar  (http://BahmanM.com)

ERP Evaluation, Implementation & Deployment Consultant
PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)




signature.asc
Description: OpenPGP digital signature

[Pharo-users] Spec - Layout behaviour when resizing

[Bahman Movaqar]

  
  
Hi all,
  
  Let's assume I have a window like the one in episode 2 of
the tutorial. Some unexpected (from the user's perspective)
  behaviour happens when I manually resize the window.  A snapshot
  is worth a thousand words (and I'm going to put two snapshots
  here!).

This is the fresh window
that I just opened:
  
  
  
  The same window after resizing:
  
  
  
  So this is my understanding:
  When a window is resized, every Row/ColumnLayout distributes the width and height evenly among any
  widget or nested layouts it contains.  In turn, widgets try to
  fill as much space as possible.  Therefore after resizing text box
  and button have become so huge and the space between the radio
  buttons has increased so much.
  Is that correct?
  
  If yes, I have a couple of points to mention:


  A text box, specially in the case of TextModel
and TextInputFieldModel, where it's basically a single line entry
  (ENTER is not allowed), should not change height (growing
  width is understandable and desired).  The height of a text
  box (specially a single line one) should only be calculated
  based on the font family and font size.

  A button should not change height and width,
  unless specifically mentioned otherwise.
  It's not usually desirable that the spacing
  between radio buttons change.
  Usually there's a way to specify how to
  distribute the width/height between layouts and widgets inside
  a layout (usually based on a percentage). 


I'd appreciate if anyone could shed a light
here; specially Benjamin the Undocumenter :-)


-- 
Bahman Movaqar  (http://BahmanM.com)

ERP Evaluation, Implementation & Deployment Consultant
PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)
  




signature.asc
Description: OpenPGP digital signature

Re: [Pharo-users] Spec - Layout behaviour when resizing

[Benjamin]

I do not get the image, but I know what happened :)


On 11 Nov 2013, at 20:08, Bahman Movaqar  wrote:

> Hi all,
> 
> Let's assume I have a window like the one in episode 2 of the tutorial. Some 
> unexpected (from the user's perspective) behaviour happens when I manually 
> resize the window.  A snapshot is worth a thousand words (and I'm going to 
> put two snapshots here!).
> 
> This is the fresh window that I just opened:
> 
> 
> 
> The same window after resizing:
> 
> 
> 
> So this is my understanding:
> When a window is resized, every Row/ColumnLayout distributes the width and 
> height evenly among any widget or nested layouts it contains.  In turn, 
> widgets try to fill as much space as possible.  Therefore after resizing text 
> box and button have become so huge and the space between the radio buttons 
> has increased so much.
> Is that correct?

It’s correct in the sense it is expected regarding to the layout you use :)

> If yes, I have a couple of points to mention:
> A text box, specially in the case of TextModel and TextInputFieldModel, where 
> it's basically a single line entry (ENTER is not allowed), should not change 
> height (growing width is understandable and desired).  The height of a text 
> box (specially a single line one) should only be calculated based on the font 
> family and font size.
TextModel is for more that one line :)
TextInputField could eventually be forced to be one line, but I think it’s too 
much of a restriction

> A button should not change height and width, unless specifically mentioned 
> otherwise.
Why ?
> It's not usually desirable that the spacing between radio buttons change.
That’s true :) 
But how to know that two radio buttons are close one to the other ?

> Usually there's a way to specify how to distribute the width/height between 
> layouts and widgets inside a layout (usually based on a percentage). 
There in spec as well :)
You can have a look at:
add:origin:corner:offsetOrigin:offsetCorner:

Ben
> I'd appreciate if anyone could shed a light here; specially Benjamin the 
> Undocumenter :-)
>  -- 
> Bahman Movaqar  (http://BahmanM.com)
> 
> ERP Evaluation, Implementation & Deployment Consultant
> PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)

Re: [Pharo-users] Spec - Disable auto-complete in text box

[Benjamin]

try entryCompletion: nil
and tell me if it does the job :)

Ben

On 11 Nov 2013, at 19:21, Bahman Movaqar  wrote:

> Hi all,
> 
> Is it possible to disable auto-completion in a text box?  I've tried
> `textName isCodeCompletionAllowed: false` to no avail.  Am I doing it
> wrong? Any other way to do it?
> 
> TIA,
> 
> -- 
> Bahman Movaqar  (http://BahmanM.com)
> 
> ERP Evaluation, Implementation & Deployment Consultant
> PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)
> 
> 

[Pharo-users] How to change background color

[Gisela Decuzzi]

Hi, I'm getting some problems trying to change the default colors for the
widgets.
I need to replace the gray color for a blue (yes, quite horrible, long
history).
I'm using Spec and didn't find how to do this, and after trying I end up
hacking in morph.

Is there a way to do this? Or someone can show me a starting point?

Re: [Pharo-users] How to change background color

[Benjamin]

A good pointer would be to add support for color on AbstractWidget and change a 
bit the way MorphicAdapters are built to take this color in account

Ben

On 11 Nov 2013, at 21:42, Gisela Decuzzi  wrote:

> Hi, I'm getting some problems trying to change the default colors for the 
> widgets.
> I need to replace the gray color for a blue (yes, quite horrible, long 
> history).
> I'm using Spec and didn't find how to do this, and after trying I end up 
> hacking in morph.
> 
> Is there a way to do this? Or someone can show me a starting point?

Re: [Pharo-users] How to change background color

[Ignacio Matías Sniechowski]

Gisela,
I've been trying to do that, and also changing the alignment of the text
with no success.
saludos
nacho



*Lic. Ignacio Sniechowski, MBA*






On Mon, Nov 11, 2013 at 5:42 PM, Gisela Decuzzi wrote:

> Hi, I'm getting some problems trying to change the default colors for the
> widgets.
> I need to replace the gray color for a blue (yes, quite horrible, long
> history).
> I'm using Spec and didn't find how to do this, and after trying I end up
> hacking in morph.
>
> Is there a way to do this? Or someone can show me a starting point?
>

Re: [Pharo-users] How to change background color

[Sergi Reyner]

2013/11/11 Benjamin 

> A good pointer would be to add support for color on AbstractWidget and
> change a bit the way MorphicAdapters are built to take this color in account
>

Hmmm... I may or may not give it a try tonight/tomorrow morning :)

Cheers,
Sergi

Re: [Pharo-users] How to change background color

[Benjamin]

Cool :)

Keep me in touch then :)
I am visiting a customer this week, so I do not have all the time I would to 
test it, but I will give a try as soon as I can :)

Ben

On 11 Nov 2013, at 22:13, Sergi Reyner  wrote:

> 2013/11/11 Benjamin 
> A good pointer would be to add support for color on AbstractWidget and change 
> a bit the way MorphicAdapters are built to take this color in account
> 
> Hmmm... I may or may not give it a try tonight/tomorrow morning :)
> 
> Cheers,
> Sergi

Re: [Pharo-users] Spec - Layout behaviour when resizing

[Bahman Movaqar]

On 11/11/2013 22:52, Benjamin wrote:
> I do not get the image, but I know what happened :)

Oops!  Corrected that.

>
> On 11 Nov 2013, at 20:08, Bahman Movaqar  > wrote:
>
>>
>> When a window is resized, every Row/ColumnLayoutdistributes the width
>> and height evenly among any widget or nested layouts it contains.  In
>> turn, widgets try to fill as much space as possible.  Therefore after
>> resizing text box and button have become so huge and the space
>> between the radio buttons has increased so much.
>> Is that correct?
>
> It’s correct in the sense it is expected regarding to the layout you
> use :)
>
>> If yes, I have a couple of points to mention:
>>
>>  1. A text box, specially in the case of TextModel and
>> TextInputFieldModel, where it's basically a single line entry
>> (ENTER is not allowed), should not change height (growing width
>> is understandable and desired).  The height of a text box
>> (specially a single line one) should only be calculated based on
>> the font family and font size.
>>
> TextModel is for more that one line :)
> TextInputField could eventually be forced to be one line, but I think
> it’s too much of a restriction.

I am 100% sure I didn't tell TextInputField to accept one line.  It
doesn't accept ENTER and I don't understand how a "multi-line" text
entry widget can work without accepting new line character :-)
Yes, TextInputField wraps the text but that's doesn't count as
multi-line entry :-)  More importantly it is unexpected behaviour from
user's PoV; I have never seen a single text entry widget wrap the text.

Or maybe I'm doing something wrong?

>
>> 1.
>>
>>
>>
>>  2. A button should not change height and width, unless specifically
>> mentioned otherwise.
>>
> Why ?

Because if the button changes height/width it loses the visual element
which users use to recognise buttons across a screen. Just like a
single-line text entry, a button's height, if not manually set, is
determined only by the font family and font size.
And regarding changing the button width, I've very rarely seen
applications that resize their buttons when the screen is resized.
Usually people put constraints over this. I'm not stating that this
definitely should be some UI framework's internal mehcanism. Perhaps a
simple method like `isCalculatedSize: aBoolean` with a TRUE default is
enough.

>>  3. It's not usually desirable that the spacing between radio buttons
>> change.
>>
> That’s true :) 
> But how to know that two radio buttons are close one to the other ?

Right.  That's the reason radio button groups are, AFAIK, always
implemented as widgets.

>
>>  4. Usually there's a way to specify how to distribute the
>> width/height between layouts and widgets inside a layout (usually
>> based on a percentage).
>>
> There in spec as well :)
> You can have a look at:
> add:origin:corner:offsetOrigin:offsetCorner:
>
Hmm...couldn't figure out the logic.  Though it seems simple when
looking at the code :-)
The best case I could get was a button with fixed width but a variable
height.  Could you please help me out a bit here?

-- 
Bahman Movaqar  (http://BahmanM.com)

ERP Evaluation, Implementation & Deployment Consultant
PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)




signature.asc
Description: OpenPGP digital signature

[Pharo-users] Pharo Source Code

[Bahman Movaqar]

Could someone please point me to the non-Smalltalk source code for Pharo
--I searched the website but couldn't find anything?

TIA,

-- 
Bahman Movaqar  (http://BahmanM.com)

ERP Evaluation, Implementation & Deployment Consultant
PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)



signature.asc
Description: OpenPGP digital signature

Re: [Pharo-users] ImageMorph scaling

[Sean P. DeNigris]

Sean P. DeNigris wrote
> How would I get an ImageMorph to automatically resize inside a Spec UI?

The following must be called /after/ the ImageMorph is added to the
parent...
imageMorph addFlexShell
hResizing: #spaceFill;
vResizing: #spaceFill.

The resizing is a bit slow, but it works. HTH...



-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/ImageMorph-scaling-tp4719248p4721219.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Pharo Source Code

[p...@highoctane.be]

https://github.com/pharo-project/pharo-vm
https://github.com/pharo-project/pharo-core (Smalltalk still)
https://github.com/SquareBracketAssociates

Phil