Application layering design question

Hi,

What is the best design method for separating in an application some important components that we need to keep track of, other components that need to do something not so important(like showing some text, buttons for some actions over the important components)?

The idea is that for serializing this structure we only need to serialize the important components that define the structure and logic. The rest of the components are auxiliary and are there as helpers for those primary components.

Please give me any idea or thought that you might have about this.

Thanks.

[603 byte] By [oopcodera] at [2007-10-2 11:02:20]
# 1

It's called Model-View-Controller architecture (or design pattern). Live it, love it. Dozens of links on this site and on the Net. Place your 'important' logic and data structures in the model. Your buttons are view components, but the listeners that act on them are controllers. The rest should be relatively straightforward going through a tutorial. Numerous discussions of MVC as posts in this forum as well.

- Saish

Saisha at 2007-7-13 3:34:08 > top of Java-index,Other Topics,Patterns & OO Design...