link fixes

.gitignore

@@ -11,6 +11,3 @@
 
 # MacOS directory store
 .DS_Store
-
-# local playground
-skins

archive/scrollable-1.0.0.html

@@ -16,9 +16,9 @@ <h2>New Features</h2>
 
 
 <ul>
-	<li>now it's possible to add/remove items from scrollable using standard jQuery methods. <a href="demos/scrollable/edit.html">see demo</a></li>
-	<li>automatic action generation for "next page" and "prev page". <a href="demos/scrollable/navigation.html#pagescroll">see demo</a> </li>
-	<li>interval option to automatically step through elements in specified intervals. <a href="demos/scrollable/autoscroll.html">see demo</a>  </li>
+	<li>now it's possible to add/remove items from scrollable using standard jQuery methods. <a href="${jqt}/demos/scrollable/edit.html">see demo</a></li>
+	<li>automatic action generation for "next page" and "prev page". <a href="${jqt}/demos/scrollable/navigation.html#pagescroll">see demo</a> </li>
+	<li>interval option to automatically step through elements in specified intervals. <a href="${jqt}/demos/scrollable/autoscroll.html">see demo</a>  </li>
 	<li>next/prev links can now be hidden (or styled) when they are not active using <samp>disabledClass</samp> configuration option </li>
 	<li><samp>hoverClass</samp> for styling elements upon mouseover event</li>
 	<li>new event handler <samp>onBeforeSeek</samp> which is triggered before seeking occurs. returning false here cancels seeking</li>
@@ -73,7 +73,7 @@ <h3>New HTML layout</h3>
 </pii:code>
 
 <p>
-	And those wrappers must be styled according to the rules specified in <a href="demos/scrollable/index.html">minimal setup</a> demo. Previous version did some dirty work on the background and added an extra wrapper element automatically to achieve scrolling. This was a good thing for non- programmers but bad for serious programmers who doesn't like dirty tricks they do not understand. Now everything is "open" and understandable.
+	And those wrappers must be styled according to the rules specified in <a href="${jqt}/demos/scrollable/index.html">minimal setup</a> demo. Previous version did some dirty work on the background and added an extra wrapper element automatically to achieve scrolling. This was a good thing for non- programmers but bad for serious programmers who doesn't like dirty tricks they do not understand. Now everything is "open" and understandable.
 </p>
 
 <h3>Navigational elements as siblings</h3>

documentation/basics.html

@@ -208,7 +208,7 @@ <h3><em>1.</em> CSS-based design</h3>
 </ul>
 
 <p>
-	There are lots of new features in the latest CSS version such as rounded borders, gradient borders, shadows and opacity, but these are not yet supported by every major browser. Some of the demos on this site uses these CSS3 features. If you are using Firefox&nbsp;3.5, Safari&nbsp;4.0 or other CSS3 compatible browser please take a look at the <a href="demos/combine/scrollable-gallery-with-tooltips.html">scrollable gallery with tooltips</a> demo and click on the thumbnails. You'll see nice looking drop shadows on the overlay. As you can see you can create stunning looks by only using CSS and the design will also be well-behaved in older browsers.
+	There are lots of new features in the latest CSS version such as rounded borders, gradient borders, shadows and opacity, but these are not yet supported by every major browser. Some of the demos on this site uses these CSS3 features. If you are using Firefox&nbsp;3.5, Safari&nbsp;4.0 or other CSS3 compatible browser please take a look at the <a href="${jqt}/demos/combine/scrollable-gallery-with-tooltips.html">scrollable gallery with tooltips</a> demo and click on the thumbnails. You'll see nice looking drop shadows on the overlay. As you can see you can create stunning looks by only using CSS and the design will also be well-behaved in older browsers.
 </p>
 
 
@@ -315,7 +315,7 @@ <h4>PNG24 and opacity in all versions of IE</h4>
 </p>
 
 <p>
-	This "black box" bug can also happen in situations where a PNG image is placed on top of a transparent layer. I noticed this happening in <a href="demos/combine/scrollable-gallery-with-tooltips.html">this demo</a>.
+	This "black box" bug can also happen in situations where a PNG image is placed on top of a transparent layer. I noticed this happening in <a href="${jqt}/demos/combine/scrollable-gallery-with-tooltips.html">this demo</a>.
 </p>
 
 <!--}}}-->

index.html

@@ -21,7 +21,7 @@
 
 <script>$(function() { $("#jqt1").addClass("active"); });</script>
 
-<%@ include file="demos/scrollable/home.htm" %>
+<%@ include file="${jqt}/demos/scrollable/home.htm" %>
 
 <a id="tease" href="release-notes/"></a>
 

tabs/index.html

@@ -249,9 +249,9 @@ <h4><em>2<sup>nd</sup> argument:</em> configuration</h4>
 			<ul>
 				<li><samp>'default'</samp>: a simple show/hide effect. The default behaviour for tabs.</li>
 				<li><samp>'fade'</samp>: the tab contents are gradually shown from zero to full opacity.</li>
-				<li><samp>'ajax'</samp>: loads tab contents from the server using AJAX. <a href="demos/tabs/ajax.html">View example</a>.</li>
-				<li><samp>'slide'</samp>: a vertical sliding effect, suitable for <a href="demos/tabs/accordion.html">accordions</a>.</li>
-				<li><samp>'horizontal'</samp>: a horizontal sliding effect, suitable for <a href="demos/tabs/accordion-horizontal.html">horizontal accordions</a>.</li>
+				<li><samp>'ajax'</samp>: loads tab contents from the server using AJAX. <a href="${jqt}/demos/tabs/ajax.html">View example</a>.</li>
+				<li><samp>'slide'</samp>: a vertical sliding effect, suitable for <a href="${jqt}/demos/tabs/accordion.html">accordions</a>.</li>
+				<li><samp>'horizontal'</samp>: a horizontal sliding effect, suitable for <a href="${jqt}/demos/tabs/accordion-horizontal.html">horizontal accordions</a>.</li>
 			</ul>
 
 			<p>
@@ -277,7 +277,7 @@ <h4><em>2<sup>nd</sup> argument:</em> configuration</h4>
 		<td class="code">fadeOutSpeed</td>
 		<td><code>0</code></td>
 		<td>
-			<strong>Since 1.1.0.</strong> Only available when used together with the "fade" effect. This property defines how fast (in milliseconds) the opened pane hides its content. A positive value here will result in a cool "crossfade" effect which is demonstrated in this <a href="#slideshow">slideshow demo</a>.
+			<strong>Since 1.1.0.</strong> Only available when used together with the "fade" effect. This property defines how fast (in milliseconds) the opened pane hides its content. A positive value here will result in a "crossfade" effect which is demonstrated <a href="slideshow.html">here</a>.
 		</td>
 	</tr>
 	<tr>
@@ -299,7 +299,7 @@ <h4><em>2<sup>nd</sup> argument:</em> configuration</h4>
 		<td class="code">rotate</td>
 		<td><code>false</code></td>
 		<td>
-			<strong>Since 1.1.0.</strong> When the last tab is open and the <samp>next()</samp> API call is invoked, then the tabs will start from the beginning and when the first tab is open and the <samp>prev()</samp> call is invoked the tabs will advance to the last tab. This is demonstrated in the <a href="#slideshow">slideshow demo</a>.
+			<strong>Since 1.1.0.</strong> When the last tab is open and the <samp>next()</samp> API call is invoked, then the tabs will start from the beginning and when the first tab is open and the <samp>prev()</samp> call is invoked the tabs will advance to the last tab. This is demonstrated in <a href="slideshow.html">here</a>.
 		</td>
 	</tr>
 	<tr>
@@ -364,7 +364,7 @@ <h3>Initializing multiple Tabs</h3>
 </pii:code>
 
 <p>
-	With accordion setups you typically have a common root element for both the tabs and the panes so there is no need for a separate wrapper element. You should take a look at the demo about <a href="demos/tabs/multiple.html">Multiple Tabs and Accordion instances</a>.
+	With accordion setups you typically have a common root element for both the tabs and the panes so there is no need for a separate wrapper element. You should take a look at the demo about <a href="${jqt}/demos/tabs/multiple.html">Multiple Tabs and Accordion instances</a>.
 </p>
 
 

toolbox/expose.html

@@ -95,7 +95,7 @@ <h3>Expose and Flowplayer demos</h3>
 <a name="graphics"></a>
 <c:set var="description">
 	<p>
-		These graphics are being used as the mask's background image. JPG versions are smaller, but they have a fixed background color. PNG images are larger, but you can use any background color in them. Here is a <a href="demos/expose/styling.html">cool example</a> where the mask's background image has been changed.
+		These graphics are being used as the mask's background image. JPG versions are smaller, but they have a fixed background color. PNG images are larger, but you can use any background color in them. Here is a <a href="${jqt}/demos/expose/styling.html">cool example</a> where the mask's background image has been changed.
 	</p>
 </c:set>
 

toolbox/flashembed.html

@@ -164,15 +164,15 @@ <h3><span class="blue">2nd argument: </span> configuration</h3>
 			</p>
 
 			<p>
-				If this is specified and the user's Flash version is greater than <samp>[6, 65]</samp>, then this plugin attempts to install Flash on-the-fly. You can learn more with <a href="demos/flashembed/fail.html">this demo</a>.
+				If this is specified and the user's Flash version is greater than <samp>[6, 65]</samp>, then this plugin attempts to install Flash on-the-fly. You can learn more with <a href="${jqt}/demos/flashembed/fail.html">this demo</a>.
 			</p>
 		</td>
 	</tr>
 	<tr>
 		<td class="code">onFail</td>
 		<td></td>
 		<td>
-			A JavaScript function that is evaluated when the Flash plugin is missing or its version is too old. You can learn more from <a href="demos/flashembed/fail.html">this demo</a>. This function is called in every possible scenario when and old version is detected. Inside the function the <samp>this</samp> variable is a pointer to the <a href="#api">flashembed API</a>.
+			A JavaScript function that is evaluated when the Flash plugin is missing or its version is too old. You can learn more from <a href="${jqt}/demos/flashembed/fail.html">this demo</a>. This function is called in every possible scenario when and old version is detected. Inside the function the <samp>this</samp> variable is a pointer to the <a href="#api">flashembed API</a>.
 		</td>
 	</tr>
 	<tr>
@@ -221,7 +221,7 @@ <h3><span class="blue">2nd argument: </span> configuration</h3>
 		<td class="code">wmode</td>
 		<td class="code">window</td>
 		<td>
-			Set this to "opaque" if you want to place normal HTML elements on top of the Flash object, for example, a dropdown menu. You can find a demo about this <a href="demos/flashembed/wmode.html">here</a>.
+			Set this to "opaque" if you want to place normal HTML elements on top of the Flash object, for example, a dropdown menu. You can find a demo about this <a href="${jqt}/demos/flashembed/wmode.html">here</a>.
 		</td>
 	</tr>
 	<tr>

tooltip/index.html

@@ -380,7 +380,7 @@ <h3>Event management</h3>
 </pii:code>
 
 <p>
-	Here is a <a href="demos/tooltip/form.html">demo</a> that shows you the various event types in action.
+	Here is a <a href="${jqt}/demos/tooltip/form.html">demo</a> that shows you the various event types in action.
 </p>
 
 <%--{{{ api --%>

validator/index.html

@@ -193,7 +193,9 @@ <h3>HTML5 Attributes</h3>
 	<tr>
 		<td class="code">required</td>
 		<td><code>"required"</code></td>
-		<td>Makes value submission mandatory for this field. The standard syntax is <samp>required="required"</samp>, but this tool allows you to write <samp>required="true"</samp> or simply <samp>required</samp>.</td>
+		<td>
+			Makes value submission mandatory for this field. The standard syntax is <samp>required="required"</samp>, but this tool allows you to write <samp>required="true"</samp> or simply <samp>required</samp>. Works with checkbox and SELECT fields too. 
+		</td>
 	</tr>
 </table>