Thanks to all for your helpful replies. Mikel's greet.clj is something
that "just works," but it requires invoking Java through the command
line. If I go that route, the code that I wrote will work...won't it?
(I'll try.)
But look at the proposed solutions--for example, "It's easier to do
something like this using a Swing GUI with a read-only JTextArea
holding the interaction history above a one-line JTextField used to
submit new input; stick an ActionListener on the JTextField and it
will get called when enter is pressed in the field"! *How* does the
word "easier" belong in that sentence, when I all I want to do is read
input from the keyboard?!
My modest proposal:
I invite the Clojure community to deem this input-from-keyboard
problem to be a Clojure "Adoption Assassin" that is stifling Clojure
adoption by the larger programming community. There are other such
pain points, and they need to be solved.
WOULDN'T IT BE GREAT if we could solve them with a
"Clojure Starter Kit" that newcomers could just load
with their programs to get A MUCH BETTER STARTING
EXPERIENCE with the language?
If anybody wants to nominate a certain problem as a Clojure Adoption
Assassin, I'll be glad to keep track of them and keep the community
aware of them. You can email me at the address below.
Again, thanks for the help. If you think you have a solution to the
problem in my original post, please post it here. Don't consider this
reply to mean that I feel the thread is finished!
-----------------------
Gregg Williams, gregg AT-SIGN GettingClojure DOT-SIGN com
http://www.GettingClojure.com: because we're *all* still learning
Clojure!
--
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
