Home | Trees | Indices | Help |
|
---|
|
object --+ | event.dd.acceptcriteria.accept_criterion.IAcceptCriterion --+ | event.dd.acceptcriteria.server_side_criterion.ServerSideCriterion --+ | TableDropCriterion
Lazy loading accept criterion for Table. Accepted target rows are loaded from server once per drag and drop operation. Developer must override one method that decides on which rows the currently dragged data can be dropped.
Initially pretty much no data is sent to client. On first required criterion check (per drag request) the client side data structure is initialized from server and no subsequent requests requests are needed during that drag and drop operation.
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
Inherited from Inherited from |
|
|||
Inherited from |
|
x.__init__(...) initializes x; see help(type(x)) for signature
|
|
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.
|
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 Apr 20 16:01:27 2013 | http://epydoc.sourceforge.net |