Hi Nicolai,
On Aug 19, 2014, at 11:58 AM, Nicolai Hess wrote:
> Thank you eliot,
>
>
> 2014-08-19 7:29 GMT+02:00 Eliot Miranda :
>> Hi Nicolai,
>>
>> the stack starts as deep as the method's number of temporaries,
>
> ok,
>
>> which is the sum of the number of arguments
>
> ok,
>
Ronie Salgado wrote
> For Mac OS X, I don't have one for testing. But Alex is going allow me to
> borrow one for some time. So be patience.
Any progress? I can help with testing...
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Initial-versions-for-OSWindow-and-Woden
Hi guille
I was cleaning the event and we were slow to integrate the refactoring
we did with igor. And now this is obsolete
because there is OSWindow coming.
We are about to integrate OSWindow code and soon or later we will have
probably to change the processEvent: code.
Stef
On 18/8/14 17:
for taking a look at the past the images are still available and will remain
like that.
what will not be available anymore are just the zeroconf scripts.
And yes, cleaning time to time is a good idea, IMO. Otherwise we will end with
infinite listings of things that no one use, left there just
Is removing history actually a good thing?
Are those conveniences creating any actual problem by standing there?
What if someone want to take a look at the past?
On Aug 19, 2014, at 6:17 AM, Esteban Lorenzano wrote:
> Hi,
>
> right now there zeroconf scripts for pharo 1.2-1.4 that I do n
good idea.
We were discussing with alain about handles and handle because in bloc
he is used wantsMouseDown instead handlesMouseDown.
Stef
On 19/8/14 09:17, Ben Coman wrote:
It took a bit of hunting around to discover how to use the custom
hooks for mouse event, and I needed to make some exa
Torsten Bergmann wrote
> I personally would keep ValueHolder as it is a well known concept
Although it's extremely corollary to the purpose of this thread, since it
keeps coming up, I just want to remind that the point of the original
ValueHolder-rename discussion (in which no one said "let's keep
Hi Ben,
first: I think it is not a secret that we appreciate any work you did so far
for Pharo and our community. Still I do not like the mail you have written,
because:
- It gives a false impression of the community itself and leaves us back
once more with questions (especially as most o
On Tue, Aug 19, 2014 at 1:24 PM, Esteban Lorenzano
wrote:
> is different problem.
> most probably we will not have zeroconf for centos anytime soon.
> but we will have builds for centos compatible vms (downloadable, but not
> zercoconf), that’s for sure :)
>
> (yeah, I know, I promised that to yo
Hoi Eliot--
> [great explanation of method/block stack depth]
Cool, is this viewable from an in-system tool somewhere (even if
only a "documentation" method in a class browser)?
thanks,
-C
--
Craig Latta
netjam.org
+31 6 2757 7177 (SMS ok)
+ 1 415 287 3547 (no SMS)
is different problem.
most probably we will not have zeroconf for centos anytime soon.
but we will have builds for centos compatible vms (downloadable, but not
zercoconf), that’s for sure :)
(yeah, I know, I promised that to you like months ago, but I’ve been busy. I
can just say the issue it
Centos ?
Le 19 août 2014 13:19, "Esteban Lorenzano" a écrit :
> ah, I also will add zeroconf for pharo-minimal :P
>
> On 19 Aug 2014, at 11:37, Yuriy Tymchuk wrote:
>
> > +1
> >
> > On 19 Aug 2014, at 11:16, Max Leske wrote:
> >
> >> I don’t need them.
> >>
> >> On 19.08.2014, at 11:17, Esteban
ah, I also will add zeroconf for pharo-minimal :P
On 19 Aug 2014, at 11:37, Yuriy Tymchuk wrote:
> +1
>
> On 19 Aug 2014, at 11:16, Max Leske wrote:
>
>> I don’t need them.
>>
>> On 19.08.2014, at 11:17, Esteban Lorenzano wrote:
>>
>>> Hi,
>>>
>>> right now there zeroconf scripts for ph
+100
On Tue, Aug 19, 2014 at 11:37 AM, Yuriy Tymchuk
wrote:
> +1
>
> On 19 Aug 2014, at 11:16, Max Leske wrote:
>
> > I don’t need them.
> >
> > On 19.08.2014, at 11:17, Esteban Lorenzano wrote:
> >
> >> Hi,
> >>
> >> right now there zeroconf scripts for pharo 1.2-1.4 that I do not think
> a
Thank you eliot,
2014-08-19 7:29 GMT+02:00 Eliot Miranda :
> Hi Nicolai,
>
> the stack starts as deep as the method's number of temporaries,
ok,
> which is the sum of the number of arguments
ok,
> plus the number of temporary variables that can exist in the stack
ok (what does "ca
+1
On 19 Aug 2014, at 11:16, Max Leske wrote:
> I don’t need them.
>
> On 19.08.2014, at 11:17, Esteban Lorenzano wrote:
>
>> Hi,
>>
>> right now there zeroconf scripts for pharo 1.2-1.4 that I do not think
>> anyone is using it.
>> Can I remove them?
>>
>> cheers,
>> Esteban
>
>
I don’t need them.
On 19.08.2014, at 11:17, Esteban Lorenzano wrote:
> Hi,
>
> right now there zeroconf scripts for pharo 1.2-1.4 that I do not think
> anyone is using it.
> Can I remove them?
>
> cheers,
> Esteban
No great things are achieved without great characters, Stephan has been doing a
great long term effort of maintaining research budgets for Smalltalk and
pushing a viable open source solution for it while the situation was pretty
difficult. Like many of us he has some rough edges to and we should
Hi,
right now there zeroconf scripts for pharo 1.2-1.4 that I do not think anyone
is using it.
Can I remove them?
cheers,
Esteban
It took a bit of hunting around to discover how to use the custom hooks
for mouse event, and I needed to make some examples to prove how it
worked. I thought others might find this interesting. It just outputs
to Transcript for each of the following events. Check the class
comments for usa
ReactiveHolder ?
Phil
On Tue, Aug 19, 2014 at 7:52 AM, Eliot Miranda
wrote:
> It is well to remember Marshall McLuhan, The Medium is the Message, the
> thesis of which is that the nature of any medium has more importance than
> the content if that medium in shaping its effects in the users of
So why not simply ReactiveValueHolder? Who will look for ValueHolder
will find it, who will look for reactive variables will find it and it
well describes the purpose of the class ;-)
Cheers,
-- Pavel
2014-08-19 9:25 GMT+02:00 p...@highoctane.be :
> Sure but the new thing was NewValueHolder.
>
Sure but the new thing was NewValueHolder.
ValueHolder per se doesn't look like impacted.
Well I saw some OldValueHolder proposal but it seemed strange to me.
How would you name the new thing?
Is there some pattern for that kind of case?
Phil
Le 19 août 2014 07:52, "Eliot Miranda" a écrit :
23 matches
Mail list logo
