Home | Trees | Indices | Help |
|
---|
|
object --+ | IAcceptCriterion
Criterion that can be used create policy to accept/discard dragged
content (presented by Transferable
).
The drag and drop mechanism will verify the criteria returned by DropHandler.getAcceptCriterion
before calling DropHandler.drop
.
The criteria can be evaluated either on the client (browser - see ClientSideCriterion) or on the server (see ServerSideCriterion). If no constraints are needed, an AcceptAll can be used.
In addition to accepting or rejecting a possible drop, criteria can provide additional hints for client side painting.
DropHandler
,
ClientSideCriterion,
ServerSideCriterion
|
|||
|
|||
|
|||
|
|||
|
|||
Inherited from |
|
|||
Inherited from |
|
Validates the data in event to be appropriate for the Note that even if your criterion is validated on client side, you should always validate the data on server side too. |
Returns whether the criteria can be checked on the client or whether a server request is needed to check the criteria. This requirement may depend on the state of the criterion (e.g. logical operations between criteria), so this cannot be based on a marker interface. |
This needs to be implemented iff criterion does some lazy server side initialization. The UIDL painted in this method will be passed to client side drop handler implementation. Implementation can assume that accept is called before this method. |
Home | Trees | Indices | Help |
|
---|
Generated by Epydoc 3.0.1 on Sat Jul 6 19:32:51 2013 | http://epydoc.sourceforge.net |