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

nebulous99@xxxxxxxxx wrote:
RedGrittyBrick wrote:
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.

Likely, because you know of some shortcut that I don't.

I really doubt it! I only know half a dozen keyboard shortcuts that are specific to Eclipse.

(Eclipse seems
to include a whole damn continent worth of just shortcuts alone, the
exploring of which would take any single person decades. So you can't
fault me for not knowing some specific one. :))

145 items is a lot but I'm not sure it is exactly continental. I think I'd reserver the work continental for bigger numbers. It's not hard to pick "key assist" from the "Help" menu and look for anything relevant.


Care to divulge it?

Divulge is a strange choice of word, it has undertones of concealment and witholding. I get the impression you choose your words carefully.

As I already said, to create a new GUI project I cut and paste (Ctrl+C Ctrl+V) from a myGuiTemplate.java or elsewhere.

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?

How long have you been using eclipse?

(I'm guessing it creates a new stub Swing-app
project in a couple of mouse clicks and one typed-in project name,

There may be a way of doing that but I don't know of it.

but
does not solve the 10,000-projects clutter problem I've pointed out
such usage would lead to in a relatively short span of time.)

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.

As a rule, I prefer to work on one thing at a time. Regardless of its
merits, creating whole new applications at the drop of a hat will
necessitate tons of context-switching and workflow disruption...

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.
2. When I hit a snag in my main app, if I want to test some idea out, it's sometimes *less* disruptive to do it in a small separate application which runs faster and has less baggage.


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?

Eh what? I don't see how cut and paste helps. If I've got a broken
behavior involving my use of, say, the Foo class, in a threaded context
with various accesses, I'd need to copy and paste several chunks of
code (and each chunk means switching projects *twice*) and then write a
whole lot of glue code before it will even *compile*, likely including
a new thread subclass or two. Then I need to tweak it until it
reproduces the behavior seen in the original app...

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.

The alternative would seem to be to copy the original project in its
entirety (all potentially however-many class source files worth) and
then pare it down, which might take an insane amount of time (and if
one important bit is deleted by mistake, the result either won't work
or won't reproduce the original problem, and then it all has to be done
again *from scratch*...)

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.


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.


If I mention that
I'm doing X, in other words, then anyone who for whatever reason thinks
doing X is dumb is liable to go and open their big mouth and I'll be
forced to defend my use of X. Multiply that by however many details are
revealed, and before long that's a lot of defending and not much actual
work getting done. 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 to
avoid letting at least one criticism a day slide, with the devastating
consequence of bad beliefs about me beginning to circulate unopposed.
And the number circulating then growing with every passing day until,
presumably, all 6 billion people in the world believe something bad
about me and nobody will want anything to do with me again. Needless to
say, that would then put a crimp in my lifestyle...

So I hope you'll forgive me if I'm sparing with details,

Thats a lot of words to say something simple!

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.

<snippage - too many topics for one posting!>


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.

<more snippage>

I'm now seriously considering retrofitting the icon with
getResource

Halleluya!


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.

Shift+F2? You don't mean just the little scrollable box with an
abbreviated, un-hyperlinked version? (Which I'm fairly sure was just
regular-F2...)

No, I don't mean that.

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')".

The web page I referred you to (below) walks you through the process recommended by Eclipse.

When you do that, Shift+F2 takes you to a fully hyperlinked web page in sun.com that displays the docs for the relevant class (if a Sun class).

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.)


It does at least seem to be able to find the standard library javadocs
to provide the latter functionality, even if shift-F2 is misfiring.

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

The last tinyurl I ran across led directly to goatse, so I hope you'll
forgive me if I at least save this one for later. :)

Most browsers let you turn off Javascript, images etc for untrusted sites and there is always Lynx.

In the unlikely event that anyone less ... well ... paranoid reads this, it may prove useful for them, if not for you.

Good luck!
.

Relevant Pages

  • Re: Setting up JBOSS 5 Server on my local computer
    ... Run on Server" deployment options in Eclipse to deploy the app to the JBoss instance, or to use JBoss's own deployment tools to deploy the WAR or EAR files you build with Eclipse. ...
    (comp.lang.java.programmer)
  • Re: Lisp v. Java/Eclipse
    ... First off, Eclipse is great! ... and was Lisp-programmable it would be The Killer ... far from calling it "Killer App". ... It is best tool for doing refactoring in Java. ...
    (comp.lang.lisp)
  • Cannot export eclipse rcp product with fedora eclipse
    ... I am building an RCP app on Linux Fedora 8 x86_64. ... It is a stock standard pure Fedora installation, so the eclipse is based on ... I use the "Eclipse Product export wizard" to make a standalone app. ...
    (Fedora)
  • Re: OutOf Memory exception under Eclipse when using relatively small amount of heap
    ... I've tried an experimental app under Eclipse, ... a large xml file using the java XSLT library DOM parser and ...
    (comp.lang.java.programmer)
  • Re: Eclipse IDE Javadoc Tooltips
    ... it does not show any Javadocs for the other classes that are ... you should change the path depending on your installation of the ... If the JRE thats used upon launching Eclipse doesn't contain the ...
    (comp.lang.java.softwaretools)