Entries: Make deprecations more useful

Ref 09d05eb
Fixes gh-261

Author: jzaefferer

entries/dialog.xml

@@ -142,7 +142,10 @@
 			<type name="String" />
 		</option>
 		<option name="dialogClass" default='""' example-value='"alert"' deprecated="1.12">
-			<desc>The specified class name(s) will be added to the dialog, for additional theming.</desc>
+			<desc>
+				<p>The specified class name(s) will be added to the dialog, for additional theming.</p>
+				<p>The <code>dialogClass</code> option has been deprecated in favor of the <a href="#option-classes"><code>classes</code> option</a>, using the <code>ui-dialog</code> property.</p>
+			</desc>
 			<type name="String" />
 		</option>
 		<option name="draggable" default="true" example-value="false">

entries/droppable.xml

@@ -30,7 +30,10 @@
 			</type>
 		</option>
 		<option name="activeClass" type="String" default="false" example-value='"ui-state-highlight"' deprecated="1.12">
-			<desc>If specified, the class will be added to the droppable while an acceptable draggable is being dragged.</desc>
+			<desc>
+				<p>If specified, the class will be added to the droppable while an acceptable draggable is being dragged.</p>
+				<p>The <code>activeClass</code> option has been deprecated in favor of the <a href="#option-classes"><code>classes</code> option</a>, using the <code>ui-droppable-active</code> property.</p>
+			</desc>
 		</option>
 		<option name="addClasses" type="Boolean" default="true" example-value="false">
 			<desc>If set to <code>false</code>, will prevent the <code>ui-droppable</code> class from being added. This may be desired as a performance optimization when calling <code>.droppable()</code> init on hundreds of elements.</desc>
@@ -44,7 +47,10 @@
 			<desc>By default, when an element is dropped on nested droppables, each droppable will receive the element. However, by setting this option to <code>true</code>, any parent droppables will not receive the element. The <code>drop</code> event will still bubble normally, but the <code>event.target</code> can be checked to see which droppable received the draggable element.</desc>
 		</option>
 		<option name="hoverClass" type="String" default="false" example-value='"drop-hover"' deprecated="1.12">
-			<desc>If specified, the class will be added to the droppable while an acceptable draggable is being hovered over the droppable.</desc>
+			<desc>
+				<p>If specified, the class will be added to the droppable while an acceptable draggable is being hovered over the droppable.</p>
+				<p>The <code>hoverClass</code> option has been deprecated in favor of the <a href="#option-classes"><code>classes</code> option</a>, using the <code>ui-droppable-hover</code> property.</p>
+			</desc>
 		</option>
 		<option name="scope" type="String" default='"default"' example-value='"tasks"'>
 			<desc>Used to group sets of draggable and droppable items, in addition to the <a href="#option-accept"><code>accept</code></a> option. A draggable with the same scope value as a droppable will be accepted.</desc>

entries/tooltip.xml

@@ -85,8 +85,8 @@
 		<xi:include href="../includes/widget-option-show.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
 		<option name="tooltipClass" default="null" example-value='"custom-tooltip-styling"' deprecated="1.12">
 			<desc>
-				A class to add to the widget, can be used to display various tooltip types, like warnings or errors.
-				<p>This may get replaced by the <a href="http://bugs.jqueryui.com/ticket/7053">classes option</a>.</p>
+				<p>A class to add to the widget, can be used to display various tooltip types, like warnings or errors.</p>
+				<p>The <code>tooltipClass</code> option has been deprecated in favor of the <a href="#option-classes"><code>classes</code> option</a>, using the <code>ui-tooltip</code> property.</p>
 			</desc>
 			<type name="String" />
 		</option>