nongrata and clojurescript

[Nick Bauman]

So I've been playing with Clojurescript One to learn how to work with
Clojurescript. Clojurescript One intends to provide an entire
development environment around clojurescript and Clojure web
technologies. If we are truly going to get browserid to work under the
best practices approach of Clojurescript One, it will likely be many
hours of work for configuration, templating, design and testing. It is
quite impressive that I was able to run a REPL and change the look and
feel of a web page _on the fly in the browser._ But it's a ton of
setup.

I think this is too much right out of the gate for the intent of a
browserid implementation in clojure.

I propose we scale down the work in nongrata to just get a simple
browserid implementation working using standard noir web and js
features.

Once we do this, we can then take nongrata into a direction where we
incorporate the approach of Clojurescript One in another meeting. Tom
Marble, for one, will want to have a close eye on the testing part and
how it works with Jenkins / CI so that this wonderful autoci thing he
set up for us continues to work well going forward.

Can I get a vote on this proposal?

+1 +0 -1 for:

"Let's leave Clojurescript out for the first working implementation of
browserid."

Cheers,

Nick

[Tom Marble]

On 05/04/2012 11:41 AM, Nick Bauman wrote:
> Can I get a vote on this proposal?
> +1 +0 -1 for:
> "Let's leave Clojurescript out for the first working implementation of
> browserid."

+1

With the utmost respect for Brian I think we should
really unwind the cljs dependencies for the purpose
of better understanding and integrating Persona.

That being said I am *very* interested in ClojureScript One
(and cljs in general)... there's every reason to continue
talking and collaborating on these topics. We can even
imagine another project merging in Persona.

My goals with nongrata are 1) show how we can integrate
it with Clojure (Noir) and 2) kick the tires on the
security model so Dan can take some good feedback
back upstream.

> ...works with Jenkins / CI so that this wonderful autoci thing he

> set up for us continues to work well going forward.

In word... Jenkins is "the bomb"! Ben asked me about my
setup and I've committed to writing a blog post about it
(stay tuned).

Regards,

--Tom

[Nick Bauman]

So since it has been only me and Tom that have expressed an opinion about ditching the clojurescript component, I decided to stay on track in the name of keeping to the community's original mission. I now have been able to get the browserid.org callback mechanism working.

I think the hard part is done and checked in: the initial handshake. I'll probably have the rest done by tonight or tomorrow.

Cheers,

Nick