mrynit

this is the capstone project for my GUI programming class. my group is making a program to handle and manage studnets and tutors signing in and out of the schools math center.

so far we have a basic sign in and out for studnents with time stamping, adding new students, reading and writing student list to disk. when the program loads it checks to see if the file of students exists then reads it or makes a new one. the tutor tab doesnt do anything. the admin tab is buggy but the change student info works.it is not finished and is a work in progerss.

Would you all please look over our code and see what should be changed, comment style, class structure, better OO modling, problem solving, break up the large class file into smaller peaces and so on.

Attached Files

capStone.zip (9.2 KB, 28 views)

__________________
i dont know much about programming but i try to help

msi_333

I think you made a very good work.The GUI is excellent.








Computer Science & Information Technology Engineer.
My Place on the net :
http://www.codemiles.com

mrynit

i am more conserned about the code rather than how it looks

__________________
i dont know much about programming but i try to help

andro

If it were mine I would definitely make an effort at moving some code out of MathTracker.java. There's way too much in there that could easily be moved to other classes imo.

mrynit

why? all the code is related. more lines means its better!

__________________
i dont know much about programming but i try to help

xavier

Actually all the classes in MathTracker.java should stay in separate files. There's no point in making one big file.
That, you could explain a bit . Why is that better?

__________________
Don't take life too seriously, it's not permanent !

msi_333

IT is a good Design is to make small classes and using OOP Concepts ,to make it readable and easy to understand and also easy to add more function to it

__________________
Don't walk in front of me, I may not follow.
Don't walk behind me, I may not lead.
Just walk beside me and be my friend

mrynit

That it what my group thinks. I know it is wrong. it should be split into many separate classes. It is quite logical to separate it for the tabs, at least, considering each tab has a lot of methods and anonymous classes for action listeners.

do you have any suggestions to convise my group to slipt it up? I said it was way too difficult to browse the file considering there are like 30 methods and 10 classes all in one file! args!!

__________________
i dont know much about programming but i try to help

xavier

Well, what if : your GUI would be 10times more complex ? what then? there's no point in making a 3000 lines file. Imagine working on line 789 and 1934 . It would be a nightmare. Similar code is grouped in separate folders: You can have a folder for the GUI stuff and another for the rest of your logic ... and so on , depending on your project.

+ what msi_333 said

And another thing: What if you had 2 windows . The first being MathTracker.java and the next Something.java, and they would need essentially the same inner classes .What would you do then ? where would you put the inner classes ? Something.java or MathTracker.java ). The best place for them is in other files.

__________________
Don't take life too seriously, it's not permanent !

mrynit

thanks. I do understand these reasons, I just have a hard time explaining what I know is right to people. I will write these notes down and present it to the group. I hope i don't come off as a conceited smart ass.

__________________
i dont know much about programming but i try to help