data.stdforms.singletableformsheet
Class EditButtonStrategy
java.lang.Object
|
+--sale.stdforms.FormSheetStrategy
|
+--data.stdforms.singletableformsheet.EditButtonStrategy
- Direct Known Subclasses:
- AbstractAddCatalogItemStrategy, DefaultRemoveCatalogItemStrategy
- public abstract class EditButtonStrategy
- extends FormSheetStrategy
Abstract super class for strategies that can be associated with the
"Add" and the
"Remove" button of a SingleTableFormSheet
.
The strategy defines a sub-process that can be integrated into the process that displayed the FormSheet
to perform the editing.
- Hooks:
- Define New Strategy For Add Or Remove Button
- Since:
- v2.0
- Version:
- 2.0 20/08/1999
- Author:
- Steffen Zschaler
- See Also:
- Serialized Form
Methods inherited from class java.lang.Object |
clone,
equals,
finalize,
getClass,
hashCode,
notify,
notifyAll,
toString,
wait,
wait,
wait |
EditButtonStrategy
public EditButtonStrategy()
getEditProcess
public abstract Transition getEditProcess(SingleTableFormSheet stfs,
SaleProcess p,
SalesPoint sp)
- Get the first transition of the process that will perform the editing. The process can have any number of
Gates and Transitions and display any number of Form-
and MenuSheets. Normally, the sub-process should end at the gate at which the
SingleTableFormSheet is being displayed, which can be obtained by
SingleTableFormSheet.getGate().
- Override:
- Always.
- Parameters:
stfs
- the SingleTableFormSheet that triggers the sub-process.p
- the process into which the sub-process will be implanted.sp
- the SalesPoint at which the FormSheet is displayed, if any.- Hooks:
- Define New Strategy For Add Or Remove Button