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

nebulous99@xxxxxxxxx wrote:
RedGrittyBrick wrote:
Twisted wrote:

You write sample programs just to respond to newsgroup messages? But
the overhead of creating a new project, main class, etc. ... It doesn't
seem worth it. Or are you talking about quick jots in things like BASIC
or Smalltalk that lend themselves to such uses?

It's not just Patricia, I find it only takes a couple of minutes to
write a 30-line Swing app to illustrate some problem or it's solution.

I use Eclipse. I'm surprised you find using Eclipse to be so difficult
that you'd not attempt this!

I find using Eclipse to be much easier than using either text editors +
command line or any other IDE I've ever tried.

But I certainly do not find that what you describe takes "a couple of
minutes".

Really, I wonder why it is that I am so much more productive? Oh well.

Creating a new project and main class with a blank main
method and blinking insertion point, maybe,

I have a Project called Testing, so I don't need to create a new one each time. I just click the "testing" project then click the "new class" button. These two button clicks take only a second or two of the "couple of minutes".

and even then it wouldn't
be long before my workspace was cluttered with ten billion tiny
projects,

Ten billion? You wouldn't be exaggerating unecessarily would you?

A single press of the delete key can reduce the clutter (I've not bothered so far)

Alternatively, when the clutter seems too much, you can create appropriately named source folders within the project (I have "layout", "jdbc" and so on) and drag & drop classes into them.

all of them for some one-time use. Seems a waste.

For me, it's never a waste to learn something new about an interesting topic. I keep them around so I can go back and remind myself of a solution or to use them as a basis for another test case.


If there's some clever shortcut you're not telling me about

There's lots I'm not telling you about, but that is because you haven't asked or because it is not apparent that you don't know.

It's not because (as you imply) that I am deliberately withholding any information. Not that you've any right to demand info from me, you're perhaps lucky that I, and others, are happy to give it.

to just run
some one-off quickie code in Java with Eclipse,

I use Ctrl-C and Ctrl-V to save a lot of typing. I really don't understand why you think this is hard or time-consuming?

then by all means,
don't let some stupid NDA stop you from sharing it. ;)

What NDA?

Incidentally, you don't happen to know any fix for this
tangentially-related issue do you? In Eclipse I've gotten around to
creating three or four projects of various sorts. When started, Eclipse
*always* starts with the first of these as the "current" project (no
matter which was the last edited) and a blank package explorer, whose
active "up arrow" button needs to be used a couple times to get the
full project and package listing.

I don't have that problem with Eclipse 3.1, so I can't offer any certain solutions. Have you tried creating a "Working set" (see menu under down-arrow to right of title in Package Explorer). At start-up Eclipse remembers my last-selected working set. They are also a great way to eliminate clutter (I don't see any Testing classes in Project Explorer when working on my main project).

Worse, folding shut some of the projects causes weird side effects; on
one occasion the package explorer got stuck blank with the "up arrow"
button disabled and Eclipse had to be restarted to make it useful again
(closing and recreating the package explorer "window" did not suffice).

I've not experienced that.

It seems to have a concept of "current project" separate from the run
MRU and open source files MRU,

That is what I see too. I don't find it a problem, so I've no experience of trying to tailor this characteristic. I sometimes find it useful to have java files form several projects open for the following reasons:
- I can cut & paste between projects more easily (e.g. real to testing)
- I have my own common library classes in a separate Project.

Did you know that you can right-click a source tab and select "close others"? It might ameliorate the issue you have with this behaviour.

such that the name of that first project
(now collecting dust for months) is always in the titlebar, and it
isn't obvious how to change it...folding shut all but one of the
projects doesn't change it to the one, for instance, nor does
navigating in the package explorer into one project's classes.

The Project menu is also not informative on this particular matter.
Properties brings up the properties for the project that's active in
the usual sense, so if I call the one stuck in the title bar and where
the package explorer always starts (well, is after one up arrow click
after being blank on startup) A and the one containing the source file
currently being edited B, it's B's properties that come up; if I select
a project C in the package explorer and pick that item again C's come
up (all while A remains in the title bar of the main window, by the
way).

When I select a project in Package Explorer, then choose Properties from the Project menu, it is the selected project whose properties are displayed. This seems to differ from your experience. Are you using a different version of Eclipse?

Related is that the Problems window lists every problem in any project,
not just in whichever one is currently active (in either sense!); one
old project has dozens of them (because it's woefully incomplete rather
than because it's woefully broken, mind you) and the list seems to
limit itself to 100 (configurable nowhere that I can find), with the
predictable results...

You can tailor this, I did so. Select the "Problems" pane, at the right of the title is a set of icons, one is "filters" click it, there are radio-buttons for "On any resource", "On any resource in same project" and so on. I suggest you select one of the narrower scopes.


(The above are just about my ONLY issues so far with Eclipse, though,
which is remarkable for anything of its scope and complexity. The only
remaining niggle is that browsing the library API docs directly from
type names, method names, or whatever is not apparently possible.

Yes it is possible. Position the cursor over any Java Class name and press Shift+F2. You'll need to download the Javadocs (if you have not already) and tell Eclipse where to find them.

http://tinyurl.com/avqq8 Has more detail including screenshots.

For
some reason, functionality that produces an abbreviated piece of the
API docs (if applicable) in a tooltip on hovering over an identifier
mysteriously started existing (or at least started working) a week or
two ago, and F2 does turn this into a scrollable less-abbreviated
version, but being able to go from there to a basic HTML browser
capable of following the docs' hyperlinks would be nice, or even to
make it launch a Firefox tab into the docs, with the second frame in
the package and the third in the specific place...)


See above.

N.B. If this is at all useful, a simple thanks would go a *long* way.
.