Fork me on GitHub
#fulcro
<
2019-01-07
>
pvillegas1213:01:57

hey @claudiu, how is your router lib different from the dynamic router in the incubator?

claudiu13:01:33

@U6Y72LQ4A Hi. Yep it's a bit different in scope and approach. Currently it's more of a proof of concept, not really production ready.

claudiu13:01:05

Working on a big update to it (changing the interface a bit), and getting close to something more stable and with less dependencies.

claudiu10:01:58

@U6Y72LQ4A Sorry was a bit tired and misread the question. The fulcro router in icubator is mostly around screen routing of components + intial load. What I am going for is an approach to abstract away stuff like: html5 routing, pre-loading route content, page metadata + painless SSR with all of these (on nodejs now). Think the approach in incubator might be better for admin apps... my main focus is to make my life as easy as possible for simple public apps, that need SEO, code splitting, updating html title etc...

angrygami18:01:52

What does this part in documentation exactly means: 2.2.2. Starting the Server Simply start a REPL and use:

angrygami18:01:01

I have at least two options: 1) lein repl in project directory 2) connect to nrepl server that is listening at 9000 port (according to npx shadow-cljs server output)

currentoor19:01:36

lein repl in project directory is for a clojure repl, backend server

currentoor19:01:03

nrepl port 9000 is for a browser connected clojurescript repl

currentoor19:01:36

what exactly do you want to do?

angrygami19:01:21

just go through tutorial

currentoor19:01:42

which tutorial? the book?

angrygami19:01:28

what is "brower connected clojurescript repl"? Can I use this from e.g. Cursive?

currentoor19:01:29

ok, just a suggestion it’s a lot easier to help if you provide more context like i started lein repl in the project directory and got this output

lorem ipsum

currentoor19:01:49

yes you can totally use the browser connected repl from cursive

angrygami19:01:13

I've tried and (fulcro.client.primitives/get-initial-state app.ui.root/Root {}) doesn't work

currentoor19:01:41

> doesn’t work is not at all useful information, that could mean anything

currentoor19:01:11

when you evaluated that code snippet what did output did you get?

angrygami19:01:11

well 🙂 I understand that, just a sec

currentoor19:01:26

have you seen this video?

angrygami19:01:55

This is totally useless I'm sorry

currentoor19:01:08

what is totally useless?

angrygami19:01:35

it doesnt match directory structure I got after lein new fulcro app

angrygami19:01:57

and uses figwheel while latest template rely on shadow-clj

currentoor19:01:16

true it’s a little out of date, the video description says that

currentoor19:01:23

BUT all the main ideas are the same

angrygami19:01:39

🙂 if you know ideas - maybe yes

angrygami19:01:48

but not if you starting from scratch

angrygami19:01:08

the same problem I see in book - which repl should I use?

angrygami19:01:23

it doesn\t help

currentoor19:01:06

which repl depends on if you want a frontend repl or backend repl

angrygami19:01:43

of course 🙂 but doc just says "simply start repl" 🙂

currentoor19:01:09

the readme that gets generated with the project has a lot more

currentoor19:01:13

### Client REPL

The shadow-cljs compiler starts an nREPL. It is configured to start on
port 9000 (in `shadow-cljs.edn`).

In IntelliJ, simply add a *remote* Clojure REPL configuration with
host `localhost` and port `9000`.

If you're using CIDER
see [the Shadow-cljs User's Guide]()
for more information.

### The API Server

The shadow-cljs compiler starts a server for serving development files,
but you usually will not use it. Instead you'll start your own server
that can also serve your application's API.

Start a clj REPL in IntelliJ, or from the command line:

bash $ lein repl user=> (go) ... user=> (restart) ; stop, reload server code, and go again user=> (tools-ns/refresh) ; retry code reload if hot server reload fails
The URL to work on your application is then
[]().

Hot code reload, preloads, and such are all coded into the javascript,
so serving the files from the alternate server is fine.

angrygami18:01:57

and neither of these two work when it comes to this part of doc: dev:cljs.user=> (fulcro.client.primitives/get-initial-state app.ui.root/Root {})

mss19:01:46

hey all, trying to get fulcro-inspect to work inside of an electron app

mss19:01:16

do I just req this namespace in the process with my fulcro app?

mss19:01:24

ya that didn’t work. if anyone has gotten the inspector to work in an electron app, would love some pointers!

currentoor19:01:28

@mss, @wilkerlucio would know more but i see there’s this open issue https://github.com/fulcrologic/fulcro-inspect/issues/43 and it’s not documented in the readme, maybe it’s not ready yet?

👍 5
wilkerlucio01:01:59

its not developed, the issue is mostly to track things I like to do, but no roadmap at this point, it still points to the idea, and if anybody wants to do I can help with some guidance about what needs to be done

wilkerlucio01:01:31

in summary it needs some work in the communication layer, and the client implementation comms using websockets

currentoor19:01:44

i don’t have a need for it right now, but there’s a good chance i’ll need it for our carwash software eventually, maybe i can help then