Let's say I have a GUI project "abc" that consists of 3 "components" each of
which has some widgets (GUI elements), model classes and controller classes.
What's the best way to structure the packages?
My first thought would be something like this:
abc.comp1.model.*
abc.comp1.view.*
abc.comp1.controller.*
abc.comp2.model.*
abc.comp2.view.*
abc.comp2.controller.*
abc.comp3.model.*
abc.comp3.view.*
abc.comp3.controller.*
but then I have seen others who structure things like:
abc.model.comp1.*
abc.model.comp2.*
abc.model.comp3.*
abc.view.comp1.*
abc.view.comp2.*
abc.view.comp3.*
abc.controller.comp1.*
abc.controller.comp2.*
abc.controller.comp3.*
Which is better and why? Or perhaps there is a better alternative?

Signature
And loving it,
-Q
_________________________________________________
Qu0llSixFour@gmail.com
(Replace the "SixFour" with numbers to email me)
Roedy Green - 18 Jul 2007 08:19 GMT
>Which is better and why? Or perhaps there is a better alternative?
I would tend not to break the packages down so finely. It really
depends on how much interaction there is between members. Don't put
things in different packages that live in each other's laps. I don't
know how much interaction there is in your case.

Signature
Roedy Green Canadian Mind Products
The Java Glossary
http://mindprod.com