Permalink
Browse files

Moved functional CSS comment into resuable note.

  • Loading branch information...
1 parent 6c710f7 commit 21606fa5283c3c9d553e21bc1198bee9bd26e9ea @scottgonzalez scottgonzalez committed Aug 22, 2012
View
@@ -17,10 +17,9 @@
]]></pre>
<p>Accordions support arbitrary markup, but each content panel must always be the next sibling after its associated header. See the <a href="#option-header"><code>header</code></a> option for information on how to use custom markup structures.</p>
- <p>The panels can be activated programmatically by setting the <a href="#option-active"><code>active</code></a> option..</p>
-
- <p>This widget requires some functional CSS, otherwise it won't work. If you build a custom theme, use the widget's specific CSS file as a starting point.</p>
+ <p>The panels can be activated programmatically by setting the <a href="#option-active"><code>active</code></a> option.</p>
</longdesc>
+ <note id="functional-css"/>
<added>1.0</added>
<options>
<option name="active" default="0">
View
@@ -9,9 +9,8 @@
<p>This can be used to choose previously selected values, such as entering tags for articles or entering email addresses from an address book. Autocomplete can also be used to populate associated information, such as entering a city name and getting the zip code.</p>
<p>You can pull data in from a local or remote source: Local is good for small data sets, e.g., an address book with 50 entries; remote is necessary for big data sets, such as a database with hundreds or millions of entries to select from. To find out more about customizing the data soure, see the documentation for the <a href="#option-source"><code>source</code></a> option.</p>
-
- <p>This widget requires some functional CSS, otherwise it won't work. If you build a custom theme, use the widget's specific CSS file as a starting point.</p>
</longdesc>
+ <note id="functional-css"/>
<added>1.8</added>
<options>
<option name="appendTo" type="Selector" default='"body"'>
View
@@ -11,9 +11,8 @@
<p>In order to group radio buttons, Button also provides an additional widget, called Buttonset. Buttonset is used by selecting a container element (which contains the radio buttons) and calling <code>.buttonset()</code>. Buttonset will also provide visual grouping, and therefore should be used whenever you have a group of buttons. It works by selecting all descendants and applying <code>.button()</code> to them. You can enable and disable a button set, which will enable and disable all contained buttons. Destroying a button set also calls each button's <code>destroy</code> method.</p>
<p>When using an input of type button, submit or reset, support is limited to plain text labels with no icons.</p>
-
- <p>This widget requires some functional CSS, otherwise it won't work. If you build a custom theme, use the widget's specific CSS file as a starting point.</p>
</longdesc>
+ <note id="functional-css"/>
<added>1.8</added>
<options>
<xi:include href="../includes/widget-disabled.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
View
@@ -48,9 +48,8 @@
<code>$.datepicker.setDefaults($.datepicker.regional[""]);</code>
<p>And can then override an individual datepicker for a specific locale:</p>
<code>$(selector).datepicker($.datepicker.regional['fr']);</code>
-
- <p>This widget requires some functional CSS, otherwise it won't work. If you build a custom theme, use the widget's specific CSS file as a starting point.</p>
</longdesc>
+ <note id="functional-css"/>
<added>1.0</added>
<options>
<option name="altField" type="Selector, jQuery, Element" default='""'>
View
@@ -9,9 +9,8 @@
<p>If the content length exceeds the maximum height, a scrollbar will automatically appear.</p>
<p>A bottom button bar and semi-transparent modal overlay layer are common options that can be added.</p>
-
- <p>This widget requires some functional CSS, otherwise it won't work. If you build a custom theme, use the widget's specific CSS file as a starting point.</p>
</longdesc>
+ <note id="functional-css"/>
<added>1.0</added>
<options>
<option name="autoOpen" default="true">
View
@@ -29,9 +29,8 @@
<p>If you use a structure other than <code>&lt;ul></code>/<code>&lt;li></code>, including using the same element for the menu and the menu items, use the <a href="#option-menus"><code>menus</code></a> option to specify a way to differentiate the two elements, e.g., <code>menus: "div.menuElement"</code>.</p>
<p>Any menu item can be disabled by adding the <code>ui-state-disabled</code> class to that element.</p>
-
- <p>This widget requires some functional CSS, otherwise it won't work. If you build a custom theme, use the widget's specific CSS file as a starting point.</p>
</longdesc>
+ <note id="functional-css"/>
<added>1.9</added>
<options>
<xi:include href="../includes/widget-disabled.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
View
@@ -10,9 +10,8 @@
<p>
This is a determinate progress bar, meaning that it should only be used in situations where the system can accurately update the current status. A determinate progress bar should never fill from left to right, then loop back to empty for a single process &#8212; if the actual status cannot be calculated, an indeterminate progress bar or spinner animation is a better way to provide user feedback.
</p>
-
- <p>This widget requires some functional CSS, otherwise it won't work. If you build a custom theme, use the widget's specific CSS file as a starting point.</p>
</longdesc>
+ <note id="functional-css"/>
<added>1.6</added>
<options>
<xi:include href="../includes/widget-disabled.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
View
@@ -6,8 +6,8 @@
<longdesc>
<p>The jQuery UI Resizable plugin makes selected elements resizable (meaning they have draggable resize handles). You can specify one or more handles as well as min and max width and height.</p>
<p>All callbacks (start,stop,resize) receive two arguments: The original browser event and a prepared ui object.</p>
- <p>This interaction requires some functional CSS, otherwise it won't work. If you build a custom theme, use the interaction's specific CSS file as a starting point.</p>
</longdesc>
+ <note id="functional-css"/>
<added>1.0</added>
<options>
<option name="alsoResize" default='false'>
View
@@ -5,9 +5,8 @@
<desc>Use the mouse to select individual or a group of elements</desc>
<longdesc>
<p>The jQuery UI Selectable plugin allows for elements to be selected by dragging a box (sometimes called a lasso) with the mouse over the elements. Also, elements can be selected by click or drag while holding the Ctrl/Meta key, allowing for multiple (non-contiguous) selections.</p>
-
- <p>This interaction requires some functional CSS, otherwise it won't work. If you build a custom theme, use the interaction's specific CSS file as a starting point.</p>
</longdesc>
+ <note id="functional-css"/>
<added>1.0</added>
<options>
<option name="autoRefresh" default='true'>
View
@@ -7,9 +7,8 @@
<p>The jQuery UI Slider plugin makes selected elements into sliders. There are various options such as multiple handles and ranges. The handle can be moved with the mouse or the arrow keys.</p>
<p>The slider widget will create handle elements with the class <code>ui-slider-handle</code> on initialization. You can specify custom handle elements by creating and appending the elements and adding the <code>ui-slider-handle</code> class before initialization. It will only create the number of handles needed to match the length of <a href="#option-value"><code>value</code></a>/<a href="#option-values"><code>values</code></a>. For example, if you specify <code>values: [ 1, 5, 18 ]</code> and create one custom handle, the plugin will create the other two.</p>
-
- <p>This widget requires some functional CSS, otherwise it won't work. If you build a custom theme, use the widget's specific CSS file as a starting point.</p>
</longdesc>
+ <note id="functional-css"/>
<added>1.5</added>
<options>
<option name="animate" default="false">
View
@@ -7,9 +7,8 @@
</desc>
<longdesc>
<p>Spinner wraps a text input, adds two buttons to increment and decrement the current value, along with handling key events for the same purpose. It delegates to <a href="https://github.com/jquery/globalize">Globalize</a> for number formatting and parsing.</p>
-
- <p>This widget requires some functional CSS, otherwise it won't work. If you build a custom theme, use the widget's specific CSS file as a starting point.</p>
</longdesc>
+ <note id="functional-css"/>
<added>1.9</added>
<options>
<option name="culture" default="null">
View
@@ -7,9 +7,8 @@
<p>Tabs are generally used to break content into multiple sections that can be swapped to save space, much like an accordion.</p>
<p>The content for each tab panel can be defined in-page or can be loaded via Ajax; both are handled automatically based on the <code>href</code> of the anchor associated with the tab. By default tabs are activated on click, but the events can be changed to hover via the <a href="#option-event"><code>event</code></a> option.</p>
-
- <p>This widget requires some functional CSS, otherwise it won't work. If you build a custom theme, use the widget's specific CSS file as a starting point.</p>
</longdesc>
+ <note id="functional-css"/>
<added>1.0</added>
<options>
<option name="active" default="0">
View
@@ -15,9 +15,8 @@
<p>A fade animation is used by default to show and hide the tooltip, making the appearance a bit more organic, compared to just toggling the visiblity. This can be customized with the <a href="#option-show"><code>show</code></a> and <a href="#option-hide"><code>hide</code></a> options.</p>
<p>The <a href="#option-items"><code>items</code></a> and <a href="#option-content"><code>content</code></a> options need to stay in-sync. If you change one of them, you need to change the other.</p>
-
- <p>This widget requires some functional CSS, otherwise it won't work. If you build a custom theme, use the widget's specific CSS file as a starting point.</p>
</longdesc>
+ <note id="functional-css"/>
<added>1.9</added>
<options>
<option name="content" default="function returning the title attribute">
View
@@ -1,6 +1,7 @@
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:import href="entries2html-base.xsl"/>
+<xsl:import href="notes.xsl"/>
<xsl:template name="example-code">
&lt;!doctype html&gt;
View
@@ -0,0 +1,9 @@
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
+<xsl:template name="note">
+ <xsl:choose>
+ <xsl:when test="@id = 'functional-css'">
+ This widget requires some functional CSS, otherwise it won't work. If you build a custom theme, use the widget's specific CSS file as a starting point.
+ </xsl:when>
+ </xsl:choose>
+</xsl:template>
+</xsl:stylesheet>

0 comments on commit 21606fa

Please sign in to comment.