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

On Nov 21, 12:31 pm, "Twisted" <twisted...@xxxxxxxxx> wrote:
Method 1 involved: getting a couple of class files, editing one of them
to fix a simple bug, and compiling.
Method 2 would have involved: learning a chunk of new API and either
figuring out how to get Eclipse to tell an app where to find resources
when it's run in the development environment rather than from a final
packaging or building a jar for every edit-test-debug cycle.
Method 3 would have entailed all of the things mentioned in Method 2,
plus obtaining a new tool, learning how to use *that*, and possibly
additional things.
You insist on continuing to exaggerate the method we're suggesting.

You don't have to tell the app where to find resources. You simply put
it in the classpath. Whether that's inside a JAR file when you deploy,
or simply inside your class directories, i.e. classes/.

Advantage of method 1: simple and straightforward and quick. (It took
maybe half an hour.)
Straightforward and quick? As an earlier poster pointed out, this is
the procedure you've told us you are following:
Step 1, convert image to XPM,
Step 2, run some tool to convert it to a class file.
Step 3, move the class file into the correct place.
Step 4, use some uncommon third party tool to load and convert the
class's data..
Step 5, Fix the third party tool, because it was broken.
Step 6, Fix the third party tool again, because it was broken in
another way.

How is this simple and straightforward?

I find it curious that this "tried and true" method was not the first
relevant Google result for the topic, while the method you deride
*was*.
Because we all know the Google ranking algorithms can determine best
practices for software development.

Overdesigning is a
frequent source of missed deadlines, bloated budgets, and yes, even
bugs.
None of which are an issue with the very simple approach advocated by
myself and others in this thread.

If anyone wants to point me to a quick tutorial on managing external
resources that explains how exactly to make Eclipse hide any underlying
complications from you so that you can focus on doing *actual
programming*, I'll bookmark it for future reference. Anything that
involves an extra, manual build-Jar step on every edit-test-debug cycle
is, of course, right out.
Again you are exaggerating the process we are recommending here.
Eclipse has nothing to do with it. And using the classloader to load
resources such as images is *actual programming*, I'd be curious to see
why you don't see it that way. You don't have to build a JAR file every
edit-test-debug cycle, as we have said several times now. It just needs
to be in your classpath.

Didn't you hear? They're De Rigeur(tm) when discussing certain things (and certain *attitudes*) on the net.
No, not really.

I'm trying to understand here. You have no problem hacking some third
party class, and transforming a simple icon image to a weird format,
but you don't feel like using something that's built in to the JVM
(classloader) for this very purpose? You are trying to re-invent the
wheel. External resources like strings, images, etc. can be loaded by
the classloader so that you don't have to worry about where it's
installed or how it's deployed, which I believe was your original
problem.

--
jpa

.

Relevant Pages

  • Re: Giving an application a window icon in a sensible way
    ... newsgroup, spending lots of time and effort helping out people with their ... Did you say you were using Eclipse? ... then I have no further objections there. ... If I have more resources, ...
    (comp.lang.java.programmer)
  • Re: help with understanding relative path problems
    ... I've developed and tested a java program in Eclipse. ... I then packed this program up into a jar file (which by the way is ... The problem is that all of the resources I've named in my program are ...
    (comp.lang.java.help)
  • Re: GBLSECTIONS loop
    ... >> The offer by AUTOGEN to fix this never works. ... to fix problems around AUTOGEN and some of the layered products and greedy ... DECW was typically a victim since it is the last resource-hungry ... everything should have enough resources to start up. ...
    (comp.os.vms)
  • PHPMyNewsLetter 0.6.11 - customize.php include problem
    ... Vulnerable: PHPMyNewsLetter 0.6.11 ... Advisory by Eclipse at packx.net, ... wouldn't fix the vulnerability of PHPMyNewsLetter ...
    (Bugtraq)
  • Re: Default Task Type
    ... why would you fix the duration and vary the resources ... Reducing scope because the business objectives or priorities ...
    (microsoft.public.project)