Directory structure and source organization

A W4 Toolkit application is a web application and has therefore a directory structure that complies to that specified in the Java Servlet specification. One of the advantages of this is that you can easily deploy your application to an application server. W4T Eclipse provides an export wizard for that task. The wizard packages your application, along with some further files (libraries, images etc.) needed by W4 Toolkit, and creates a web application archive (.war) file from it.

The proceedings of this are described in detail in the Examples Guide.

The directory structure of the example application contains:

WEB-INF/classes/ the compiled classes of the web application (specified directory)
WEB-INF/conf/ contains files for configuration, like the W4Toolkit configuration file W4T.xml and configuration files used by components like the CMenu and CToolBar (look here for more info).
WEB-INF/lib/ the libraries used by the application (when run in an application server)
src/ the sources of the example application reside here
data/ contains the data files of the example application (we use a simple XML binding)

Sources are divided into the following packages (all below com.mycorp):

common access point from which the user interface gets data
common.data data beans
gui WebForms and WebPanels that are created using W4T Eclipse.
This is everything the user interface consists of. All classes in this package can be edited visually with W4T Eclipse. They trigger the commands which are contained in the commands subpackage from their event handlers.
gui.commands the command implementations that are used by the gui to control the business logic
gui.components some classes that extend standard widgets in order to provide special functionality to them. This is needed primarily for the data binding.
gui.tree contains the TreeViewer implementation of the Reusable Components tutorial, along with customized content provider and label provider implementations needed in the example application.

Copyright (c) 2003 by Innoopract Informationssysteme GmbH. All rights reserved.