General Guidelines about Java Application

[Sameer]

Hello,
Can anybody give me general guidelines about developing a professional
Java Application?
I mean what things must be take into account while coding a java
application?
Some few things may be like centering the frame on the screen, making
the java application resolution independant i.e. it does not hides some
components when the screen resolution changes from 1024 X 768 to 800 X
600 like a typical simple VB application.
It may read some system properties and do some stuff related to it.
It may detect the OS and do some stuff related to it....
............

-Sameer

 

[Oscar kind]

Can anybody give me general guidelines about developing a professional
Java Application?
I mean what things must be take into account while coding a java
application?

Start with keeping it simple. This cannot be stressed enough: for
professional applications, requirements tend to be vague and thus change
often to meet knew insights. Not to mention that users may actually change
requirements too.

Also, it's often difficult enough to try and model the user requirements
into something the user can work with. You don't want to add to that task.

IMHO, it is thus important to keep it simple. This includes:
- Design good underlying data structures. If you do this well, much of the
application writes itself.
- Not using "cool" technology. If it's simple: OK. Otherwise, practice
with it in other projects; not this one.
- Reusing interface components. This also makes your application easier to
understand, which is a plus.

If you keep it simple, you have enough time to make the customer happy.
Keeping it simple also leaves enough time to actually finish the project
on time, within budget and relatively bug free. This last part makes sure
the customers keep coming (back).

Some few things may be like centering the frame on the screen, making
the java application resolution independant i.e. it does not hides some
components when the screen resolution changes from 1024 X 768 to 800 X
600 like a typical simple VB application.
It may read some system properties and do some stuff related to it.
It may detect the OS and do some stuff related to it....

Often it's easier not to specify such things, and let the OS take care of
it. Also, make sure the interface fits completely in the lowest resolution
you want to support: 800x600 or even 640x480. It may look better on higher
resolutions (i.e. less cramped), but if it can display at 640x480 it fits
on any screen.

In case of full-blown environments to do stuff (like Outlook for messages
and time management for example), you may also have a look at the
maximized window state.