Open zot opened 7 years ago
I have a bit of a fork happening here as well:
https://github.com/chr15m/wisp https://chr15m.github.io/wisp/
Things I've done:
Great, @chr15m I'll check out your fork.
Please feel free to use the Google plus community for announcements or whatever Wisp-related stuff you like!
I made a post about it: https://plus.google.com/111407704672373701301/posts/EuzpZmepFzE?sfc=false
Cool, thanks @zot - hopefully nobody will come to rely on it as I am a relentless project abandoner. :)
I'm sort of the same way unless I'm working with other people :-/
I like to think it's a feature not a bug.
@zot instead of this issue I'd like to have a pointer in the documentation to your fork, maybe in a section called "notable forks"? Could you issue a PR like that so we can close this ticket?
The "UMD-friendly" pull request is at my latest branch position and I don't seem to be able to issue a pull request. Maybe we need to reuse the old request or maybe if you reject/close it I can issue another?
-- Bill
On Tue, Feb 7, 2017 at 9:02 AM Chris McCormick notifications@github.com wrote:
@zot https://github.com/zot instead of this issue I'd like to have a pointer in the documentation to your fork, maybe in a section called "notable forks"? Could you issue a PR like that so we can close this ticket?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Gozala/wisp/issues/150#issuecomment-277917919, or mute the thread https://github.com/notifications/unsubscribe-auth/AABoKS7QPdgNPkletZ_lDPfwebtjqQnKks5raBcRgaJpZM4LJuMv .
@zot if you create a branch off Gozala/master then you can issue a separate PR for the "notable forks" documentation change.
Let's move discussion of the UMD-friendly change to your PR #147.
oh, OK
On Tue, Feb 7, 2017 at 9:50 AM Chris McCormick notifications@github.com wrote:
@zot https://github.com/zot if you create a branch off Gozala/master then you can issue a separate PR for the "notable forks" documentation change.
Let's move discussion of the UMD-friendly change to your PR.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Gozala/wisp/issues/150#issuecomment-277925298, or mute the thread https://github.com/notifications/unsubscribe-auth/AABoKfjLjiFLtSnGVOQZ_bEzWarpX04Oks5raCIxgaJpZM4LJuMv .
@chr15m @zot I know that this project is long since put to rest, but I'm wondering if either of you know of a way to load a .wisp
file in the repl, so that it's functions can be executed interactively?
Also, now that Google+ is gone, is there another space for folks exploring wisp...or am I the only one around?
I haven't touched Wisp in a loooooong time -- I don't remember anything about getting it working. I should really bundle it into my Leisure project instead of Lispyscript...
You might be the only one around, I'm not sure. Personally I like Wisp as a super light-weight Clojure.
@eli-oat you can (require)
a file from the repl. Imagine you have a file called bloop.wisp
with the following contents:
(defn bleep []
(console.log "bleep"))
You can then require and use it as follows:
=> (def bloop (require "./bloop"))
=> (.bleep bloop)
bleep
Hopefully this answers your question.
You might be the only one around, I'm not sure. Personally I like Wisp as a super light-weight Clojure.
@zot I discovered wisp a few weeks ago and have sort of fallen in love. I like cljs a lot, but this is so much leaner. Great for toy projects
@chr15m thanks! I think that was what I was looking for!
For all it's worth, I've made a fork of my own a while ago… I've been committing fixes there occasionally, mostly to fix bugs I encountered and to reduce discrepancies with Clojure.
@LeXofLeviafan this is great. You've fixed a ton of stuff. Can I get a PR to merge your changes back in?
@chr15m You probably don't actually need my personal input to do that (at least the previous PR with my commits was made by someone else). Still, here you go.
Thanks for the PR @LeXofLeviafan - merged.
For anyone interested, we're maintaining a fork of Wisp, here.
We also have a Google Plus Community. There's even a post! It's on a Wisp pattern package I wrote, that provides lens-like pattern functions.