On May 7, 2011, at 10:01 AM, isaac praveen wrote:

> On Sat, May 7, 2011 at 5:50 PM, Laurent PETIT <laurent.pe...@gmail.com> wrote:
>> Yeah, nrepl support for CCW, which Chas personnally did, has been an
>> incredibly valuable addition.
>> 
>> I'm glad to see more tools adopting it for backend support !
>> 
> 
> I agree.

Indeed, this was exactly my intention when I set out to build nREPL.  So, we 
now have Eclipse/CCW, jark, and Enclojure (soon: 
http://groups.google.com/group/enclojure/msg/a742dd461c88109b) using nREPL; 
such common ground will certainly make it easier to support having diverse 
toolsets in teams of Clojure programmers, etc.

On May 6, 2011, at 7:37 PM, Ambrose Bonnaire-Sergeant wrote:

> We haven't started on a VimClojure nREPL fork yet.
> 
> We should probably ask Meikel if he's already tackled it, there is a "nrepl" 
> tag on
> bitbucket but it's about 6 months old. 
> https://bitbucket.org/kotarak/vimclojure/overview

My recollection is that Meikel was a fair ways along in his nREPL 
implementation late last year.  Hopefully he can chime in as to what the 
current status is of things there.

> Also, the nrepl-server itself should be bundled with some basic
> utilities. That is where jark is useful.
> 
> Jark is a tool that provides
> a) a nrepl-server
> b) a set of extensible utilities to manage classpaths, namespaces, JVM  both 
> on
> c) a command-line client that communicates via the nREPL protocol, has
> minimum runtime dependencies and can run on most platforms.
> 
> It would be nice to have a jark/nREPL plus SLIME/Vim stack.

nREPL + jark + some baseline set of introspection utilities and such (started 
to be described here: 
http://dev.clojure.org/display/design/IDE+tooling+backend) is looking like a 
proper foundation for Clojure tooling, regardless of platform/editor/etc.

FWIW, I'd like to throw out the notion that perhaps some small part of jark 
might make sense to be rolled into the nREPL project itself (in particular, a 
command-line interface / client is needed -- there's one there, but it's far 
from ideal).  Further, if the jark leads are open to it, it may be worth 
discussing over on clojure-dev to see what the appetite is among the core folks 
for a Clojure Contrib project with jark's objectives/scope.

Cheers,

- Chas

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

Reply via email to