Just renaming
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send
Any API change ? Or just renaming?
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe f
To avoid confusion with Agile term “Scrum” the library, artifact and
namespaces were renamed to *Citrus* since v3.0.0. Older versions are still
available under the old name *Scrum*. To migrate to v3.0.0+ replace all
occurrences of *scrum* with *citrus.*
Old artifact name: *org.roman01la/scrum*
We're pleased to release Onyx version 0.8.0, which brings with it
primitives for
automatic state management, failure recovery, windowed computations, and
triggers.
Onyx is a scalable, distributed, fault tolerant, high performance data
processing platform
for handling batch and stre
Hello there!
https://github.com/Frozenlock/historian
One of the big sales pitch of React.js (and cljs immutable data structure)
is how it enables us to easily make 'undo'.
Here's a library that does just that.
You tell it which atom(s) you want to be able to undo/redo and it will keep
track o
On Wed, Apr 2, 2014 at 3:42 AM, rlewczuk wrote:
>
> First one is about object created by (om/build ...) - in all tutorials
> these objects are always created on the fly in (render ...) functions. So
> if some component disappears from view for some time, it loses its state.
> This might be the ca
Hi,
Thank you for all answers, as I did my homework (reading overview sent by
Jeff and applying Luca's suggestions), things have improved quite a bit.
Yet there are still some things I'm not fully grasping, so I have more
questions :)
First one is about object created by (om/build ...) - in a
Hi Rle,
I'm a clojurescript / om newbie too. I'll try to answer to the best of my
knowledge and maybe someone else can improve this first guess.
Il giorno giovedì 27 marzo 2014 09:20:41 UTC+1, rlewczuk ha scritto:
>
> Hi,
>
> After playing a bit with om, I'm somewhat confused about state maintai
There is some explanation about component local state in the documentation
here:
https://github.com/swannodette/om/wiki/Conceptual-overview
UI components will often have transient state that really doesn't make
sense to expose externally. For example the characters in an input as
someone is t
Hi,
After playing a bit with om, I'm somewhat confused about state maintaining
possibilities it offers. There is global application state and local
component state. I have some doubts about using local state as it seems to
lead to troubles as soon as code grows a bit (I'm thinking about
trad
Thanks - I'd kind-of worked that out after posting (with the aid of a walk
outside, and a beer!) but it's nice to know I'm on the right track.
On 5 Jan 2014 19:05, "Stuart Sierra" wrote:
> Hi Korny,
>
> Components implementing protocols can provide different implementations.
> In the Database exa
Hi Korny,
Components implementing protocols can provide different implementations. In
the Database example, both the "real" component and the "stub" component
would have to implement some common protocol that defines the "primitive"
capabilities needed by the application.
Traditional update-in-pl
Hi - I've been playing with this and I'm a little confused.
I can understand how you use the library to pass around stateful
components, and to start/stop them and wire them up etc.
But I'm not sure I see how it should be used for more general dependency
injection.
I'll pick a concrete example -
On Thu Nov 21 07:14:16 2013, Stuart Sierra wrote:
On Thursday, November 21, 2013 7:22:10 AM UTC-5, abp wrote:
> Why do you prefer declaring dependencies between
> components of a system explicitly instead of using
> prismatics Graph?
'Graph' by itself does not preserve the dependency
relationshi
On Thursday, November 21, 2013 7:22:10 AM UTC-5, abp wrote:
> Why do you prefer declaring dependencies between
> components of a system explicitly instead of using
> prismatics Graph?
'Graph' by itself does not preserve the dependency
relationships after constructing the map. But the two
approache
Hi, great work indeed.
One question though: Why do you prefer declaring dependencies between
components of a system explicitly instead of using prismatics Graph?
On Thursday, November 21, 2013 3:01:19 AM UTC+1, Stuart Sierra wrote:
>
> This is a small library/framework I've been working on for a
This is simple brilliant... The approach proposed and the component
"framework" implementing it finally solves the issue with the "necessary
evil" (start/stop interactions with statefull components in any bigger
Clojure app) by cleverly taking only the best ideas (like using inferred
dependency
This is a small library/framework I've been working on for a few months.
https://github.com/stuartsierra/component
I use this to manage runtime state in combination with my "reloaded"
workflow using tools.namespace.[1]
I've started using this on some personal and professional projects and it
see
Hi,
I'm dealing with a problem where numerical data needs to be read through a
serial port, then rendered to a chart and displayed to the user. The user
has to be able to export the chart, and control whether or not reading is
actually being done. In addition to this, the chart needs to reflect
:
> Hi,
>
> Are there any clojurescript libraries / frameworks for mvc, or state
> management ?
>
> I have come across clojurescript one and waltz.
>
> Thanks,
> Murtaza
--
You received this message because you are subscribed to the Google
Groups "Clojure" gro
Hi,
Are there any clojurescript libraries / frameworks for mvc, or state
management ?
I have come across clojurescript one and waltz.
Thanks,
Murtaza
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email
21 matches
Mail list logo
