Re: Giving an application a window icon in a sensible way
- From: nebulous99@xxxxxxxxx
- Date: 26 Nov 2006 00:45:24 -0800
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". Creating a new project and main class with a blank main
method and blinking insertion point, maybe, and even then it wouldn't
be long before my workspace was cluttered with ten billion tiny
projects, all of them for some one-time use. Seems a waste.
If there's some clever shortcut you're not telling me about to just run
some one-off quickie code in Java with Eclipse, then by all means,
don't let some stupid NDA stop you from sharing it. ;)
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.
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).
It seems to have a concept of "current project" separate from the run
MRU and open source files MRU, 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).
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...
(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. 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...)
.
- Follow-Ups:
- Re: Giving an application a window icon in a sensible way
- From: RedGrittyBrick
- Re: Giving an application a window icon in a sensible way
- From: Patricia Shanahan
- Re: Giving an application a window icon in a sensible way
- From: Patricia Shanahan
- Re: Giving an application a window icon in a sensible way
- References:
- Re: Giving an application a window icon in a sensible way
- From: Twisted
- Re: Giving an application a window icon in a sensible way
- From: Ian Wilson
- Re: Giving an application a window icon in a sensible way
- From: Twisted
- Re: Giving an application a window icon in a sensible way
- From: Daniel Dyer
- Re: Giving an application a window icon in a sensible way
- From: Twisted
- Re: Giving an application a window icon in a sensible way
- From: wesley . hall
- Re: Giving an application a window icon in a sensible way
- From: Twisted
- Re: Giving an application a window icon in a sensible way
- From: wesley . hall
- Re: Giving an application a window icon in a sensible way
- From: Twisted
- Re: Giving an application a window icon in a sensible way
- From: Patricia Shanahan
- Re: Giving an application a window icon in a sensible way
- From: Twisted
- Re: Giving an application a window icon in a sensible way
- From: Patricia Shanahan
- Re: Giving an application a window icon in a sensible way
- From: nebulous99
- Re: Giving an application a window icon in a sensible way
- From: Patricia Shanahan
- Re: Giving an application a window icon in a sensible way
- From: Twisted
- Re: Giving an application a window icon in a sensible way
- From: RedGrittyBrick
- Re: Giving an application a window icon in a sensible way
- Prev by Date: Re: Giving an application a window icon in a sensible way
- Next by Date: Re: Singleton Pattern
- Previous by thread: Re: Giving an application a window icon in a sensible way
- Next by thread: Re: Giving an application a window icon in a sensible way
- Index(es):