- Add dev / relase automatic mapping of datbase connection string, (e.g lein profile)
- Sug-slider
- Confirm messagebox for deleting game
- Add feedback section
- Add image uploads for each game
- Add game details panel on the right of selected game.
- Prevent duplicate game adds ( enforce unique name ) bug
- Merge votes (and other common data) on the server side instead of client to be able to work simultaneously with voting without affect each other
- Söka efter spel
- Add add instant number feedback for slider (prob: was causing atom deref problems)
X Click on entire row to select a game -> Use :attr X Enlarge slider and X Fix sorting... Seems buggy (due to inifinity, div by zero)
https://clojurians-log.clojureverse.org/beginners/2018-04-05
use live db.cloneCollection("ip:port", "collectionname")
use admin db.runCommand({renameCollection:"test.people",to:"world.people"});
Compile project to a jar file via: 'lein uberjar'
Server can then be started via: 'java -jar target/gamelist.jar'
Open a terminal and type lein repl
to start a Clojure REPL
(interactive prompt).
In the REPL, type
(go)
(cljs-repl)
The call to (go)
starts the Figwheel server at port 3449, which takes care of
live reloading ClojureScript code and CSS, and the app server at port 10555
which forwards requests to the http-handler you define.
Running (cljs-repl)
starts the Figwheel ClojureScript REPL. Evaluating
expressions here will only work once you've loaded the page, so the browser can
connect to Figwheel.
When you see the line Successfully compiled "resources/public/app.js" in 21.36 seconds.
, you're ready to go. Browse to http://localhost:10555
and enjoy.
Attention: It is not needed to run lein figwheel
separately. Instead (go)
launches Figwheel directly from the REPL
If all is well you now have a browser window saying 'Hello Chestnut',
and a REPL prompt that looks like cljs.user=>
.
Open resources/public/css/style.css
and change some styling of the
H1 element. Notice how it's updated instantly in the browser.
Open src/cljs/gamelist/core.cljs
, and change dom/h1
to
dom/h2
. As soon as you save the file, your browser is updated.
In the REPL, type
(ns gamelist.core)
(swap! app-state assoc :text "Interactivity FTW")
Notice again how the browser updates.
Lighttable provides a tighter integration for live coding with an inline browser-tab. Rather than evaluating cljs on the command line with the Figwheel REPL, you can evaluate code and preview pages inside Lighttable.
Steps: After running (go)
, open a browser tab in Lighttable. Open a cljs file
from within a project, go to the end of an s-expression and hit Cmd-ENT.
Lighttable will ask you which client to connect. Click 'Connect a client' and
select 'Browser'. Browse to http://localhost:10555
View LT's console to see a Chrome js console.
Hereafter, you can save a file and see changes or evaluate cljs code (without saving a file).
CIDER is able to start both a Clojure and a ClojureScript REPL simultaneously,
so you can interact both with the browser, and with the server. The command to
do this is M-x cider-jack-in-clojurescript
.
We need to tell CIDER how to start a browser-connected Figwheel REPL though, otherwise it will use a JavaScript engine provided by the JVM, and you won't be able to interact with your running app.
Put this in your Emacs configuration (~/.emacs.d/init.el
or ~/.emacs
)
(setq cider-cljs-lein-repl
"(do (user/go)
(user/cljs-repl))")
Now M-x cider-jack-in-clojurescript
(shortcut: C-c M-J
, that's a capital
"J", so Meta-Shift-j
), point your browser at http://localhost:10555
, and
you're good to go.
To run the Clojure tests, use
lein test
To run the Clojurescript you use doo. This can run your tests against a variety of JavaScript implementations, but in the browser and "headless". For example, to test with PhantomJS, use
lein doo phantom
This assumes you have a
Heroku account, have installed the
Heroku toolbelt, and have done a
heroku login
before.
git init
git add -A
git commit
heroku create
git push heroku master:master
heroku open
Heroku uses Foreman to run your
app, which uses the Procfile
in your repository to figure out which
server command to run. Heroku also compiles and runs your code with a
Leiningen "production" profile, instead of "dev". To locally simulate
what Heroku does you can do:
lein with-profile -dev,+production uberjar && foreman start
Now your app is running at http://localhost:5000 in production mode.
Copyright © 2016 FIXME
Distributed under the Eclipse Public License either version 1.0 or (at your option) any later version.
Created with Chestnut 0.17.0 (83a08ccb).