GithubHelp home page GithubHelp logo

ingesolvoll / kee-frame-sample Goto Github PK

View Code? Open in Web Editor NEW
19.0 4.0 6.0 235 KB

Demo application to show off features of kee-frame

Home Page: https://github.com/ingesolvoll/kee-frame

Clojure 96.29% HTML 0.40% CSS 3.31%
reagent re-frame clojurescript keechma

kee-frame-sample's People

Contributors

brjann avatar ingesolvoll avatar jjunior130 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

kee-frame-sample's Issues

Outdated README

Figwheel seems to have been removed in this commit 313352e
but it's still mentionned in the README

And lein cljsbuild once min seems broken too.

ctjhoa@t490 ~/perso/kee-frame-sample (git)-[master] % lein cljsbuild once min
WARNING: no :cljsbuild entry found in project definition.
--------------------------------------------------------------------------------
WARNING: your :cljsbuild configuration is in a deprecated format.  It has been
automatically converted it to the new format, which will be printed below.
It is recommended that you update your :cljsbuild configuration ASAP.
--------------------------------------------------------------------------------
:cljsbuild
{:builds []}
--------------------------------------------------------------------------------
See https://github.com/emezeske/lein-cljsbuild/blob/master/README.md
for details on the new format.
--------------------------------------------------------------------------------
java.lang.Exception: Unknown build identifier: min
 at leiningen.cljsbuild$run_compiler.invokeStatic (cljsbuild.clj:84)
    leiningen.cljsbuild$run_compiler.invoke (cljsbuild.clj:81)
    leiningen.cljsbuild$once.invokeStatic (cljsbuild.clj:189)
    leiningen.cljsbuild$once.invoke (cljsbuild.clj:186)
    leiningen.cljsbuild$cljsbuild.invokeStatic (cljsbuild.clj:260)
    leiningen.cljsbuild$cljsbuild.doInvoke (cljsbuild.clj:249)
    clojure.lang.RestFn.applyTo (RestFn.java:142)
    clojure.lang.Var.applyTo (Var.java:705)
    clojure.core$apply.invokeStatic (core.clj:669)
    clojure.core$apply.invoke (core.clj:662)
    leiningen.core.main$partial_task$fn__7334.doInvoke (main.clj:284)
    clojure.lang.RestFn.applyTo (RestFn.java:139)
    clojure.lang.AFunction$1.doInvoke (AFunction.java:31)
    clojure.lang.RestFn.applyTo (RestFn.java:137)
    clojure.core$apply.invokeStatic (core.clj:669)
    clojure.core$apply.invoke (core.clj:662)
    leiningen.core.main$apply_task.invokeStatic (main.clj:334)
    leiningen.core.main$apply_task.invoke (main.clj:320)
    leiningen.core.main$resolve_and_apply.invokeStatic (main.clj:343)
    leiningen.core.main$resolve_and_apply.invoke (main.clj:336)
    leiningen.core.main$_main$fn__7423.invoke (main.clj:453)
    leiningen.core.main$_main.invokeStatic (main.clj:442)
    leiningen.core.main$_main.doInvoke (main.clj:439)
    clojure.lang.RestFn.applyTo (RestFn.java:137)
    clojure.lang.Var.applyTo (Var.java:705)
    clojure.core$apply.invokeStatic (core.clj:667)
    clojure.main$main_opt.invokeStatic (main.clj:514)
    clojure.main$main_opt.invoke (main.clj:510)
    clojure.main$main.invokeStatic (main.clj:664)
    clojure.main$main.doInvoke (main.clj:616)
    clojure.lang.RestFn.applyTo (RestFn.java:137)
    clojure.lang.Var.applyTo (Var.java:705)
    clojure.main.main (main.java:40)

Can you update the README to provide clear guidance?

FSM: stop/start behaviour clarification

Hi.

When stopping and starting FSMs, shouldn't the FSM state be restarted according to the :start directive?

Example:

(require '[kee-frame.fsm.alpha :as fsm])

(def my-http-request-fsm
   {:id    :my-http-request
    :start ::loading
    :stop  ::loaded
    :fsm   {::loading        {[::fsm/on-enter]      {:dispatch [[:contact-the-server]]}
                              [:server-responded]   {:to ::loaded}
                              [:default-on-failure] {:to ::loading-failed}}
            ::loading-failed {[::fsm/timeout 10000] {:to ::loading}}}})

If I dispatch ::fsm/start my-http-request-fsm again, shouldn't :state become ::loading?

TBH, I have not tried this with actual :stop condition as I'm stopping my FSM manually. But I'm seeking to essentially reset the FSM via :start/:stop, and if I dspatch :stop and then :start, the :state remains whatever it was on when :stop was dispatched.

I was expecting state to be reset on :stop, but maybe I shouldn't?

better examples in readme

Why isn't the example for switch-route something like this?

[k/switch-route (comp :name :data)
    :index  [:div "index :)"]
    :about  [:div "About"]
    nil     [:div "loading..."]]

I also think that having a shadow example would be good

(defn init []
  (k/start! {:debug?         true
             :routes         [["/" :index] ["/menu" :menu]]
             :root-component [main-panel]}))

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.