pete stein wrote:
Leandro Coutinho wrote:I think you should use them as inner classes, because this is one of its purporses.
Normally it is a specialized code, i.e., you won't use it in other places, so you use it as inner class.
As noted in the post above you, this is fine for small apps, but if you start to develop large and complex apps, you may find that this doesn't scale well, that you need to separate out the control portion from the view portion of the code.
Hi,
thanks
alot for your suggestion.
but for seperating view portion from control portion, i have to make two separate packages.
1. one for classes related to view part of an application.
2. other for listener classes.
so for accessing listener class in view portion, i have to make it public.
so is it a Standard way to expose listener classes to outside according to application design point of view???