I want to integrate reflex-dom as a frontend project in my monorepo. Since I have to use Obelisk/Reflex-Platform, I have 2 nixpkgs set in my entire project. What I want to have is only 1 nixpkgs (20.09) and then build reflex/reflex-dom using the existence ghcjs in 20.09.
I have heard that there is a little changes made by reflex-platform wrt to GHCJS. Iirc it is regarding JsString. Is that all?
if frontend == ghcjs, no - you are better off staying with reflex-platform. if frontend == ghc (jsaddle-warp or gtk+), then just use the one in nixpkgs.
if frontend == ghcjs, no - you are better off staying with reflex-platform. if frontend == ghc (jsaddle-warp or gtk+), then just use the one in nixpkgs.
Yeah after diving into obelisk + reflex-platform, I'll stick to them. It's too much goodies in there that are worthy for the project.
There is also https://github.com/srid/reflex-stone if you want only "ob run" (and full build) workflow from obelisk, but not the rest including backend.
Uh, can you Rizary elaborate on the JupyterWith thing? You mean Jupyter Notebooks, what is your project doing? (sounds veery interesting)
It's an old project. I attempt to integrate JupyterWith with obelisk platform. So we can code reflex-dom inside jupyter (the first aim is that) also include hasktorch in it.
My first idea is I want to create minimum example (like the one in pytorch tutorial) that creates flask based app with pytorch. Instead, I want to have fullstack haskell with hasktorch in it. my current state is only able to run jupyterWith, but I haven't got the time to continue developing obelisk + hasktorch part.
I want to integrate reflex-dom as a frontend project in my monorepo. Since I have to use Obelisk/Reflex-Platform, I have 2 nixpkgs set in my entire project. What I want to have is only 1 nixpkgs (20.09) and then build reflex/reflex-dom using the existence ghcjs in 20.09.
I have heard that there is a little changes made by reflex-platform wrt to GHCJS. Iirc it is regarding
JsString. Is that all?if frontend == ghcjs, no - you are better off staying with reflex-platform. if frontend == ghc (jsaddle-warp or gtk+), then just use the one in nixpkgs.
kais based on the latterSridhar Ratnakumar said:
Yeah after diving into obelisk + reflex-platform, I'll stick to them. It's too much goodies in there that are worthy for the project.
There is also https://github.com/srid/reflex-stone if you want only "ob run" (and full build) workflow from obelisk, but not the rest including backend.
I've seen that and also your rhyolite template (I also have project with JupyterWith combined with rhyolite using the same way you did).
Uh, can you @Rizary elaborate on the
JupyterWiththing? You mean Jupyter Notebooks, what is your project doing? (sounds veery interesting)Matthias Putz said:
It's an old project. I attempt to integrate
JupyterWithwith obelisk platform. So we can code reflex-dom inside jupyter (the first aim is that) also include hasktorch in it.My first idea is I want to create minimum example (like the one in pytorch tutorial) that creates flask based app with pytorch. Instead, I want to have fullstack haskell with hasktorch in it. my current state is only able to run jupyterWith, but I haven't got the time to continue developing obelisk + hasktorch part.
jupyterWithrefers to tweag's project here https://github.com/tweag/jupyterWith