Skip to main content

How to Decide on Product(desktop appl) Architecture

6 replies [Last post]
titanicemerges
Offline
Joined: 2007-07-19

Hi All,
I am newbie here and also to desktop applications... All these time in my career been in the web services.
Now in my company ,we are trying to develop a product ,clearly a desktop application .The main theme of the application is to MAINTAIN A LOCAL REPOSITORY AND A FRONT END FOR THIS...We thought about webserver for the local transactions and not able to decide on any thin web server.
THE MAJOR PROBLEM IS MOST OF OUR TEAM ARE WELL VERSED IN JSP,SERVLETS AND OTHER WEB SERVICES AND NEW TO DESKTOP APPLICATIONS.....
The fix we are in right now is what sort of architecture we need to stick to for our application.
Could anyone help us out how to go about deciding a desktop architecture as a startup .

Thanks and Regards
Kishore

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
coderight
Offline
Joined: 2006-06-02

[b]Jazz Desktop Application Framework[/b] provides everything you need (including architecture/how to start).
Even with little or no Swing experience you can develop desktop applications with Jazz.

Regards,
Will Boluyt
CodeRight

http://www.coderight.nl

opginf
Offline
Joined: 2004-07-20

May I know what your requirements are, might be I could help you out on this.

prunge
Offline
Joined: 2004-05-06

Hi Kishore,

We developed a Swing application a while back, and found that most books on Swing (especially introductory books) gave examples where a Frame was built up and filled with basic Swing components, panels, buttons, text fields, etc; nested panels within panels within panels and lots of components added to a frame in one class. So at the start developers were copying this approach.

We found it was much better to build smaller reusable components, with their own data models, listeners, etc. No Swing books at that time (this was years ago) actually described this approach at all, and since everyone was new to desktop app development they just copied the approach the books used.

I know what I described is probably common sense to most, but when you are learning something new it is very tempting to copy approaches used in books.

nimloth
Offline
Joined: 2005-01-25

About the hint with eclipse: We use Eclipse RCP for our "rich client" and we are very unhappy with it. The Problem is that our application is a end user application. Its very GUI centric (It's a Desktop CMS). We have special requirements for the GUI and a lot of Problems with Eclipse RCP/SWT.
We will change in the future to Swing. Our solution will then be OSGI (Eclipse low level) with Swing!

Use reusable blocks where your common sense told you so. The stuff in the books are examples and most of the time when reality comes in, you are on your own.

We developed a little "In Place Java DSL" for our property Sheets. So even the none-programmers in the team could make Property-Dialogs. (-:

kirillcool
Offline
Joined: 2004-11-17

Does most of your team use CAPS LOCK ALL THE TIME?

weberjn
Offline
Joined: 2003-11-11

What you call desktop architecture is usually called rich client architecture.

The best rich client framework for Java is Eclipse RCP:

http://wiki.eclipse.org/index.php/Rich_Client_Platform