It is possible, but it may not be easy. If you can find the Sun Java
docs then you can also find the Sun Java tutorials, which a probably a
better way to get started.
rossum
<http://java.sun.com/docs/books/tutorial/index.html>
Mind you, the Javadocs are an excellent and important source of information,
particularly the package-level docs.
--
Lew
Multi-posting is the practice of sending the same message independently to
separate newsgroups, and is both ineffective and somewhat rude. Most of the
Java newsgroups have substantial overlap in their readership; your message
will get through if you send it to only one of them. Furthermore, a person
won't enter an answer only to find that it is not in the conversation when
viewed from another group. It's not a good idea to fragment the
conversational threads in that manner.
Please do not multi-post. If you really feel the need to redundantly post
redundantly to redundant newsgroups, use "cross-posting", where the same
message posts simultaneously to all of them in a linked way.
People started answering you on clj.help only to find that you'd gone and
started over on clj.programmer.
--
Lew
[snip remainder of OT tangent]
I don't see anywhere where you answer the OP's question, and I don't
see anything to make what you did write relevant. Why would one
question get a straight answer, and another answer with nothing
visibly different (in the body or the headers) about it get a useless
response like the one you just wrote? And yet that's what I see here.
Nothing different about various questions, but something very
different about the attitude you had when answering them.
Huh. You must've missed my first post to their question, then.
--
Lew
This is substantially the same information that was provided in the clj.help
version of this thread, joined here with the clj.programmer line for
everyone's convenience.
After you've gotten a gander at the tutorials, Sun also has delightful white
papers. While they might not directly reveal code idioms you want to use
(though many do), they provide much insight into the mindset of the Java
universe and the way things work.
IBM developerWorks
<http://www.ibm.com/developerworks/>
has an entire tree devoted to Java that is priceless.
<http://www.ibm.com/developerworks/java>
--
Lew
I'll second that. I find multi-posting to be
counter-productive, and very irritating as well.
>...If you really feel the need to redundantly post
>redundantly to redundant newsgroups, use "cross-posting", where the same
>message posts simultaneously to all of them in a linked way.
Further info.
<http://www.physci.org/codes/javafaq.html#xpost>
--
Andrew Thompson
http://www.athompson.info/andrew/
Message posted via JavaKB.com
http://www.javakb.com/Uwe/Forums.aspx/java-setup/200708/1
That WAS your first post to their question. This thread has only six
posts. The OP's question, your OT followup, my followup to your
followup, your post I'm replying to now, Zig's more helpful separate
response to the OP's question, and your response to Zig. Seven now,
including this post. More if you read this later and there've been
more new posts, which will all be dated after this post's timestamp.
Google's archive shows nothing after the OP's question and before your
OT followup, from you or anyone else, to this thread. Even if
something had been posted with X-No-Archive: Yes I'd see it now as
it's been less than six days since the thread was born.
So no, I didn't miss your first post to their question. I followed up
to your first post to their question. :P
The first post on this topic from Lew that I could find, either on the
UCSD NNTP server or on Google groups, is
http://groups.google.com/group/comp.lang.java.help/msg/df0d4396f06d0f22
It was a substantive reply.
It was posted to comp.lang.java.help. If you looked only in
comp.lang.java.programmer you would not have seen it. Confusion due to
some posters only seeing part of the discussion is a natural but
unfortunate consequence of multi-posting.
Patricia
So you can argue that Lew wrote what he did for the benefit
of Twisted !
:-)
Arne
Nope. That is not a post from Lew to this thread. The first post by
Lew to this thread was the 100% OT one I called him on.
What goes in in some other thread is irrelevant, especially if it's
not even in the same *newsgroup*, because I won't necessarily have
read it, and neither will anyone else. Any reference to such is thus
going to appear out of context to a majority of readers and should
therefore be avoided.
Keep discussions inside the same thread where they originated. If your
newsreader doesn't thread references properly when you reply get a new
one. *Google Groups* even manages to get that bit right, for heaven's
sake!
If Lew was indeed referring to a post he made in a completely
different place, and perhaps to one the OP made in a different place,
it's no wonder he made no sense at all; he posted in the wrong place.
He should have posted in the other place. :P
Actually, you are posting in both comp.lang.java.programmer, in a thread
that does not contain Lew's original response, and in
comp.lang.java.help in the same thread as Lew's response.
You seem to be treating "thread" as the same "topic" or as containing
all responses to a given question. Ideally, that would be the case, but
multi-posting makes them different.
Patricia
>How can I learn Java's library from the API docs?
The problem with the API docs in they contain many methods you will
rarely use. You get swamped in detail. Read the tutorials first. Also
look up the components in the Java glossary e.g.
http://mindprod.com/jgloss/jbutton.html
It will show you a small program that uses the most common methods,
all heavily commented.
Then go back and read the API's to see what else is in there.
--
Roedy Green Canadian Mind Products
The Java Glossary
http://mindprod.com
Thanks for the Site Roedy Green
Eh. I'm using "thread" to refer to a thread, as in what Google Groups
shows to be a tree of responses to an initial posting in
comp.lang.java.programmer when tree view is on. I am not subscribed to
any other comp.lang.java newsgroups and don't read them so I don't
know what's going on in them and I frankly don't care either.
Referring to events in one of those here is going to leave readers of
this newsgroup confused and lacking context. If there's some necessity
for doing so a summary of whatever it is that establishes the relevant
background context for people who only read cljp would seem to be in
order, and probably a GG link or several for those who want to see
what the summary is based on. OTOH, it's almost guaranteed that
referring to events in one newsgroup from another is just going to be
OT and confusing no matter what you do. Stick to discussing Java. :P
I guess as someone said once usenet -> uselessnet
just my pov.
--
Cheers,
Ishwor Gurung
/* humpty dumpty */
>
>> > look up the components in the Java glossary
>> > e.g.http://mindprod.com/jgloss/jbutton.html
I agree with Roedy. Tutorials are easy to grasp and they show u how you can
use a particular method in an API.
>
> Thanks for the Site Roedy Green
As an aside, Sun's java website has lots of tutorial on Java swing. It might
be a good place to start. Goodluck!