BTW, I have published an updated version of JNIPort which partly resolves the
performance issue caused by using #become:.
Joachim
--
My OpenPGP Key: 29F88108 available from hkp://wwwkeys.de.pgp.net
Thanks guys!
On Apr 7, 2014 4:36 PM, "Camille Teruel" wrote:
>
> On 7 avr. 2014, at 16:31, Clément Bera wrote:
>
> Hello,
>
> I do not like 'Smalltalk evaluate:' either.
>
> One solution is to do 'self class compiler evaluate:'.
>
>
> Yes IMO, calling #compiler on a class is the best solution si
2014-04-07 17:58 GMT+02:00 Thomas Bany :
> Okey so I only needed to select a directory and needed to shrink the size
> of the widget anyway. So I opted for the sublass solution, got rid of the
> file pane and added an action block on the #ok method.
>
>
> 2014-04-07 16:12 GMT+02:00 Thomas Bany :
>
Hello,
Can you tell me the error message you get when executing from a terminal?
Also I am curious about the output you get from your latest VM with this
command:
ldd -v bin/pharo
Thanks
Hilaire
Le 07/04/2014 10:01, Bernat Romagosa a écrit :
> Very nice, Hilarie!
>
> Just FYI, I had
Okey so I only needed to select a directory and needed to shrink the size
of the widget anyway. So I opted for the sublass solution, got rid of the
file pane and added an action block on the #ok method.
2014-04-07 16:12 GMT+02:00 Thomas Bany :
> Hi !
>
> I'm trying to fit a GUI in full screen mo
Ben
On 07 Apr 2014, at 12:17, MartinW wrote:
> Benjamin Van Ryseghem (Pharo) wrote
>> Out of this thread, I have made this post:
>> http://spec.st/docs/drag_n_drop/
>> With a small change in the Spec code base (to not sort by default, but
>> only when a sorting block is specified),
>> it gives
Hi
I think this is spec related.
How can I set a ballonText on aTreeNode?
I was expecting something like:
tree childrenBlock: [ :anObject | self childrenFor: anObject
];
displayBlock: [ :anObject | self labelFor:
anObject ];
On 7 avr. 2014, at 16:31, Clément Bera wrote:
> Hello,
>
> I do not like 'Smalltalk evaluate:' either.
>
> One solution is to do 'self class compiler evaluate:'.
Yes IMO, calling #compiler on a class is the best solution since it returns a
compiler with the options that the class defines.
Hello,
I do not like 'Smalltalk evaluate:' either.
One solution is to do 'self class compiler evaluate:'.
2014-04-07 5:02 GMT-07:00 Sergi Reyner :
> 2014-04-07 11:51 GMT+01:00 Marcus Denker :
>
> In 4.0, we will remove the old compiler and then we can see how to make
>> the API perfect.
>>
>
>
On Mon, Apr 7, 2014 at 8:43 AM, Roelof Wobben wrote:
> I wonder if there is a free book with a lot of exercises so I can practice
> and learn a lot about Smalltalk.
You can learn from Pharo By Example http://pharobyexample.org/
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success i
Hi !
I'm trying to fit a GUI in full screen mode, that uses a FileDialogWindow
at some point.
I'm able to recover the answer from FileDialogWindow when I it is opened
modaly. However, since I would like to open it fullscreen with the selector
#openFullScreen, the calling block does not wait and i
Hi Joachim,
Thanks for the explanations. It looks complicated but I am very happy it is
possible!
I will give a try next week and get back to you.
Cheers,
Doru
On Sat, Apr 5, 2014 at 2:32 PM, Joachim Geidel wrote:
> Am 31.03.2014 um 21:25 schrieb Tudor Girba :
> > Now, the next question. I s
2014-04-07 11:51 GMT+01:00 Marcus Denker :
> In 4.0, we will remove the old compiler and then we can see how to make
> the API perfect.
>
Will it be able to decompile by then?
Cheers,
Sergi
Jean Baptiste Arnaud schreef op
7-4-2014 8:58:
Steph keeps some treasure:
http://stephane.ducasse.free.fr/FreeBooks.html
On 07 Apr 2014, at 08:43, Roelof Wobben
wrote:
On 07 Apr 2014, at 12:15, Andre Hora wrote:
> Hello,
>
> Recently in Pharo there was some tendency to replace Compiler evaluate: by
> Smalltalk evaluate:.
> Stef does not seem to agree with that.
> My question is which one is the correct convention to call #evaluate: ?
>
The problem is that
Benjamin Van Ryseghem (Pharo) wrote
> Out of this thread, I have made this post:
> http://spec.st/docs/drag_n_drop/
> With a small change in the Spec code base (to not sort by default, but
> only when a sorting block is specified),
> it gives an example of how to do what you want :)
Cool. Thank yo
Hello,
Recently in Pharo there was some tendency to replace Compiler evaluate: by
Smalltalk evaluate:.
Stef does not seem to agree with that.
My question is which one is the correct convention to call #evaluate: ?
thanks in advance,
--
Andre Hora
Sorry for the delay, I turn off my emails during the week end :)
Out of this thread, I have made this post: http://spec.st/docs/drag_n_drop/
With a small change in the Spec code base (to not sort by default, but only
when a sorting block is specified),
it gives an example of how to do what you wa
Very nice, Hilarie!
Just FYI, I had to replace the shipped vm and plugins by the latest ones to
get it to work on my Debian Wheezy machine.
Congrats!
2014-04-05 18:20 GMT+02:00 Hilaire Fernandes :
> Hello,
>
> For those who want to give a try to work in progress iStoa on Linux, an
> Interactiv
19 matches
Mail list logo