cl-react icon indicating copy to clipboard operation
cl-react copied to clipboard

Workflow example

Open ebenbruyns opened this issue 4 years ago • 3 comments

Would it be possible to get a workflow example. I've just started tinkering with react and the code repetition is insane. I was wondering how you handle your workflow to get the react code out to nodejs to compile it and deliver it to the browser.

I'm trying to reduce friction as much as possible and I'm struggling to see how this is achieved from the limited documentation you have provided.

ebenbruyns avatar Jan 13 '21 18:01 ebenbruyns

I'm working on a build system / dependency manager for parenscript at https://github.com/BnMcGn/ps-lib-tool

It's not quite ready for public consumption.

Historically, I've been using browserify and custom scripts for my cl-react project.

Ben

On Wed, Jan 13, 2021 at 10:47 AM ebenbruyns [email protected] wrote:

Would it be possible to get a workflow example. I've just started tinkering with react and the code repetition is insane. I was wondering how you handle your workflow to get the react code out to nodejs to compile it and deliver it to the browser.

I'm trying to reduce friction as much as possible and I'm struggling to see how this is achieved from the limited documentation you have provided.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/helmutkian/cl-react/issues/11, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4KLDQO3RKOGDJQ7JDGNZ3SZXTFTANCNFSM4WBHZKCA .

BnMcGn avatar Jan 13 '21 23:01 BnMcGn

Does that mean that you only use lisp to generate some code and package it up with external tools?

While I can appreciate the convenience of using lisp to generate the react output, it seems like a lot of productivity is lost again in the workflow. Unless my understanding is completely wrong.

ebenbruyns avatar Jan 14 '21 00:01 ebenbruyns

It can go either way. You can generate your .js bundle from within lisp, including a (simple) api to call browserify to handle any node library requirements. Or you can make a node library that is written in parenscript and compiled using https://github.com/BnMcGn/sigil . In this case the build process is controlled entirely by npm.

Rumor has it that https://github.com/skeeto/skewer-mode in emacs makes it possible to connect to your browser and interact with the console. You can send live updates of js and parenscript (with an additional minor mode) directly to your browser without reloading the page. Might be what you are looking for.

The parenscript mode seems to live here: https://github.com/johnmastro/trident-mode.el

On Wed, Jan 13, 2021 at 4:38 PM ebenbruyns [email protected] wrote:

Does that mean that you only use lisp to generate some code and package it up with external tools?

While I can appreciate the convenience of using lisp to generate the react output, it seems like a lot of productivity is lost again in the workflow. Unless my understanding is completely wrong.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/helmutkian/cl-react/issues/11#issuecomment-759847722, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4KLDQPSXRMN5KOVUERI3LSZY4H3ANCNFSM4WBHZKCA .

BnMcGn avatar Jan 14 '21 01:01 BnMcGn