Wisp Forks

[zot]

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.

[chr15m]

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:

• Merged some of the PRs that look sensible.
• Compiled an easily downloadable, minified version people can use in their browser.
• Tried to make the introduction and interactive repl friendlier.

[zot]

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!

[zot]

I made a post about it: https://plus.google.com/111407704672373701301/posts/EuzpZmepFzE?sfc=false

[chr15m]

Cool, thanks @zot - hopefully nobody will come to rely on it as I am a relentless project abandoner. :)

[zot]

I'm sort of the same way unless I'm working with other people :-/

[chr15m]

I like to think it's a feature not a bug.

[chr15m]

@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?

[zot]

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 ***@***.***> 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 <#150 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABoKS7QPdgNPkletZ_lDPfwebtjqQnKks5raBcRgaJpZM4LJuMv> .

[chr15m]

@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.

[zot]

oh, OK

…

On Tue, Feb 7, 2017 at 9:50 AM Chris McCormick ***@***.***> 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 <#150 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABoKfjLjiFLtSnGVOQZ_bEzWarpX04Oks5raCIxgaJpZM4LJuMv> .

[eli-oat]

@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?

[zot]

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.

[chr15m]

@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.

[eli-oat]

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!