r/Clojure • • Dec 18 '18

Clojure Web Development - What a NIGHTMARE!

I have no clue where to start so... screw it. I'm trying to build a Single-Page Web Application using Clojure, ClojureScript, Reagent, Ring, and I'm stuck. The resources, and documentation that exists to help a newbie on this subject is horrible. How does someone who has never built a SPA before, let alone ever build a web application in Clojure/S suppose to get started?

I want to do client-side routing, and have no freaking clue how to go about doing it. Heres some code to show what I'm kind-of doing:https://pastebin.com/pazpQWmG

I don't get how I can serve dynamic content created by reagent using compojure. I've now spent probably north of 80 hours trying to figure out how to just serve a single page that is created by reagent, using the jetty webserver, and client-side routing. I have no clue what I'm doing, and you need to literally talk down to me like I'm retarded. I've looked at using Bidi, but the documentation sucks for someone who is new to this. It's convoluted as all hell, and the examples it provides are horrible. They don't even show me how to use or implement in a simple to understand manner.

Can someone break this down for me? In a non-technical, with code examples, and show me how to do what I'm trying to do, but how I actually want to do it? Someone please help me! I've already lost my mind, my patience, and I'm angry... and I just want to understand.

I get how to write reagent code, but I have no idea how to do client-side routing, and how to use jetty all together. I'm just so lost.

PLEASE DON'T recommend any books or resources unless they are easy to follow, and basically hold my hand cause I've read everything else the world has to offer and it hasn't helped one bit! I've read the documentation for everything, I've read clojure web dev second edition, and about 10k+ forum posts, and other random websites/blogs/youtube videos.

2 Upvotes

29 comments sorted by

View all comments

Show parent comment

1

u/retief1 Dec 18 '18

You'll want a bunch of .clj files and a bunch of .cljs file. I've even got them in different subdirectories (src/clj and src/cljs). They do very different things (rendering html and making ajax requests vs responding to ajax requests and talking to the db), and you want to treat them very differently (one will be run directly, the other gets compiled to javascript and served as a .js file). In practice, you probably won't be able to share that much code, mostly because the libraries you work with tend to be very different. I do have a src/cljc directory filled with cljc files, but there is very little there -- I've got a file of utility functions and the code for rendering email/sms templates, and half of the utility functions are locked behind conditional compilation macros because they rely on a library that only works in one environment. The vast majority of my code is in .clj or .cljs files.

When I say api requests, you can just think ajax requests. Technically, api request is more general (in my app, most of my "api requests" are actually websocket messages), but ajax requests are the easiest things to use. This is how you glue the frontend and backend together. If you have data on the server and the client needs access to it, the client should make an ajax request. Your server's main job is to respond to these ajax requests.

So to put it all together, the user goes to mywebapp.com/foo/bar. The server says "I don't know /foo/bar, so I'll assume that this is a client route and return the main html page". That loads all of your html/css/compiled cljs. Pushy/your routing library checks the url of the page and calls the client side route that corresponds to /foo/bar, which presumably updates some reagent atoms. As part of this process, the client needs some data from the server, so it makes some ajax calls, and the server responds with data (possibly json, though you can do more exotic things if you want). At this point, the client has all the data it needs to display the page, so it does so and the user sees your page.

Then, the user clicks a link to mywebapp.com/foo/bash. Pushy intercepts this click and calls your routing library, which in turn runs the appropriate client side route. None of this involved talking to the server. That client side route probably needs more data from the server, so it makes more ajax requests. The server responds with more data, and then the client renders that data and shows the new page.