• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

B&S Total classes in the project.

 
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have finished the coding part. Still need to generate the javadocs.
All together i have created 4 packages with just 15 classes.These are the packages

suncertify.client

suncertify.config

suncertify.server

suncertify.db

I saw lot of people posted that they had about more than 30 classes. Am i too short?
[ May 22, 2008: Message edited by: John Mattman ]
 
Bartender
Posts: 2292
3
Eclipse IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hey man.

I think you should not worry about these numbers. For instance, I finished with 5 packages (and other 4 packages inside them), 56 classes and around 2000 lines of code. I think you should only worry if you have to many inner classes, and too many classes with too much code. I would say that this may be considered in the OO Design part of their evaluation.
 
John Mattman
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for your reply Roberto. One of my class has 3 listeners as inner classes. Will that going to be problem?

John
 
Roberto Perillo
Bartender
Posts: 2292
3
Eclipse IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hey my buddy.

Well, I would avoid this, you know... take a look at this article: http://developers.sun.com/mobility/midp/articles/slimming/. Even though it is about wireless Java applications, the behavior of the JVM theoretically is the same (in this case), and they do advise to avoid inner classes. I've also seen many discussions around the software engineering comunity, where people tend to avoid inner classes. I do too because I believe it makes the code more cohesive, maintainable, reusable and readable.

I also have a big number of classes because many of them are interfaces, and I created several components as well.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic