On a related note, there is a lot of sympathy between this line of
thought and event-sourcing/CQRS on the server side. It _completely_
transformed my way of thinking about these problems and how I
implement things but the benefits are huge, including the fact that
time changing is really just
I understand the relationship between state machines and event-log/CQRS. A
program could just translate the UI events into events stored in an event log,
and let them be consumed continually by a state machine. You would basically
reduce the events log using the state machine as a reduction
cljs.closure/build is failing unless I turn off *analyze-deps*. Is this a
normal behavior?
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
ClojureScript group.
To
Ok, you talk about logic being on the server and the client. I thought you
were saying that related logic was spread across different points from an
architecture point of view, like some in the event-log consumers, some
in the components, some in the request handlers etc. (these are just
Clojure 1.7.0-beta3 is now available.
Try it via
- Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.7.0-beta3/
- Leiningen: [org.clojure/clojure 1.7.0-beta3]
Additional enhancements to new features since 1.7.0-beta2:
1) CLJ-1728 - `source` fn now works for vars in cljc files
2)
On Wednesday, May 13, 2015 at 2:50:39 PM UTC+1, John Chijioke wrote:
cljs.closure/build is failing unless I turn off *analyze-deps*. Is this a
normal behavior?
Given a source-dir with options like {:optimizations :none :libs [generated-js]
:output-to bar.deps} it fails when it tries to parse
So you are saying on any single change to a source file a clean must happen
before build can succeed?
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
ClojureScript
Looks good for current project. Project compiles and runs with clojure
1.7.0-beta3, clojurescript 0.0-3269, figwheel 0.3.1 + core.async
core.match + om + ...
Figwheel repl still works from within Cursive.
Thanks,
Andrew
--
Note that posts from new members are moderated - please be patient
No, I am not saying that. I'm just saying what you are specifically trying
to do is not something the ClojureScript compiler has ever supported.
On Wed, May 13, 2015 at 10:31 AM, John Chijioke johnben...@gmail.com
wrote:
So you are saying on any single change to a source file a clean must
On Wed, May 13, 2015 at 2:15 PM, John Chijioke Umeasiegbu
johnben...@gmail.com wrote:
Okay. Thanks for clarifying. But I still have a number of questions on my
mind.
First there are cljs sources in generated-js copied over by source-on-disk
or so.
ClojureScript sources are copied over to
In addition to the Horrocks book, take a look at Practical UML Statecharts in
C / C++.
This book also describes Harel Statecharts, but goes into much more depth about
how one can implement them on embedded systems.
I've been experimenting with using Harel Statecharts as an architecture for
Oliver, I might be interested. Contact me at my first name at my first
name + 'mail.com'.
Cheers,
Akiva
Oliver George mailto:oli...@condense.com.au
March 17, 2015 at 5:05 PMvia Postbox
https://www.postbox-inc.com/?utm_source=emailutm_medium=sumlinkutm_campaign=reach
Thanks Marc
--
I just watched the video. Wow. Having a live statechart is even better than
what I imagined. It reminds me somehow of the NoFlo JavaScript project. This
would be an awesome lib to have... (Am I suggesting you should open source this
statechart stuff ? :D). Seriously thank you for the pointers.
I have a question for you Kevin : when you modeled your logic with a state
machine, were you able to unit test it outside of the browser ? (Sorry if the
answer is in the video, I haven't watched it yet)
Le 14 mai 2015 à 00:00, Kevin Lynagh ke...@keminglabs.com a écrit :
In addition to the
Thanks, David. That could be the problem. When using :compile :simple, are
externs ignored?
Cheers,
Jamie
On May 13, 2015, at 12:27 PM, David Nolen dnolen.li...@gmail.com wrote:
There is no guarantee that using the library itself as the extern will work.
In fact you should be surprised if
Hoping someone might have some insight that can help with this.
I'm using Twitters Typehead (0.9.3, before its big rework) in a
re-frame/reagent app.
Below is a snippet that works fine when :compile :simple is used, but fails
when :compile :advanced is used. I'm using the typeahead.js and
There is no guarantee that using the library itself as the extern will
work. In fact you should be surprised if it works unless the library follow
strict conventions.
David
On Wed, May 13, 2015 at 12:23 PM, Jamie Orchard-Hays jamie...@gmail.com
wrote:
Hoping someone might have some insight
As far as I know, in compile simple identifiers are not renamed, so externs
are not needed.
On Wed, 13 May 2015 17:28 Jamie Orchard-Hays jamie...@gmail.com wrote:
Thanks, David. That could be the problem. When using :compile :simple, are
externs ignored?
Cheers,
Jamie
On May 13, 2015, at
Finite state machines are a useful modeling tool, but when implemented in
code they can involve a lot of boilerplate and complexity. These days I
prefer Rx-like paradigms for sophisticated handling of asynchronous events.
e
On Wed, May 13, 2015 at 5:54 AM, Khalid Jebbari khalid.jebb...@gmail.com
Yup. I realized right after I sent the email that only :advanced needs externs.
On May 13, 2015, at 12:33 PM, Daniel Kersten dkers...@gmail.com wrote:
As far as I know, in compile simple identifiers are not renamed, so externs
are not needed.
On Wed, 13 May 2015 17:28 Jamie Orchard-Hays
Okay. Thanks for clarifying. But I still have a number of questions on my mind.First there are cljs sources in generated-js copied over by source-on-disk or so.Second if the compiler is not okay with generated-js
21 matches
Mail list logo
