COMP 310 Software Development Environment

Install latest Java Development Kit ("JDK")
Install latest version of Eclipse
Install Eclipse plug-ins. Note: Not all plugins shown on installation page are needed! See your semester's specific instructions on the required plugins in Canvas!
1. WindowBuilder
2. Install latest Yatta "UML Lab" diagramming plug-in
  - See "Software Configuration and Licensing" section in Canvas for directions on how to obtain the license key. You MUST be on-campus and connected to the Rice network when you enter this key!

References:

Eclipse:
- Using the Eclipse Integrated Development Environment
  - Setting the preferences for Eclipse <== DO THIS BEFORE ANY CODING!
- Using WindowBuilder
  - Setting the preferences for WindowBuilder <== DO THIS BEFORE ANY CODING!
- Using Subclipse (SVN version control)
  - Subversion Source Control General Information
  - Accessing your own repository <== DO THIS BEFORE ANY CODING!
  - Add an Existing Project to Subversion
  - Committing the Entire Project to Subversion
  - Using svn:externals to Access a Shared Code Library
- Using UML Lab (UML diagramming tool)
  - Setting the preferences for UML Lab <== DO THIS BEFORE ANY CODING!
- Debugging in Eclipse
Graphical User Interfaces (GUIs):
- Java GUI programming
  - serialVersionUID warning
- Basic Animations in Java
Model-View-Controller ("MVC") Design Pattern
- MVC general discussion
  - Adapter Design Pattern
- Easy MVC Creation using Anonymous Inner Classes
Inner Classes:
- Java Tutorial on Nested and Inner Classes
  - Another tutorial: Building an Application: Part 5: Writing Objects to Files, Using String Arrays, and More on GUI Components
- The Essence of OOP using Java, Anonymous Classes (web article)
- Anonymous inner class (advanced) technques
- Connexions Module on Inner Classes (requires that you understand the Visitor Design Pattern, which is covered later in this course)

See the "Eclipse/Using Subclipse" reference links above! The discussion below continues on those pages.

Why use source control?

Safety
- Your code is stored on a remote server that is backed up regularly
- Your development history is preserved
  - You can view a previous version of your work
  - You can "roll back" your work to a previous version
Coordination
- Multiple people can work on the same project without stomping on each other's code.
- Code updates from one person are quickly and easily transmitted to everyone else in the group.
Convenience
- No need to explicitly turn in your work -- your last commit or tag is your turned-in assignment.
- The staff, who has access to all student repositories, can easily obtain and work with your code without having to send anything though e-mails or dropboxes.