Re: Giving an application a window icon in a sensible way

RedGrittyBrick wrote:
[...]
You can get Eclipse to insert stuff by clicking the light bulb in the
left margin. Either Alt+Space (Content Assist) or Ctrl+1 (Quick Fix) can
be useful too. Use Ctrl+O to get the imports done for you. Surely you
already know all this?

Much of it.

How long have you been using eclipse?

Time actually clocked using it might be a week or two. Not much IOW.

No, you talked about "ten billion". I'm glad to see the hyperbole
reduced but I still think you're exaggerating by a couple of orders of
magnitude. I do apply "such usage" and I don't have anything like that
many test classes, even though I've deleted none.

Whatever. Still seems like overkill.

A couple of observations:
1. Whilst you are reading this newsgroup, you are not deep into your
project. Context switching to Eclipse between newsgroup postings isn't
much of a disruption to me.

To you.

I made a general comment, you are talking about a specific situation.
I'm saying that my experience is that the general approach is often (but
not always) useful. You *seem* to be saying that making small test apps
is never useful.

I'm saying that I think it's overkill in many of the situations where
people keep recommending it, and that it seems rather involved relative
to the alternatives.

I don't see either of these as being anything like as quick as you make
out. Unfortunately, the bugs (mine or otherwise) that would be isolated
with the least effort by this method are exactly the bugs that are so
localized to one or two lines of code that they rapidly succumb to
debugging tools such as breakpoints and added System.out.println
statements. The more complex problems are the very ones that will
require an effort to reproduce this way comparable to making a
substantial new project in its own right.

The subject-line of this thread can be demonstrated in a few tens of
lines of code. So I believe that at least half of your recent questions
could have been handled that way.

I don't see how, unless you're suggesting either that I should have
just sat down and somehow had the code I didn't know magically pour
forth from my fingers despite my not knowing it or that someone helping
me should have posted such code for me to copy and adapt.

There's also the issue that the stripped-down copy produced (by either
method) will, for more complex situations, still potentially reveal way
too much about the nature and architecture of my project. I had one
reason to avoid doing so in the past; lately I've added a second,
namely that every fact that is exposed about what I'm doing is another
potential target for someone to latch onto to criticize for no apparent
reason beyond the sheer joy of criticizing someone.

That is a good thing! I always learn something to my benefit. I gain,
the posters expend the effort. It's a bargain and I thank them for it.

Did you completely miss the bit about how it would gratuitously expose
me to gratuitous attacks? I have enough problems now as it is without
handing some of the other people in this thread ammunition on a silver
platter! (Problem being it doesn't matter if the code is squeaky clean;
the personalities in question will still invent something "wrong" with
it and launch a fusillade, when they might, hope-hope-hope, post one
fewer post attacking me that day otherwise rather than the same number
but with one picking on me for something different.)

In the worst case, enough implementation details are
exposed, and enough of those become the focus of some dweeb's pointless
attacks, that defending them actually requires 300 GG accounts and over
24 hours a day of defending. At that point, it becomes impossible...

and if I react
somewhat negatively to any and all attempts to pry beyond the narrow
confines of the specific areas about which I've asked questions, as
well as to all suggestions that would involve exposing lots of such
details in one fell swoop.

Your "attempts to pry" are other people's "attempts to help you". I'm
not much surprised your negative reaction isn't well received.

My perceptions are colored by my experiences here so far.
Understandably so.

Also, I'm mainly talking about things like:

Q: How do I do X?
A: Why do you want to do X?

Who's asking, Sigmund Fricking Freud? This isn't a psychoanalysis. Just
tell me how to do X please and never you mind why. :P

Honestly, I don't get responses like that. They seem to imply that the
responder thinks any use of X is automatically suspect and the poster
therefore goes on a "moron watch list" full of false positives, not
unlike the "terrorist watch list" and with slightly milder
consequences, like having their every step questioned, nitpicked, and
criticized, well beyond the scope of what they were asking for help
with.

If X is deprecated API, I can see such a reaction, but otherwise? :P

Please explain; I'm curious to hear what you think about this,
including about the underlying motives and states of mind.

It won't mean that such questions won't put me on the defensive,
though. Whoever else is watching will read the question, read between
the lines, and begin to suspect that maybe I'm a moron, and it will be
up to me to set the record straight on that score lest they actually
start thinking it's true.

Sounds like you need version control and branching -- or at least so
some other people here would probably jump at suggesting. ;) (I'd say
it depends on the complexity of what you're doing. If you're
maintaining parallel versions of something over a significant span of
time, it may very well be warranted. If you're just forking a quick
copy to experiment in, it might be a waste of time instead.)

If Eclipse supported RCS I'd be using it. I miss Vim and RCS! Setting up
a CVS repository is something I'll probably get around to one day.

Isn't RCS evil and proprietary and unfree and things like that?

Whoa *does double take*

You miss ... vim?

I don't miss the days of having to toggle in the OS and your own code
from scratch every run, and I don't miss the more recent days of having
to fumble around in the dark probing the immediate environment by
typing instructions to a mentally-deficient prompt of some kind instead
of being able to see what the heck I was doing at a glance and easily
find stuff, orient myself, and whatnot. GUIs were like finally finding
the light switch after years of fumbling around with a flashlight all
the time. And now you're saying you prefer clunky,
ten-zillion-things-to-memorize flashlight-fumbling interfaces to a
modern text editor you can just type into and use in a natural way? I
suppose you also prefer nostalgic cars you need to actually crank up to
start, or the quaintness of churning butter or hand-wringing laundry
too. ;)

I'm now seriously considering retrofitting the icon with
getResource

Halleluya!

Let it be known that this is in no way to be taken as any kind of
admission, whether of wrongdoing or of incompetence or of whatever
else; let the record show that I have my own reasons entirely
unconnected with any kind of peer-pressure or any of the specific
things mentioned here earlier. It is because I don't like compiler
warnings, a reason that nobody ever suggested. :)

Testing it, it doesn't seem to work. It's looking for the project
javadocs, which I've not built at this time, rather than the standard
library javadocs, and that's while pointing at the identifier
PriorityQueue and seeing in the regular-F2 window the PriorityQueue
class docs' preamble (before the method list etc.) without hyperlinks.

When I use a copy of Eclipse without the core Java documentation
installed, and press Shift+F2 with the cursor over PriorityQueue, I
don't get an F2 window, I get a dialog box that says "The documentation
location for 'PriorityQueue<E>' has not been configured. For elements
from libraries specify the Javadoc location URL on the properties page
of the parent JAR ('rt.jar')".

I got something like this but it was looking for the project
documentation, not the JRE documentation.

I'll fiddle with it some more and see if I can get it working, of
course. When I have time.

I think you said you only trust wikipedia and sun.com, which is a shame
since http://javadocs.org/PriorityQueue is also very handy (substitute
any JRE class for PriorityQueue.)

What is that, a mirror of Sun's copy? What's the advantage -- speed or
reliability, or just a backup? I have my own local copy of the API docs
anyway.

[suggestion of ill mental health directed at me]

Aww, and we were doing so well, too!

.