[
https://issues.jboss.org/browse/RFPL-1035?page=com.atlassian.jira.plugin....
]
Anton Belevich commented on RFPL-1035:
--------------------------------------
<rich:dragBehavior> now is <rich:dragSource>. It has the following attributes:
dragIndicator, type, dragValue.
The dragIndicator parameter accepts a id of <rich:dragIndicator> component.
<rich:dropBehavior> is renamed to <rich:dragTarget>. It has the following
attributes: dropValue, acceptedType.
acceptedType can take a "@none" - this means that no type will be accepted
."null" value works the same as @none.
The value @all makes all types be acceptable.
Default value for acceptedType attribute is "null".
DropEvent now has a only tree parameters: dragSource, dragValue, dropValue
<rich:dragIndicator> has 3 attributes: acceptClass, rejectClass, draggingClass .
These attributes define a css classes which applied to indicator in different state in
regard to dragTarget component position on the page.
Drag-n-drop: documentation review
---------------------------------
Key: RFPL-1035
URL:
https://issues.jboss.org/browse/RFPL-1035
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: components, doc
Affects Versions: 4.0.0.Milestone5
Reporter: Sean Rogers
Assignee: Anton Belevich
Fix For: 4.0.0.Milestone6
Please review the documentation:
http://docs.jboss.org/richfaces/nightly_4_0_X/Component_Reference/en-US/h...
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira