towards definitive "getting started" assistance
Stuart Halloway
to everyone who pitched in. But this begs the question: Why hide the
getting started instructions in a single project? So, I am working to
create definitive instructions for getting started with Clojure in a
variety of environments.
The goal:
A single source of truth that stays up to date.
The plan:
(1) Keep the instructions linked from a page in Assembla (http://www.assembla.com/wiki/show/clojure/Getting_Started
). Assembla rather than clojure.org to help with maintenance, since
all CA signers can get on Assembla and pitch in.
(2) Link to the Assembla page from clojure.org (tbd soon).
What I (Stu) will commit to do:
(1) Edit and post new suggestions from the community.
(2) Review and test *some* of the suggestions.
(3) Flip the official bit (link from clojure.org) once y'all are happy.
Requested of you, the community:
(1) If you created, or are the expert on, some environment, please
feel free to either update the Assembla page directly, or send edits
to me.
(2) If you find a problem let me know.
(3) If you write or have written a blog post or article on setup
particulars, also link out to the Assembla page.
(4) Help me by reviewing and testing instructions.
Suggestions and comments welcome, as always.
Thanks!
Stu
Wilson MacGyver
I wrote an blog post on how to use clojure in gradle.
That may be of use as part of the "getting started"
Thanks,
On Tue, Mar 30, 2010 at 1:12 PM, Stuart Halloway
<stuart....@gmail.com> wrote:
> The labrepl now has much better "getting started" instructions, thanks to
> everyone who pitched in. But this begs the question: Why hide the getting
> started instructions in a single project? So, I am working to create
> definitive instructions for getting started with Clojure in a variety of
> environments.
>
> The goal:
> A single source of truth that stays up to date.
>
> The plan:
> (1) Keep the instructions linked from a page in Assembla
> (http://www.assembla.com/wiki/show/clojure/Getting_Started). Assembla rather
> than clojure.org to help with maintenance, since all CA signers can get on
> Assembla and pitch in.
> (2) Link to the Assembla page from clojure.org (tbd soon).
>
> What I (Stu) will commit to do:
> (1) Edit and post new suggestions from the community.
> (2) Review and test *some* of the suggestions.
> (3) Flip the official bit (link from clojure.org) once y'all are happy.
>
> Requested of you, the community:
> (1) If you created, or are the expert on, some environment, please feel free
> to either update the Assembla page directly, or send edits to me.
> (2) If you find a problem let me know.
> (3) If you write or have written a blog post or article on setup
> particulars, also link out to the Assembla page.
> (4) Help me by reviewing and testing instructions.
>
> Suggestions and comments welcome, as always.
>
> Thanks!
> Stu
>
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clo...@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+u...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
>
> To unsubscribe from this group, send email to
> clojure+unsubscribegooglegroups.com or reply to this email with the words
> "REMOVE ME" as the subject.
>
--
Omnem crede diem tibi diluxisse supremum.
David Nolen
http://mmcgrana.github.com/2010/03/clojure-web-development-ring.html
is much friendlier and the kind of base-level design aesthetic people expect from programming language introductions these days. I'm more than happy to submit content, sadly my design chops are abysmal.
/me wishes someone would put together a http://tryclojure.org.
David
Stuart Halloway
in multiple places as a consequence of point-in-time decisions and
organic growth. For now I am going to stick with Assembla, but in the
medium run (months) there I want to revisit this idea.
Stu
Rob Wolfe
On 30 Mar, 19:12, Stuart Halloway <stuart.hallo...@gmail.com> wrote:
> The labrepl now has much better "getting started" instructions, thanks
> to everyone who pitched in. But this begs the question: Why hide the
> getting started instructions in a single project? So, I am working to
> create definitive instructions for getting started with Clojure in a
> variety of environments.
I tried to gather all instructions needed for getting started
with Emacs and SLIME:
http://wiki.github.com/robwolfe/leiningen/clojure-with-emacs-and-slimeswank
In my opinion this description:
http://www.assembla.com/wiki/show/clojure/Getting_Started_with_Emacs
is a little bit too terse.
It assumes that everyone is an Emacs and Java expert
and Linux user (e.g. no info about ELPA patch for Windows).
It would be great to have a step by step instruction even for newbies.
Hundreds of blogs is not useful at all. Feel free to use my
description
somehow (e.g. copy and paste) in order to create one comprehensive
wiki page with all needed instructions.
Br,
Rob
Meikel Brandmeyer
On Apr 1, 9:58 am, Rob Wolfe <r...@smsnet.pl> wrote:
> In my opinion this description:http://www.assembla.com/wiki/show/clojure/Getting_Started_with_Emacs
> is a little bit too terse.
> It assumes that everyone is an Emacs and Java expert
> and Linux user (e.g. no info about ELPA patch for Windows).
I think it is save to assume knowledge of the editor. There is no
point in including tutorials for emacs, vim, netbeans, eclipse, ...
themselves (ie. the non-clojure related stuff).
Sincerely
Meikel
Rob Wolfe
Knowledge of the editor is something different than knowledge
how to use ELPA package manager in order to install SLIME
for Clojure and what problems might occur in this process.
Knowledge what JARs are needed and where
they should be placed in order to use swank-clojure
is not only editor related stuff in my opinion.
Br,
Rob
Eric Thorsen
The labrepl now has much better "getting started" instructions, thanks to everyone who pitched in. But this begs the question: Why hide the getting started instructions in a single project? So, I am working to create definitive instructions for getting started with Clojure in a variety of environments.
The goal:
A single source of truth that stays up to date.
The plan:
(1) Keep the instructions linked from a page in Assembla (http://www.assembla.com/wiki/show/clojure/Getting_Started). Assembla rather than clojure.org to help with maintenance, since all CA signers can get on Assembla and pitch in.
(2) Link to the Assembla page from clojure.org (tbd soon).
What I (Stu) will commit to do:
(1) Edit and post new suggestions from the community.
(2) Review and test *some* of the suggestions.
(3) Flip the official bit (link from clojure.org) once y'all are happy.
Requested of you, the community:
(1) If you created, or are the expert on, some environment, please feel free to either update the Assembla page directly, or send edits to me.
(2) If you find a problem let me know.
(3) If you write or have written a blog post or article on setup particulars, also link out to the Assembla page.
(4) Help me by reviewing and testing instructions.
Suggestions and comments welcome, as always.
Thanks!
Stu
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@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+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
To unsubscribe from this group, send email to clojure+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.