RubyGems - survivalkit - Versions diffs - 0.3.4 → 1.0.beta.1 - Mend

survivalkit 0.3.4 → 1.0.beta.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1362) hide show

data/templates/project/sources/pie/documentation/q-and-a.html DELETED Viewed

@@ -1,152 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-    <meta content="text/html; charset=UTF-8" http-equiv="content-type">
-    <title>PIE Documentation: Q &amp; A</title>
-</head>
-<body>
-<h1>Q &amp; A</h1>
-<!-- noformat on -->
-<h2>What is PIE?</h2>
-<p>PIE is a utility for Internet Explorer (currently versions 6-8) which gives it the ability to parse
-and render a number of the most useful CSS3 properties.</p>
-<h2>How does it work?</h2>
-<p>PIE is implemented as an attached behavior; in your CSS, you simply specify:</p>
-<pre><code>behavior: url(PIE.htc);</code></pre>
-<p>Once the behavior is attached, it looks for any of the supported CSS3 properties which might be attached to the
-target element, parses those properties, and renders them on the page.</p>
-<h2>What CSS3 properties are currently supported?</h2>
-<p>PIE currently has full or partial support for:</p>
-<ul>
-    <li>border-radius</li>
-    <li>box-shadow</li>
-    <li>border-image</li>
-    <li>multiple background images</li>
-    <li>linear-gradient background images</li>
-</ul>
-<p>You can find detailed information about the levels of support in the
-<a href="/documentation/supported-css3-features/">Supported CSS3 Properties and Values</a> documentation.</p>
-<h2>How large is it?</h2>
-<p>The .htc behavior file is 30K. With gzip compression, it is 12K. (You do gzip your content, right?)</p>
-<p>It's pretty easy to save at least as much as that by using CSS3 instead of all the extra images, markup, and CSS
-you'd have to use otherwise, so this is usually a net win in terms of total page weight. Also, it's important to
-note that the behavior file is only downloaded by IE, so in other browsers which support these CSS3 features natively,
-that's pure win.</p>
-<h2>What are the goals of the project?</h2>
-<p>Even though today's advanced browsers are starting to implement decent levels of CSS3 support, it will still be
-years before Web authors can start using these CSS3 features in widespread deployment. The main reason is, of course,
-that Internet Explorer does not yet implement any of these features, has a majority market share, and has a notoriously
-slow upgrade cycle among its users. IE9 promises to start implementing some CSS3, but like it or not it will still
-likely be years before IE8 and below shrink to a negligible percentage of users.</p>
-<p>PIE aims to drastically shorten that timeframe, by implementing a simple shim to make CSS3 "just work" in IE. Our
-goals are:</p>
-<ol>
-    <li>
-        <h3>Be simple to use</h3>
-        <p>Applying PIE is extremely simple; in many cases the only thing you have to do is add the behavior property
-        to your CSS.</p>
-    </li>
-    <li>
-        <h3>Be a CSS-only solution</h3>
-        <p>Many of the current solutions for implementing CSS3 features like border-radius are implemented as
-        JavaScript libraries and require the author to write JavaScript to invoke them. That is less than ideal
-        because it requires the CSS author to also know how to write JS, and it makes development slower and less
-        maintainable because your styling code is scattered between CSS and JS files. PIE works entirely within the
-        stylesheet, so you only write CSS and it's all in a single place.</p>
-    </li>
-    <li>
-        <h3>Be seamless to the CSS author</h3>
-        <p>There have been several articles and resources in recent months which show ways that you can make IE
-        "mimic" certain CSS3 features, for example using IE filters to fake box-shadow, or jQuery plugins to implement
-        rounded corners. The problem with these solutions is that they require a lot of IE-specific code on top of your
-        real CSS3, increasing your development time and the size of your CSS files. PIE on the other hand uses your
-        CSS3 directly whenever possible; you simply write real CSS3, and PIE handles it seamlessly.</p>
-        <p>PIE handles attaching, detaching, and updating automatically without any intervention from the author. This
-        means that, unlike some other solutions, PIE does not require you to explicitly initialize elements when they
-        are added to or removed from the document via script, and does not require any sort of "update" method to be
-        called when an element's position, size, or styles are modified on the fly.</p>
-        <p>Another aspect of PIE's seamlessness is that it should be fully compatible with any JavaScript library the
-        site author might choose to use. You can create elements and assign CSS3 styles to them in jQuery or YUI or
-        MooTools or any other library and PIE will automatically apply itself. Also, PIE's objects are completely
-        self-contained except for a single global <code>PIE</code> object, so there's no chance that it will
-        override objects or functions from any other JS code.</p>
-    </li>
-    <li>
-        <h3>Be as compliant with the CSS3 specs as possible</h3>
-        <p>PIE aims to be a true CSS3 implementation for those features it supports, complying with the current spec
-        drafts as closely as possible. The goal is to allow authors to write a single set of CSS3 code and have it
-        "just work" between browsers.</p>
-    </li>
-    <li>
-        <h3>Be as performant as possible</h3>
-        <p>If it makes the browser feel sluggish (more so than IE normally does, that is) then it's useless. PIE was
-        architected with performance in mind from the very beginning:</p>
-        <ul>
-            <li>Rendering elements are only updated when they need to be.</li>
-            <li>CSS property values are only parsed when they have changed.</li>
-            <li>Internal objects are created lazily, and cached when appropriate.</li>
-            <li>The behavior script is written with file size in mind, and the most advanced JS compression tools
-            available are used to minimize the file size, so the initial download is as fast as possible.</li>
-        </ul>
-    </li>
-</ol>
-<h2>What sites have used PIE?</h2>
-<p>Here is just a tiny list of sites using PIE already in production. <a href="/contact/">Tell us about yours!</a></p>
-<ul>
-    <li><a href="http://americanapparel.net">American Apparel</a> (<strong><abbr title="Not safe for work">NSFW</abbr></strong>)</li>
-    <li><a href="http://demo.crowdfavorite.com/carrington-business">Carrington Business WordPress Theme</a></li>
-    <li><a href="http://www.composite.net/">Composite C1 CMS</a></li>
-    <li><a href="http://www.journeyoutreach.org/">Journey Outreach</a></li>
-    <li><a href="http://www.lizardq.com/">LizardQ Panoramic Cameras</a></li>
-    <li><a href="http://mirrorstonecrystals.com/">Mirrorstone Crystals</a></li>
-    <li><a href="http://www.blogsouthwest.com/">Nuts About Southwest</a></li>
-    <li><a href="http://oneillrealestate.ca/">O'Neill Real Estate</a></li>
-    <li><a href="http://www.protagonize.com">Protagonize</a></li>
-    <li><a href="http://realti.ca/">Realti.ca</a></li>
-    <li><a href="http://sheffieldismyplanet.co.uk/">Sheffield Is My Planet</a></li>
-    <li><a href="http://www.skillstar.com/">Skillstar</a></li>
-    <li><a href="http://twbasics.keycontent.org/">Tiki for Smarties</a></li>
-    <li><a href="http://www.tinypie.co.uk/">TinyPie Projects</a></li>
-    <li><a href="http://www.tractionco.com/">Traction</a></li>
-    <li><a href="https://www.viaprinto.de/">viaprinto</a></li>
-    <!-- Check these:
-    <li><a href="http://cahealthadvocates.org/">California Health Advocates</a></li>
-    <li><a href="http://www.kleinezeitung.at/">Kleine Zeitung</a></li>
-    <li><a href="http://www.memyteam.com/">me:myteam</a></li>
-    -->
-    <!--<li><a href=""></a></li>-->
-</ul>
-<h2>What are the licensing terms?</h2>
-<p>PIE is licensed under a <a href="http://github.com/lojjic/PIE/blob/master/LICENSE">dual license of Apache License
-Version 2.0 and General Public License (GPL) Version 2</a>.</p>
-<p>While you are welcome to use PIE free of charge, we do ask that you consider making a donation as you are able.
-Development of PIE happens almost exclusively during "free time" on evenings and weekends, so your donations are
-important to help keep this going. Think of the hours of costly, frustrating cross-browser hacking that PIE is saving
-you; if you can donate a small proportion of that it will be greatly appreciated!</p>
-<!-- noformat off -->
-</body>
-</html>

data/templates/project/sources/pie/documentation/supported-css3-features.html DELETED Viewed

@@ -1,402 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-  <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
-  <title>PIE Documentation: Supported CSS3 Features</title>
-</head>
-<body>
-<h1>Supported CSS3 Features</h1>
-<!-- noformat on -->
-<p>The following sections describe in detail the exact levels of support PIE has for certain CSS3 properties
-and value types.</p>
-<ul>
-    <li><a href="#border-radius">border-radius</a></li>
-    <li><a href="#box-shadow">box-shadow</a></li>
-    <li><a href="#border-image">border-image</a></li>
-    <li><a href="#pie-background">CSS3 Backgrounds (-pie-background)</a></li>
-    <li><a href="#gradients">Gradients</a></li>
-    <li><a href="#rgba">RGBA Color Values</a></li>
-    <li><a href="#custom">PIE Custom Properties</a>
-        <ul>
-            <li><a href="#pie-watch-ancestors">-pie-watch-ancestors</a></li>
-            <li><a href="#pie-png-fix">PNG alpha transparency and -pie-png-fix</a></li>
-            <li><a href="#pie-lazy-init">Lazy Initialization (-pie-lazy-init)</a></li>
-            <li><a href="#pie-poll">Layout polling (-pie-poll)</a></li>
-        </ul>
-    </li>
-</ul>
-<h2 id="border-radius">border-radius</h2>
-<p>PIE fully supports the border-radius property as defined in the CSS3
-Backgrounds and Borders module specification.</p>
-<pre class="long">border-radius: [ &lt;length&gt; | &lt;percentage&gt; ]{1,4} [ / [ &lt;length&gt; | &lt;percentage&gt; ]{1,4} ]?</pre>
-<p>Only the shorthand version is supported; the longhand
-border-top-left-radius etc. properties are not. The shorthand syntax does support different radii per corner, though:</p>
-<p><code>border-radius: 5px 10px 15px 20px;</code> (top-left, top-right, bottom-right, bottom-left).</p>
-<p>The rounded corners are applied to the element's background area
-(including solid background colors, background images, and background
-gradients), the element's border, and the box-shadow if specified.</p>
-<p>Both the standard border-radius property name as well as a custom
-prefixed -pie-border-radius property name are recognized; if both are
-present then the prefixed value will take precedence. It is recommended
-to only use the standard unprefixed property when possible (in
-addition, of course, to -moz- and -webkit- prefixed properties as
-necessary), since the CSS3 spec for this property seems fairly
-solidified, and because there are no known incompatibilities between
-PIE's implementation and the standard.</p>
-<p>Notes on other browsers:</p>
-<p>Elliptical radii (the optional set of values after the slash) are
-only supported in Firefox versions 3.5 and up. As of the current
-release (3.6), percentage values for vertical radii are incorrectly
-calculated relative to the width of the box whereas the CSS3 spec says
-they should be relative to the height. PIE handles this correctly.</p>
-<p>WebKit deviates significantly from the CSS3 spec: the shorthand
-property cannot be used to specify different radii per corner, so you
-must use the separate longhand properties if you want to do that. It
-also does not support percentage values at all. (TODO: check this in
-WebKit nightlies and recent Chrome, I think these may now match the
-spec and drop the prefix.)</p>
-<h2 id="box-shadow">box-shadow</h2>
-<p>PIE supports the <a href="http://dev.w3.org/csswg/css3-background/#box-shadow">box-shadow property syntax</a>
-as currently defined in the CSS3 Backgrounds &amp; Borders module.</p>
-<pre class="long">box-shadow: none | &lt;shadow&gt; [,&lt;shadow&gt;]*
-    where &lt;shadow&gt; = inset? &amp;&amp; [ &lt;offset-x&gt; &lt;offset-y&gt; &lt;blur-radius&gt;? &lt;spread-radius&gt;? &amp;&amp; &lt;color&gt;? ]</pre>
-<p>Both the standard box-shadow property name as well as a custom
-prefixed -pie-box-shadow property name are recognized; if both are
-present the prefixed value will take precedence. It is recommended to
-use the non-prefixed property when possible, since there are no known
-incompatibilities between PIE's implementation and others which use the
-non-prefixed property, such as Opera.</p>
-<p>When used in conjunction with border-radius, the shape of the shadow
-matches the shape of the rounded border box.</p>
-<p>When using the blur radius parameter, the strength and size of the
-blur as rendered by PIE should match that of other browsers almost
-identically, however you may notice some slight differences due to
-rounding, particularly when the blur is very small (this should not be
-more than a one-pixel difference).</p>
-<p>PIE does not currently support the 'inset' keyword, but support is
-planned in a future version (see <a href="http://github.com/lojjic/PIE/issues#issue/3">issue #3</a>.</p>
-<p>Notes on other browsers:</p>
-<p>See the compatibility chart at the bottom of
-<a href="https://developer.mozilla.org/En/CSS/-moz-box-shadow">https://developer.mozilla.org/En/CSS/-moz-box-shadow</a></p>
-<h2 id="border-image">border-image</h2>
-<p>PIE has preliminary support for the border-image property. This property allows
-you to specify an image which gets divided into nine squares which are then drawn as
-the corners, sides, and center of the target element. The sides and center will stretch
-to match the size of the element.</p>
-<p>There are currently several limitations of PIE's implementation, including:</p>
-<ol>
-    <li>It only supports the 'stretch' scheme. I'd like to support the others in the future but performance
-        is a big concern as it seems it will require creating a separate VML shape for each tile.</li>
-    <li>It doesn't support the <a href="http://dev.w3.org/csswg/css3-background/#border-image-outset">outset parameter</a>
-        described in the Backgrounds &amp; Borders module spec, though other browsers don't seem to support
-        that yet either.</li>
-    <li>It doesn't support the <a href="http://dev.w3.org/csswg/css3-background/#border-image-width">width override
-        parameter</a> to the border-image shorthand; it will only use the element's border-width for determining
-        the slice widths (again, support for this in other browsers is spotty too).</li>
-    <li>Related to #3, if the element's <code>border-style</code> is 'none' it will treat that as
-        <code>border-width:0</code>.</li>
-    <li>It requires the 'fill' keyword to be present for the center area to be filled in. This is correct
-        behavior according to the spec but other browsers don't require it and some even fail if 'fill' is
-        present, so it's a bit tricky making it work consistently across browsers.</li>
-    <li>It doesn't hide the element's normal border when border-image is specified. In conjunction with #4
-        above, this means you have to set the border-style to 'solid' (or something other than 'none')
-        <strong>and</strong> set the border-color to transparent.</li>
-    <li>It seems there are on rare occasion rounding errors which cause 1px gaps between slices of the
-        image. I've seen these gaps occur in other browsers too, though.</li>
-</ol>
-<p>These issues will be addressed in a future release.</p>
-<h2 id="pie-background">CSS3 Backgrounds (-pie-background)</h2>
-<p>PIE supports CSS3 multiple background images, linear gradients as
-background images, and some of the new CSS3 background aspects such as
-background origin and clip. Unfortunately, to get access to these
-post-CSS2 values, we have to put them in a property other than the
-standard 'background' property, because IE will attempt to parse the
-value internally and not allow us access to the original value string.
-Therefore we use a custom -pie-background property for holding these
-values.</p>
-<p>Only the single -pie-background shorthand value is recognized; longhand values (e.g.
--pie-background-origin) are ignored.</p>
-<p>For backward-compatibility with browsers which do not support CSS3
-backgrounds, be sure to include appropriate fallbacks. For example:</p>
-<pre class="long"><code>#myElement {
-    background: url(bg-image.png) no-repeat #CCC; /*non-CSS3 browsers will use this*/
-    background: url(bg-image.png) no-repeat, -moz-linear-gradient(#CCC, #EEE); /*gecko*/
-    background: url(bg-image.png) no-repeat, -webkit-gradient(linear, 0 0, 0 100%, from(#CCC) to(#EEE)); /*webkit*/
-    background: url(bg-image.png) no-repeat, linear-gradient(#CCC, #EEE); /*future CSS3 browsers*/
-    -pie-background: url(bg-image.png) no-repeat, linear-gradient(#CCC, #EEE); /*PIE*/
-}</code></pre>
-<p>While the PIE parser will allow them, the following aspects of the
-background shorthand will currently be ignored when rendering:</p>
-<ul>
-  <li>background-attachment (will always use 'scroll' even if 'fixed'
-or 'local' are specified)</li>
-  <li>background-size (will always use the image's intrinsic size)</li>
-  <li>background-repeat values of 'space' or 'round' (the other repeat
-values are supported)</li>
-  <li>background-origin (will always use 'padding-box')</li>
-  <li>background-position values with more than 2 parts</li>
-</ul>
-<p>Support for these items will be added in future versions as possible.</p>
-<p>Note that PNG background images specified using <code>-pie-background</code> will be
-rendered with correct alpha channel transparency in IE6. See the section below regarding
-<a href="#pie-png-fix">PNG alpha transparency</a> for more information.</p>
-<p>Notes on other browsers:</p>
-<p>Firefox supports multiple backgrounds as of version 3.6. Safari supports them as of version 1.3.
-See <a href="https://developer.mozilla.org/en/CSS/Multiple_backgrounds">https://developer.mozilla.org/en/CSS/Multiple_backgrounds</a></p>
-<h2 id="gradients">Gradients</h2>
-<p>PIE currently supports <code>linear-gradient</code> image values when used in the
--pie-background property. Uses in any contexts other than the background
-are not supported. The supported syntax matches that of the current
-<a href="http://dev.w3.org/csswg/css3-images/#linear-gradients">CSS3 Image Values module</a> draft.</p>
-<pre class="long">linear-gradient([&lt;bg-position&gt; || &lt;angle&gt;,]? &lt;color-stop&gt;, &lt;color-stop&gt;[, &lt;color-stop&gt;]*);</pre>
-<p>Currently all color stops are rendered fully opaque, even if
-specifying an rgba color value. This is due to a limitation in VML's
-linear gradient syntax which does not allow setting opacity for
-individual color stops. (See <a href="http://github.com/lojjic/PIE/issues#issue/7">issue #7</a>)</p>
-<p>Gradients containing color-stops which lie outside the bounding area
-of the element are not currently supported, due to limitations in VML's
-gradient rendering.</p>
-<p>Radial gradients are not supported at this time; this feature is planned
-for a future release (see <a href="http://github.com/lojjic/PIE/issues#issue/2">issue #2</a>)
-but it may turn out to be impossible to implement due to VML's strange radial gradient behavior.</p>
-<p>Notes on other browsers:</p>
-<p>WebKit's gradient syntax is drastically different than that of the
-CSS3 spec. See the
-<a href="http://developer.apple.com/safari/library/documentation/InternetWeb/Conceptual/SafariVisualEffectsProgGuide/Gradients/Gradients.html">Safari documentation</a> for their syntax</p>
-<p>Mozilla only supports gradients (via the -moz-linear-gradient
-function) as of Firefox 3.6.</p>
-<p>Opera currently has no support for CSS gradients, though you can use SVG to generate gradients instead.</p>
-<h2 id="rgba">RGBA Color Values</h2>
-<p>PIE parses RGBA color values wherever they are allowed. However it
-is only able to successfully render their opacity value in a few
-contexts. In all other contexts they will be rendered with the correct
-RGB color, but fully opaque. Here are the supported contexts in which
-the opacity will be rendered correctly:</p>
-<ul>
-  <li>The solid background-color as specified in the -pie-background property.</li>
-  <li>The color value of box-shadow, if the shadow has no blur.</li>
-</ul>
-<h2 id="custom">PIE custom properties</h2>
-<h3 id="pie-watch-ancestors">-pie-watch-ancestors</h3>
-<p>PIE automatically listens for any attribute or style property
-changes on the element to which the behavior is applied. This means
-that if you have scripting which modifies any of the recognized CSS3
-properties on the fly, those changes will automatically be picked up
-and the rendering will be updated to match. For example:</p>
-<pre><code>/* JS: */
-myElement.onclick = function() {
-    this.style.borderRadius = '20px';
-};
-/* CSS: */
-#myElement {
-    behavior: url(PIE.htc);
-    border-radius: 10px;
-}</code></pre>
-<p>Assuming myElement has the PIE.htc behavior attached to it, the
-above code will work as expected without any extra effort from the
-author of the script or CSS. This seamlessness is a big part of why PIE
-is so easy to use.</p>
-<p>But common best-practices in scripting dictate that instead of
-setting styles directly with element.style.foo, scripts should only
-add/remove elements' class names, letting the actual styles
-corresponding to those class names be maintained in the CSS. So
-reworking the above example:</p>
-<pre><code>/* JS: */
-myElement.onclick = function() {
-    this.className += ' poked';
-}
-/* CSS: */
-#myElement {
-    behavior: url(PIE.htc);
-    border-radius: 10px;
-}
-#myElement.poked {
-    border-radius: 20px;
-}</code></pre>
-<p>Again, since the className is being changed on the element to which
-the behavior is applied, PIE will automatically be notified of the
-change and update the border-radius rendering to match the new value.</p>
-<p>However, what if the className is changed not on the element itself
-but on one of its ancestors?</p>
-<pre><code>/* JS: */
-myElement.onclick = function() {
-    this.parentNode.className += ' poked';
-}
-/* CSS: */
-#myElement {
-    behavior: url(PIE.htc);
-    border-radius: 10px;
-}
-.poked #myElement {
-    border-radius: 20px;
-}</code></pre>
-<p>This is a very common pattern which allows a lot of flexibility.
-However, in this case, PIE will not be automatically notified of the
-className change. To be notified, it will also have to add a listener
-to the ancestor element. We could brute-force this by automatically
-adding propertychange listeners to all the ancestors of every
-PIE-targeted element, but that would be bad for performance and memory
-usage. So instead, we have introduced a custom CSS property which
-allows authors to tell PIE that certain ancestors should be watched:</p>
-<pre><code>/* JS: */
-myElement.onclick = function() {
-    this.parentNode.className += ' poked';
-}
-/* CSS: */
-#myElement {
-    behavior: url(PIE.htc);
-    border-radius: 10px;
-    <strong>-pie-watch-ancestors: 1;</strong>
-}
-.poked #myElement {
-    border-radius: 20px;
-}</code></pre>
-<p>This tells PIE that it should watch for changes on ancestors one
-level up from the element. It will attach the propertychange listener
-to the element's parent and therefore be notified when the parent's
-className gets changed, and update the rendering correctly.
-</p>
-<h3 id="pie-png-fix">PNG alpha transparency and -pie-png-fix</h3>
-<p>A nice side-effect of PIE's use of VML for rendering is that it causes PNG images
-with alpha channel transparency to be correctly displayed in IE6 when they are rendered
-by PIE's engine. This includes:</p>
-<ul>
-    <li>Background images specified using the <a href="#pie-background">-pie-background</a> property</li>
-    <li>Background images specified using the standard <code>background-image</code> style, when used
-        in conjunction with other CSS3 properties that trigger re-rendering of the background
-        (border-radius, border-image)</li>
-    <li>&lt;img> elements that have border-radius applied</li>
-</ul>
-<p>Sometimes you might want the benefit of the fixed PNG transparency, on elements that do not meet
-the criteria above. In that case, you can add the custom property <code>-pie-png-fix: true;</code> to
-force re-rendering of the background-image or &lt;img>. (The PIE.htc behavior must also be
-attached to the element.)</p>
-<h3 id="pie-lazy-init">Lazy Initialization (-pie-lazy-init)</h3>
-<p>While PIE has been optimized for speed, there is still a small cost in rendering performance for each element
-it is applied to. When you have dozens or hundreds of elements on your page with CSS3 styles applied, this
-can add up to a noticeable rendering delay.</p>
-<p>When you have that many elements on one page, chances are that only a small number of them are visible
-in the browser viewport initially, as viewing the rest would require scrolling. PIE allows an optional
-optimization for this case: if you apply the custom <code>-pie-lazy-init:true;</code> property to elements
-PIE will delay the initialization of their CSS3 rendering until they are scrolled into the viewport. This
-keeps the initial page load snappy without severely limiting the number of elements you can render.</p>
-<h3 id="pie-poll">Layout Polling (-pie-poll)</h3>
-<p>In general PIE is quite good at detecting changes to the size and position of the elements to which it
-is attached and automatically adjusting its rendering to match. It does this by listening to the IE-specific
-<code>onmove</code> and <code>onresize</code> events for each target element. In the majority of cases this
-works seamlessly; in rare cases, however, IE does not fire these events when it should, and PIE gets out of sync.</p>
-<p>To help users get around these cases, PIE has a second method for tracking size and position changes: polling.
-When polling is enabled for an element, PIE will manually query that element's layout several times a second, and
-if the layout has changed then it will adjust the rendering.</p>
-<p>Polling is enabled by default for all elements in IE8 (as that version is particularly bad about not firing
-the events) and disabled in IE 6 and 7. Users can override these defaults
-to force polling on or off for individual elements by setting a custom CSS property: just specify
-<code>-pie-poll:true;</code> to force polling on for an element, or <code>-pie-poll:false;</code> to disable it.</p>
-<!-- noformat off -->
-</body>
-</html>

data/templates/project/sources/pie/site/pie-wp-theme/404.php DELETED Viewed

@@ -1,24 +0,0 @@
-<?php
-// This file is part of the Carrington JAM Theme for WordPress
-// http://carringtontheme.com
-//
-// Copyright (c) 2008-2010 Crowd Favorite, Ltd. All rights reserved.
-// http://crowdfavorite.com
-//
-// Released under the GPL license
-// http://www.opensource.org/licenses/gpl-license.php
-//
-// **********************************************************************
-// This program is distributed in the hope that it will be useful, but
-// WITHOUT ANY WARRANTY; without even the implied warranty of
-// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-// **********************************************************************
-if (__FILE__ == $_SERVER['SCRIPT_FILENAME']) { die(); }
-// NOTE: this file is here for compatibility reasons - active templates are in the error/ dir
-cfct_error('404');
-?>

data/templates/project/sources/pie/site/pie-wp-theme/archive.php DELETED Viewed

@@ -1,24 +0,0 @@
-<?php
-// This file is part of the Carrington JAM Theme for WordPress
-// http://carringtontheme.com
-//
-// Copyright (c) 2008-2010 Crowd Favorite, Ltd. All rights reserved.
-// http://crowdfavorite.com
-//
-// Released under the GPL license
-// http://www.opensource.org/licenses/gpl-license.php
-//
-// **********************************************************************
-// This program is distributed in the hope that it will be useful, but
-// WITHOUT ANY WARRANTY; without even the implied warranty of
-// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-// **********************************************************************
-if (__FILE__ == $_SERVER['SCRIPT_FILENAME']) { die(); }
-// NOTE: this file is here for compatibility reasons - active templates are in the posts/ dir
-cfct_posts();
-?>

data/templates/project/sources/pie/site/pie-wp-theme/attachment/attachment-default.php DELETED Viewed

@@ -1,61 +0,0 @@
-<?php
-// This file is part of the Carrington JAM Theme for WordPress
-// http://carringtontheme.com
-//
-// Copyright (c) 2008-2010 Crowd Favorite, Ltd. All rights reserved.
-// http://crowdfavorite.com
-//
-// Released under the GPL license
-// http://www.opensource.org/licenses/gpl-license.php
-//
-// **********************************************************************
-// This program is distributed in the hope that it will be useful, but
-// WITHOUT ANY WARRANTY; without even the implied warranty of
-// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-// **********************************************************************
-if (__FILE__ == $_SERVER['SCRIPT_FILENAME']) { die(); }
-if (CFCT_DEBUG) { cfct_banner(__FILE__); }
-get_header();
-if (have_posts()) : while (have_posts()) : the_post();
-?>
-<a href="<?php echo get_permalink($post->post_parent); ?>" rev="attachment">&larr; back to &#8220;<?php echo get_the_title($post->post_parent); ?>&#8221;</a>
-<a href="<?php echo wp_get_attachment_url($post->ID); ?>"><?php echo wp_get_attachment_image( $post->ID, 'full' ); ?></a>
-<h1><?php the_title(); ?></h1>
-<?php
-if ( !empty($post->post_excerpt) ) the_excerpt(); // this is the "caption"
-the_content();
-if (cfct_get_adjacent_image_link(false) != '') {
-	next_image_link();
-}
-if (cfct_get_adjacent_image_link(true) != '') {
-	previous_image_link();
-}
-?>
-<?php endwhile; else: ?>
-<p>Sorry, no attachments matched your criteria.</p>
-<?php endif; ?>
-<?php
-wp_footer();
-get_footer();
-?>