On 15 Nov 2014, at 10:41 , stepharo steph...@free.fr wrote:
initializePresenter
Used to specify the subwidgets, and/or to bind them together
By default, do not do anything
extentHolder whenChangedDo: [:ex |
self widget ifNotNil: [:widget |
(widget respondsTo:
On 15 Nov 2014, at 10:49 , stepharo steph...@free.fr wrote:
I get dizzy (may be time to go to sleep) but I wonder
why do we need to check first the the window changed and after that it got
closed?
Especially since whenWindowChanged: presuppose that we have access to window.
Am I missing
On 17 November 2014 11:38, Henrik Johansen henrik.s.johan...@veloxit.no
wrote:
On 15 Nov 2014, at 10:41 , stepharo steph...@free.fr wrote:
initializePresenter
Used to specify the subwidgets, and/or to bind them together
By default, do not do anything
extentHolder
On 17 November 2014 12:08, Henrik Johansen henrik.s.johan...@veloxit.no
wrote:
On 15 Nov 2014, at 10:49 , stepharo steph...@free.fr wrote:
I get dizzy (may be time to go to sleep) but I wonder
why do we need to check first the the window changed and after that it got
closed?
Especially
Hi Henrik
Thanks for your point :)
I agree with you. Esteban prefered the current solution because of law
of demeter but I do not think that this is good.
So we will rewrite all these methods.
If you want to help you are welcome.
Stef
On 14/11/14 16:25, Henrik Johansen wrote:
On 14 Nov
initializePresenter
Used to specify the subwidgets, and/or to bind them together
By default, do not do anything
extentHolder whenChangedDo: [:ex |
self widget ifNotNil: [:widget |
(widget respondsTo: #extent:)
ifTrue: [ widget extent: ex ]]].
may
I get dizzy (may be time to go to sleep) but I wonder
why do we need to check first the the window changed and after that it
got closed?
Especially since whenWindowChanged: presuppose that we have access to
window.
Am I missing something?
self whenWindowChanged: [ :w |
w whenClosedDo:
On 15 November 2014 22:49, stepharo steph...@free.fr wrote:
I get dizzy (may be time to go to sleep) but I wonder
why do we need to check first the the window changed and after that it got
closed?
Especially since whenWindowChanged: presuppose that we have access to
window.
Am I missing
Hi guys
(this is stef hijacking the account of alain).
I was puzzled by the fact that each value holder has its own announcer.
I’m trying to understand the pros and cons.
Stef
Announcer allInstances size
5417
Announcer allInstances collect: #numberOfSubscriptions #(0 1 2 3 51 0 16 1 16
In VW the dependency transformer (which is the equivalent to Announcer)
is held in the dependent list.
So may be this is similar.
Stef
Hi guys
(this is stef hijacking the account of alain).
I was puzzled by the fact that each value holder has its own announcer.
I’m trying to understand the
This is something I'm interested in too. I thought that this was a design
decision between a) and b)
a) you can have single announcer to whom you would subscribe and then
manually filter each fired event whether it something that interests the
listener
b) subscribe directly to the object you're
This is something I'm interested in too. I thought that this was a
design decision between a) and b)
a) you can have single announcer to whom you would subscribe and then
manually filter each fired event whether it something that interests
the listener
b) subscribe directly to the object
I checked a bit deeper
Nautilus is not implemented in Spec. But senders and implementors are
and they also leak memory. Around 400 Announcers after each
opening and closing.
Now
whenChangedDo: aBlock
| block |
block := [:announcement :ann | aBlock cull: announcement newValue
cull:
On Fri, Nov 14, 2014 at 12:01 PM, stepharo steph...@free.fr wrote:
I checked a bit deeper
Nautilus is not implemented in Spec. But senders and implementors are and
they also leak memory. Around 400 Announcers after each
opening and closing.
Now
whenChangedDo: aBlock
| block |
On 14 Nov 2014, at 12:01 , stepharo steph...@free.fr wrote:
I checked a bit deeper
Nautilus is not implemented in Spec. But senders and implementors are and
they also leak memory. Around 400 Announcers after each
opening and closing.
Now
whenChangedDo: aBlock
| block |
On 14 November 2014 16:25, Henrik Johansen henrik.s.johan...@veloxit.no
wrote:
On 14 Nov 2014, at 12:01 , stepharo steph...@free.fr wrote:
I checked a bit deeper
Nautilus is not implemented in Spec. But senders and implementors are
and they also leak memory. Around 400 Announcers
I agree as well.
Doru
On Fri, Nov 14, 2014 at 4:58 PM, Igor Stasenko siguc...@gmail.com wrote:
On 14 November 2014 16:25, Henrik Johansen henrik.s.johan...@veloxit.no
wrote:
On 14 Nov 2014, at 12:01 , stepharo steph...@free.fr wrote:
I checked a bit deeper
Nautilus is not
17 matches
Mail list logo
