Class MasterDetailsBlock
The master part is responsible for adding itself as a form part and firing selection events. The details part catches the selection events and tries to load a page registered to handle the selected object(s). The page shows the details of the selected object(s) and allows users to edit them.
Details pages can be registered statically using 'registerPage' or dynamically through the use of 'IDetailsPageProvider' in case where different pages need to be shown for objects of the same type depending on their state.
Subclasses are required to implement abstract methods of this class. Master part must be created and at least one details page should be registered in order to show details of the objects selected in the master part. Tool bar actions can be optionally added to the tool bar manager.
- Since:
- 3.0
- See Also:
- 
Field SummaryFieldsModifier and TypeFieldDescriptionprotected DetailsPartDetails part created by the block.protected SashFormThe form that is the parent of both master and details part.
- 
Constructor SummaryConstructors
- 
Method SummaryModifier and TypeMethodDescriptionprotected voidapplyLayout(Composite parent) Applies layout to the parent composite of the master/details block.protected voidapplyLayoutData(SashForm sashForm) Applies layout data to the sash form containing master and detail parts of the master/details block.voidcreateContent(IManagedForm managedForm) Creates the content of the master/details block inside the managed form.voidcreateContent(IManagedForm managedForm, Composite parent) Creates the content of the master/details block inside the parent composite.protected abstract voidcreateMasterPart(IManagedForm managedForm, Composite parent) Implement this method to create a master part in the provided parent.protected abstract voidcreateToolBarActions(IManagedForm managedForm) Implement this method to create form tool bar actions and add them to the form tool bar if desired.protected abstract voidregisterPages(DetailsPart detailsPart) Implement this method to statically register pages for the expected object types.
- 
Field Details- 
detailsPartDetails part created by the block. No attempt should be made to access this field insidecreateMasterPartbecause it has not been created yet and will benull.
- 
sashFormThe form that is the parent of both master and details part. The form allows users to change the ratio between the two parts.
 
- 
- 
Constructor Details- 
MasterDetailsBlockpublic MasterDetailsBlock()
 
- 
- 
Method Details- 
createContentCreates the content of the master/details block inside the managed form. This method should be called as late as possible inside the parent part.- Parameters:
- managedForm- the managed form to create the block in
 
- 
createContentCreates the content of the master/details block inside the parent composite. This method should be called as late as possible inside the parent part.- Parameters:
- managedForm- the managed form to create the block in
- Since:
- 3.4
 
- 
applyLayoutDataApplies layout data to the sash form containing master and detail parts of the master/details block.The default implementation fills the whole parent composite area. Override this method if master/details block is to be placed on a form along with other components. Implementations that override this method should also override applyLayout(Composite)method implementation.- Parameters:
- sashForm- The sash form to be laid out on the parent composite.
- Since:
- 3.4
- See Also:
 
- 
applyLayoutApplies layout to the parent composite of the master/details block.The default implementation fills the whole parent composite area. Override this method if master/details block is to be placed on a form along with other components. Implementations that override this method should also override applyLayoutData(SashForm)method implementation.- Parameters:
- parent- parent composite for the master/details block
- Since:
- 3.4
- See Also:
 
- 
createMasterPartImplement this method to create a master part in the provided parent. Typical master parts are section parts that contain tree or table viewer.- Parameters:
- managedForm- the parent form
- parent- the parent composite
 
- 
registerPagesImplement this method to statically register pages for the expected object types. This mechanism can be used when there is 1->1 mapping between object classes and details pages.- Parameters:
- detailsPart- the details part
 
- 
createToolBarActionsImplement this method to create form tool bar actions and add them to the form tool bar if desired.- Parameters:
- managedForm- the form that owns the tool bar
 
 
-