This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Originally posted by SGSmoot: How do you know what class does what?
After writing a few programs and studying Java a bit, one soon appreciates the value of the API documentation and recognizes its organization. Every now and then, though, someone will come up with a method and not know what class it belongs to. In which case, my preferred method to find the method (alert repetition: time to refactor ) is to use NavigationZone to search the API for the method.
Anyway, at least some of you will get a good laugh at this and humor helps the day go by.
No way! This forum is here to answer beginner questions just like this one.
Joined: Apr 18, 2002
I think this meens that I need to invest in more No-Doze... Tutorials online are great, but I need LOTS of examples (and an easier IDE. My "team" has decided to use Websphere Studio as our development tool. Please pray for me). My head keeps meeting the Keyboard when I'm not coding. I've already downloaded Eckel's book, as well as the one he has on C++ (thought it would help) and have been looking at that as well. I guess it's just going to take a little (ok, a lot of) time and mis-compilings to get it right. I will also look at the others as well. Thanks! (p.s I did change my name. ) [ April 18, 2002: Message edited by: Sam Smoot ]
Sam, I too come from an entirely procedural background and I understand your question perfectly. Unfortunately, I don't really have an answer... To clarify for anyone who may not know where we are coming from: my procedural language is RPG, a very powerful and old business programming language. RPG has approximately 100 "opcodes". These are all the things that the language can do inherently. Of those 100, I would guess about 30 are commonly used. I am oversimplifying, but as far as actions within the code go it is a fairly straightforward language. Now, compare that to Java. The API lists over 1500 classes and interfaces, most of which have numerous methods, and the actions that can be performed number in the 5-6 digit range. Impossible to know them all, unlikely that you would ever have to! Enter the API. I know you are getting a lot of advice to read the API but it appears confusing and foreign. Well, it is! But if you are like me, after a lot of grinding and hard work, the light bulb just flipped on one day and now using the API is commonplace. I whole heartedly recommend the Cattle Drive. Read some books, write some code. Most importantly, keep at it! Best of luck, [ April 19, 2002: Message edited by: Joel Cochran ]
Wait a minute, I'm trying to think of something clever to say...<p>Joel
Check out "Java Cookbook" by Ian Darwin. Instead of trying to learn the API first - which is painfull, this book gives lots of great examples of how to code real life problems. That way you learn the API by using it.
Please ignore post, I have no idea what I am talking about.
AH - another mainframe programmer converted to the light. Well, maybe not quite yet . . . I am an old mainframe programmer from way back . . . well, we don't need to get into that. The conversion from procedural to OO is a MUCH harder leap than from spaghetti code to procedural. It took me the longest time to stop trying to map things back to the way they are on a mainframe. And to attempt your first project without having at least ONE OO person to help with the design . . . I hate to say it but - this is NOT going to be pretty. You can pretty much could on the result be procedural code wrapped up to look sort of OOish. Which means of course that you will not get all the benefits of OO which are driving you in this direction to begin with. However, it WILL be a great learning event . So - do you have any summary of what the project is about? Anything that we can help you with - besides getting familiar with the API (which is intimidating to say the least).
"JavaRanch, where the deer and the Certified play" - David O'Meara
Joined: Apr 18, 2002
Basically, get XML from a front end, verify against a business model / rules set from DB2, manipulate options in DB2 table (on Mainframe) through EJB's, and then pass XML/HTML back to the browser... Piece of cake (or patty, actually). [ April 22, 2002: Message edited by: Sam Smoot ]
Hi ! Here 's your question "How to assign responsibilities to methods and classes ".
For this purpose you need to have knowledge of Object Oriented Analysis and Design. As you wil be starting a project on Java, so UML will certainly be used and its really easy. Try reading the book "Applying UML and PAtterns" by Craig Larman. This will help you. It teaches all about OOA and OOD and UML. Regards Danish
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com