Table of Contents 
Previous Section
Developing a WebObjects Application
Developing a WebObjects application is a matter of creating your templates, bindings, and code files and, if your application uses Java Client, your interface files. Although these files are text based and thus could be created using a text editor, WebObjects provides graphical tools that simplify the entire process. The primary tools you use when developing WebObjects applications are:
- Project Builder. As its name implies, Project Builder manages all of the constituent parts of your application, including source code files, WebObjects components, frameworks, makefiles, graphics and sound files, and the like. It is from within Project Builder that you edit your code files, compile, debug, and launch your application for development testing. Project Builder's wizards help you to create new WebObjects components. You also can launch the other development tools from within Project Builder.
- WebObjects Builder. You use WebObjects Builder to edit your application's components. WebObjects Builder allows you to graphically edit a component's HTML template. If you prefer, you can switch to "raw mode," from which you can edit the template as an HTML text file. WebObjects Builder also allows you to graphically bind the dynamic elements on your template to variables and methods within your code.
- EOModeler. EOModeler maintains the mapping between your enterprise objects and your database schema. It presents you with the tables and columns within your database and allows you to establish relationships between them. EOModeler maintains an EOModel file, which your application then uses to determine how enterprise data is to be stored and retrieved to the data store.
- Interface Builder. This is a graphical tool that you use to create Java Client interfaces. It not only allows you to visually lay out your interface, it also allows you to graphically make connections between your code and your interface elements.
Table of Contents 
Next Section