> Does anyone have similar example using one of the cells
> implementations?
> What would be pros/cons between this and cells approach?
Sorry for a late reply but some of the code didn't exist when you
asked your question. This example can be done using neman cells and
swing wrapper like this: h
gt; (defn- run-observers-till-fixpoint [prev next]
> > (let [observers (next :observers)
> >new-next (run-observers prev next observers)]
> > (if (= new-next next)
> > new-next
> > (recur next new-next) )))
> >
> > While I understand
t) )))
>
> While I understand run-observers, run-observers-till-fixpoint has be
> baffled. Why is this required?
>
> 2009/2/27 Itay Maman
>
>
>
> > Some of the reaction for Waterfront was related to the Application
> > Context Pattern (ACP) - The pattern that a
be
baffled. Why is this required?
2009/2/27 Itay Maman
>
> Some of the reaction for Waterfront was related to the Application
> Context Pattern (ACP) - The pattern that allows most of Waterfront's
> code to be purely functional. I'll try to explain the basics in this
>
Hi,
On Feb 28, 8:32 pm, CuppoJava wrote:
> Hi Itay,
> I'm a little confused about one aspect of the context pattern.
>
> If I understand this write, a listener is a function that takes an old
> context, and returns a new context, BUT it also calls the appropriate
> GUI functions (setText, setSiz
Hi Itay,
I'm a little confused about one aspect of the context pattern.
If I understand this write, a listener is a function that takes an old
context, and returns a new context, BUT it also calls the appropriate
GUI functions (setText, setSize) to ensure that the gui state is
consistent with the
On Feb 27, 5:38 pm, Marko Kocić wrote:
> Interesting approach, nice explained.
>
> Does anyone have similar example using one of the cells
> implementations?
> What would be pros/cons between this and cells approach?
I think that in general, when comparing powerful facilities (such as
the Cont
No" it will immediately return, thus reducing the workload on the
observer invocation loop.
-Itay
> Or am I missing something?
>
> On Feb 27, 1:05 am, Itay Maman wrote:
>
> > Some of the reaction for Waterfront was related to the Application
> > Context Pattern
certain functions and are called when the listened
function is activated. In your experience, is this not a big problem?
Or am I missing something?
On Feb 27, 1:05 am, Itay Maman wrote:
> Some of the reaction for Waterfront was related to the Application
> Context Pattern (ACP) - The patter
> > The cells implementations I've seen posted to this list (in fact pretty
> > much all
> > cells reimplementations) haven't yet approached the sophistication of
> > kenny-cells.
>
> Agreed. And I wrote two of them. They're just toy implementations so
> far.
I'm still not sure how it should l
On Feb 27, 12:59 pm, Andy Chambers
wrote:
> The cells implementations I've seen posted to this list (in fact pretty much
> all
> cells reimplementations) haven't yet approached the sophistication of
> kenny-cells.
Agreed. And I wrote two of them. They're just toy implementations so
far.
-Stu
2009/2/27 Marko Kocić :
>
> Interesting approach, nice explained.
>
> Does anyone have similar example using one of the cells
> implementations?
> What would be pros/cons between this and cells approach?
The cells implementations I've seen posted to this list (in fact pretty much all
cells reimpl
Interesting approach, nice explained.
Does anyone have similar example using one of the cells
implementations?
What would be pros/cons between this and cells approach?
Regards,
Marko Kocić
--~--~-~--~~~---~--~~
You received this message because you are subscribed
for Waterfront was related to the Application
> > Context Pattern (ACP) - The pattern that allows most of Waterfront's
> > code to be purely functional. I'll try to explain the basics in this
> > post. Let me start with the motivation: the reason why FP is at odds
> > with
thanks, this will be very useful for me
On 27 Feb, 09:05, Itay Maman wrote:
> Some of the reaction for Waterfront was related to the Application
> Context Pattern (ACP) - The pattern that allows most of Waterfront's
> code to be purely functional. I'll try to explain the ba
Some of the reaction for Waterfront was related to the Application
Context Pattern (ACP) - The pattern that allows most of Waterfront's
code to be purely functional. I'll try to explain the basics in this
post. Let me start with the motivation: the reason why FP is at odds
with GUI co
16 matches
Mail list logo
