[SOLVED] project layout

[JT4NK3D]

I want to start a project (i'm using BlueJ IDE) but im not really sure how to organize it. Im going to have 1 driver class and then other classes with all the code and methods that the driver class will use, and among those maybe some interfaces, but I need some kind of structure to start with. Can someone please give me a typical layout to help me get started? If someone could post something like e.g.
driver class
_____________|_____________
| | | |
class1 class2 class 3 class4
|_______| |_______|
| |
interface1 interface 2

Not that, thats just the general idea but i really dont know very much about making projects with lots of different classes etc. this is probably a noobish question but i dont know how im gonna start it please someone answer.

[roots]

Code organization is an important aspect in programming. If you have general idea on how your classes will be. Divide them according to their functionality. For example separate the part that is related to database, user interface and so on. Put them in separate packages.
There is no hard and fast rule for the organization. Its all about making whole project easily comprehensible.

[Eranga]

All depends on your skills. Such organizing can't learn by a book, you have to make a right decision and go ahead.

[greyhat]

it depends on your scenario and skills

[Eranga]

Not that, thats just the general idea but i really dont know very much about making projects with lots of different classes etc. this is probably a noobish question but i dont know how im gonna start it please someone answer.

One of the basis idea in OOP is collect much similar process into one place. Make a class and put them inside it. You can make any number of classes, (as well as any number of methods in a single class) to make clear your project.

So always think about the common views of each other. Make all names(classes, methods, fields) in descriptive way, more depend on the class you work out.

[JT4NK3D]

Thanks, I have a better idea of what to do now. So should i just make all the other classes that the driver class uses subclasses of the driver class?

[Eranga]

Yes, start from subclasses implementations. It's the much better way to do it.