HOWTO Instructions for BeanView

This section is intended to give you tips on where to go/look to accomplish certain tasks.

Add A New User Interface Framework

BeanView implements support for Swing and Echo 2.0.  There are a huge number of user interface frameworks currently available, including SWT, Struts, JSF, WebWork, Wicket, and countless others. To implement support for a new web framework, you will want to do the following:

  1. Implement a new container object in the target framework that implements the BeanView interface. For example, for Swing this looks something like this:
    SwingBeanViewPanel<V> extends javax.swing.JPanel implements BeanView {...}
  2. The vast majority of the interface is already implemented for you via the BeanViewHelper class. You will want to implement additional details as relevant for your particular web framework. For example, the SwingBeanViewPanel implementation uses a GridBagLayout, and adds some convenience methods for setting the formatting of this layout.
  3. Your implementation of the BeanView interface should rely on the ComponentFactory pattern (e.g. com.beanview.swing.SwingComponentFactory) and the various com.beanview.PropertyComponentFactory classes for supported component types. See the graphic below.
  4. The PropertyComponentFacory classes in turn make use of com.beanview.PropertyComponent implementations. i.e. the returned entry component should be an implementation of the com.beanview.PropertyComponent interface.
  5. Create subclasses of the unit tests in the test directory com.beanview.base for your framework. As the framework evolves, more unit tests will be added to clarify behavior, so you will want to make sure that you are updating frequently and implementing all of the unit tests properly.

BeanView Subclass Configure Implementation Overview

Return to http://www.beanview.com/

@author $Author: wiverson $
@version $Revision: 1.2 $, $Date: 2006/08/12 01:31:14 $