Commits

Doug Stewart  committed f88bdde

Adding WP-Less.

  • Participants
  • Parent commits 9012719

Comments (0)

Files changed (58)

File includes/wp-less/README.md

+# Enables LESS in WordPress
+
+## Usage:
+
+Extract the zip into your theme or plugin directory.
+
+For use with themes add the following lines to your functions.php:
+
+```php
+<?php
+require_once( 'wp-less/wp-less.php' );
+if ( ! is_admin() )
+    wp_enqueue_style( 'style', get_stylesheet_directory_uri() . '/style.less' );
+?>
+```
+
+Any registered styles with the .less suffix will be compiled and the file URL rewritten.
+
+You won't need a link to your main style sheet in header.php, just make sure that `wp_head()` is called in the document head.
+
+All the standard LESS features are supported as well as @import rules anywhere within the file.
+
+Read the LESS.js documentation here: http://lesscss.org/
+For documenation specific to the PHP parser: http://leafo.net/lessphp/docs/

File includes/wp-less/lessc/LICENSE

+For ease of distribution, lessphp 0.2.0 is under a dual license.
+You are free to pick which one suits your needs.
+
+
+
+
+MIT LICENSE
+
+
+
+
+Copyright (c) 2010 Leaf Corcoran, http://leafo.net/lessphp
+ 
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+ 
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+ 
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+
+
+GPL VERSION 3
+
+
+
+
+					GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+

File includes/wp-less/lessc/README.md

+# lessphp v0.3.0
+#### <http://leafo.net/lessphp>
+
+`lessphp` is a compiler for LESS written in PHP. The documentation is great,
+so check it out: <http://leafo.net/lessphp/docs/>. Here's a quick tutorial:
+
+### How to use in your php project
+
+Copy `lessc.inc.php` to your include directory and include it into your project.
+
+There are a few ways to interface with the compiler. The easiest is to have it
+compile a LESS file when the page is requested. The static function 
+`lessc::ccompile`, checked compile, will compile the input LESS file only when it
+is newer than the output file.
+
+	try {
+		lessc::ccompile('input.less', 'output.css');
+	catch (exception $ex) {
+		exit($ex->getMessage());
+	}
+
+Note that all failures with lessc are reported through exceptions.
+If you need more control you can make your own instance of lessc.
+
+	$input = 'mystyle.less';
+
+	$lc = new lessc($input);
+
+	try {
+		file_put_contents('mystyle.css', $lc->parse());
+	} catch (exception $ex) { ... }
+
+In addition to loading from file, you can also parse from a string like so:
+
+	$lc = new lessc();
+	$lesscode = 'body { ... }';
+	$out = $lc->parse($lesscode);
+
+### How to use from the command line
+
+An additional script has been included to use the compiler from the command
+line. In the simplest invocation, you specify an input file and the compiled
+css is written to standard out:
+
+	~> plessc input.less > output.css
+
+Using the -r flag, you can specify LESS code directly as an argument or, if 
+the argument is left off, from standard in:
+
+	~> plessc -r "my less code here"
+
+Finally, by using the -w flag you can watch a specified input file and have it 
+compile as needed to the output file
+
+	~> plessc -w input-file output-file
+
+Errors from watch mode are written to standard out.
+
+

File includes/wp-less/lessc/docs/docs.html

+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+  <head>
+	<meta http-equiv="Content-type" content="text/html; charset=utf-8" />
+	<link rel="stylesheet" type="text/css" href="style.css" media="screen" />
+	<link rel="alternate" type="application/rss+xml" title="lessphp changelog feed" href="http://leafo.net/lessphp/feed/" /> 
+	<title>Documentation - lessphp</title>
+  </head>
+  <body>
+	
+	<h1>Documentation - lessphp v0.2.0</h1>
+	<div class="content">
+
+	<ul id="nav">
+		<li><a href="#start">Getting Started</a></li>
+		<li><a href="#language">The Language</a>
+			<ul><li><a href="#vars">Abstract Properties (Variables)</a></li></ul>
+			<ul><li><a href="#pvalues">Property Values &amp; Expressions</a></li></ul>
+			<ul><li><a href="#nested">Nested Blocks</a></li></ul>
+			<ul><li><a href="#mixins">Mixins &amp; Namespace Access</a></li></ul>
+			<ul><li><a href="#ablocks">Abstract Blocks</a></li></ul>
+			<ul><li><a href="#args">Mixin Arguments</a></li></ul>
+			<ul><li><a href="#import">Import Statement</a></li></ul>
+			<ul><li><a href="#strings">String Mixins</a></li></ul>
+			<ul><li><a href="#misc">Miscellaneous</a></li></ul>
+			<ul><li><a href="#differences">Differences from Ruby LESS</a></li></ul>
+		</li>
+		<li><a href="#interface">The Interface</a></li>
+	</ul>
+
+	<p><strong>lessphp</strong> is a compiler that generates css from a small superset language that adds
+	many additional features seen in other languages. It is based off an original Ruby implementation
+	called <a href="http://lesscss.org/">LESS</a>. For the most part, <strong>lessphp</strong> is syntactically
+	compatible with LESS, with the exception of a few things noted below.</p>
+
+	<a name="start"></a>
+	<h2>Getting Started</h2>
+	<p>Download the latest version of <strong>lessphp</strong> <a href="http://leafo.net/lessphp/">here</a>.</p>
+	<p>You can also find the latest development version in the <a href="http://github.com/leafo/lessphp">git repository</a>.</p>
+
+	</div>
+
+	<a name="language"></a>
+	<h1>The Language</h1>
+	<div class="content">
+		<br />
+		<p><strong>lessphp</strong> is a data description language built on top of CSS. The two major components of the language are 
+		blocks and property-value pairs. A block is a scope for a collection of property-value pairs.</p>
+
+		<p>Blocks and properties have special characteristics depending on how they are named.</p>
+
+		<p>It is important to realize that a block's state does not change over time. When a block is defined, all of its properties are constant. The best way to demonstrate this is to look at the following LESS snippet:</p>
+
+<pre class="code">
+body {
+    color: @val; 
+    @val: blue;
+}</pre>
+
+		<p>Because the state of the block is not changing over time, but constant after its creation, 
+	the color property is printed with the value <code>blue</code>.
+
+		<a name="vars"></a>
+		<h2>Abstract Properties (Variables)</h2>
+		<p>Abstract properties are defined with a name starting with <code>@</code>. These types of properties are special in two ways: first, they are not included in the output of the compiler. Second, they can be easily accessed in the values of other properties just by writing their name. If a property is referenced but can not be found, a blank string is returned.</p> 
+		<p>As a LESS programmer, it means that you can define a collection of hidden values that can be referenced in other locations.</p>
+
+<pre class="code">
+@mycolor: #fff;
+body {
+    color: @mycolor; 
+}
+pre {
+    color: @mycolor;
+}</pre>
+
+	<p>Also take note that you can define abstract properties in the global scope.</p>
+
+	<a name="pvalues"></a>
+	<h2>Property Values & Expressions</h2>
+	<p>All properties have at least one value. The value is a list of expressions separated by spaces or commas.
+	An expression is any CSS value with optional mathematical operators applied to it. The operators only function
+	with number and color value types.<p>
+
+	<p>Operations on units will keep the unit of the rightmost value, 
+	unless it is unit-less, then the leftmost unit will be kept for the result. See the following examples below.<p>
+
+<pre class="code">body {
+    color: #001 + #abc;        // evaulates to #aabbdd:
+    width: 3430px + 22;        // evaluates to 3452px;
+    margin: (1.5em / 2) + 2px; // evaluates to 2.85px;
+    margin: 20 + 2px;          // evaluates to 22px;
+    font-family: "Some " + "Family"; // evaluates to "Some Family"
+}</pre>
+
+	<p>It is important to notice that in the example above the output will print the margin property twice. 
+A single property name can hold more than one value; older values are not overwritten.</p>
+
+	<a name="nested"></a>
+	<h2>Nested Blocks</h2>
+	<p>Blocks can be nested inside of each other in order to achieve the same effect as listing out the
+	path of identifiers in CSS. This can help to increase organization of your LESS code and reduce
+	the amount of repeated tag names you have to type.</p>
+
+<pre class="code">body {
+    a {
+        color: green;
+        :hover {
+            color: blue;
+        }
+    }
+}</pre>
+
+
+	<a name="mixins"></a>
+	<h2>Mixins & Namespace Access</h2>
+	
+	<p>Any block can be "mixed" into the current block. This means that all properties and blocks 
+	in the target block are brought into the current block. It is possible to achieve the same effect
+	with just CSS and HTML, but there are some additional features discussed below that make it worthwhile
+	to utilize LESS-style mixing.</p>
+	<p>The syntax is as follows:<p>
+
+<pre class="code">
+.myclass {
+    @fonts: Helvetica, Arial;
+    margin: 1.0em;	
+    line-spacing: 150%;
+
+    a {
+        background-color: black;
+    }
+}
+
+pre {
+    .myclass;
+    font-family: @fonts; // uses the mixed in variable
+}
+
+div.notice {
+    .myclass;
+}</pre>
+
+	<p>If you want to mix in a specific block within another block you can use the <code>&gt;</code> namespace operator. 
+	Additionally you can pull out specific values of properties from blocks using the <code>[ ]</code> operator.
+
+<pre class="code">// using .myclass from above
+li {
+    .myclass &gt; a; // just mix in properties from 'a' tag in .myclass
+    fonts: .myclass[@fonts];
+    padding: .myclass['margin'];
+}</pre>
+
+
+	<a name="ablocks"></a>
+	<h2>Abstract Blocks</h2>
+
+	<p>Abstract blocks are like any other blocks, but their names start with a <code>@</code>. Like abstract properties, they are not 
+	included in the compiler's output. This allows you to utilize mixins without adding any unused blocks to the output. 
+	You can also use an abstract class to define a package of invisible, but extractable blocks and properties.<p>
+
+<pre class="code">@mypackage {
+    .coolColors {
+        color: pink;
+        background-color: green;
+    }
+
+    .hotColors {
+        color: red;
+        background-color: orange;
+    }
+}
+
+p {
+    @mypackage &gt; .coolColors;
+}
+
+div {
+    @mypackage; // inserts both classes into this block 
+}</pre>
+
+	<p>It is possible to give an abstract block the same name as an abstract property; their names will not collide.
+	Block names and property names exist in different spaces. For example:</p>
+
+<pre class="code">@color(@color:red) { color: @color; } // this is valid
+</pre>
+
+	<a name="args"></a>
+	<h2>Mixin Arguments</h2>
+	<p>All blocks have the option of taking argument lists, and the arguments can have default values.</p>
+
+<pre class="code">@some_mixin(@width: 200px;@radius) {
+    border-radius: @radius;
+    width: @width
+}
+
+.first {
+    @some_mixin(300px; 2em);
+}
+
+.second {
+    @some_mixin(;4px); // blank argument takes default value
+}</pre>
+
+	<a name="import"></a>
+	<h2>Import Statement</h2>
+	<p>If you have multiple LESS files, you can combine them into a single CSS file during compilation using the 
+	<code>@import</code> directive. LESS import uses the same syntax as CSS import. If it can find the file specified 
+	then it will pull it into the compiler in place of the statement. If the file can't be found, the statement is 
+	printed to the output. The following are all valid:</p>
+
+<pre class="code">@import "file";
+@import 'file.less';
+@import url("file");
+@import url('file');
+@import url(file); </pre>
+
+	<p>Note that if it fails to find a file  it will append <code>.less</code> to the filename and try again. 
+	This means <code>@import 'somefile'</code> and <code>@import 'somefile.less'</code> will
+	both import the file <code>somefile.less</code>.
+
+
+	<a name="strings"></a>
+	<h2>String Mixins</h2>
+	<p>It is possible to access the value of an abstract property from a string using <code>{ }</code> operators.</p>
+
+<pre class="code">@image_folder: darktheme;
+.header {
+    background-image: url(/images/{@image_folder}/header.png);
+}</pre>
+
+	<p>The <code>{ }</code> syntax will also work in any string value type, which is any text 
+	wrapped in single or double quotes</p>
+
+
+	<a name="misc"></a>
+	<h2>Miscellaneous</h2>
+	<p>As mentioned before, all properties hold constant data. This includes abstract values. While it may be convenient to 
+	think of them as variables, they don't have the ability to vary. For convenience, some tricks were implemented to
+	make self referencing properties evaluate in order as if they had changing state. Consider the following statement:</p>
+
+<pre class="code">
+@what: 1;
+body { 
+    @what: @what + 1;
+    @what: @what + 2;
+    .class {
+        @what: @what + 1;
+		width: @what;
+    }
+}
+
+#something {
+    @what: 200;
+    body > .class;	
+}</pre>
+
+	<p>In the output, <code>body .class</code> has width set to 5, and <code>#something</code> has width set to 201. It appears from that result that
+	the property <code>@what</code> is being incremented. But, as mentioned above, the name <code>@what</code> stores a series of unchanging values.
+	The values use delayed evaluation, so each value holds an equation.</p>
+
+	<p>What this means is that the values of the properties don't change while the block is parsed, only additional property-value pairs are added
+	to the block's definition.
+	When the block's is compiled into CSS, the equations and property references are solved using the data in the scope. Technically, it is 
+	ambiguous what value to use for referencing a variable, because the single name can store multiple values.<p>
+
+	<p>The approach taken in <strong>lessphp</strong> is to use the most recent value. This gives the appearance that the block is parsed line by line. 
+	In order to prevent infinite loops when a variable references itself, a single value in the set of all values for a given name can only be used once in
+	the chain of dereferencing.</p>
+
+
+	<a name="differences"></a>
+	<h2>Differences from Ruby LESS</h2>
+	<p class="important">Report missing ones <a href="http://github.com/leafo/lessphp/issues">here</a>.</p>
+	<ul>
+		<li>Arguments to mixins are separated by <code>;</code> instead of <code>,</code>.
+			<p><b>Rationale</b>: the value of a css property can contain commas, so by using a comma as an argument separator you limit the kinds of input you can pass to a mixin.</p>
+		</li>
+	</ul>
+
+	</div>
+
+<a name="interface"></a>
+<h1>The PHP Interface</h1><br />
+	<div class="content">
+<p>There are a few ways to interface with the compiler. The easiest is to have it
+compile a LESS file when the page is requested. The static function 
+<code>less::ccompile</code>, checked compile, will compile the inputed LESS file only when it
+is newer than the output file.<p>
+
+<pre class="code">
+<span class="PreProc">require</span> '<span class="String">lessc.inc.php</span>';
+
+<span class="Statement">try</span> <span class="Delimiter">{</span>
+    lessc<span class="Operator">::</span>ccompile<span class="Delimiter">(</span>'<span class="String">input.less</span>', '<span class="String">out.css</span>'<span class="Delimiter">)</span>;
+<span class="Delimiter">}</span> <span class="Statement">catch</span> <span class="Delimiter">(</span><span class="Function">exception</span> <span class="Operator">$</span><span class="Identifier">ex</span><span class="Delimiter">)</span> <span class="Delimiter">{</span>
+    <span class="Statement">exit</span><span class="Delimiter">(</span>'<span class="String">lessc fatal error:&lt;br /&gt;</span>'<span class="Operator">.</span><span class="Operator">$</span><span class="Identifier">ex</span><span class="Type">-&gt;</span>getMessage<span class="Delimiter">())</span>;
+<span class="Delimiter">}</span>
+</pre>
+
+<br />
+<p>Note that all failures with lessc are reported through exceptions.
+If you need more control then you can make your own instance of <code>lessc</code>.</p>
+<pre class="code">
+<span class="PreProc">require</span> '<span class="String">lessc.inc.php</span>';
+
+<span class="Operator">$</span><span class="Identifier">less</span> <span class="Operator">=</span> <span class="PreProc">new</span> lessc<span class="Delimiter">(</span>'<span class="String">path/to/style.less</span>'<span class="Delimiter">)</span>;
+<span class="Function">file_put_contents</span><span class="Delimiter">(</span>'<span class="String">path/to/style.css</span>', <span class="Operator">$</span><span class="Identifier">less</span><span class="Type">-&gt;</span>parse<span class="Delimiter">())</span>;
+</pre>
+
+<br />
+<p>In addition to loading from a file, you can also parse from a string like so:</p>
+<pre class="code">
+<span class="PreProc">require</span> '<span class="String">lessc.inc.php</span>';
+
+<span class="Operator">$</span><span class="Identifier">less</span> <span class="Operator">=</span> <span class="PreProc">new</span> lessc<span class="Delimiter">()</span>;
+<span class="Operator">$</span><span class="Identifier">style</span> <span class="Operator">=</span> '<span class="String">&lt;style type=&quot;text/css&quot;&gt;</span>'<span class="Operator">.</span>
+    <span class="Operator">$</span><span class="Identifier">less</span><span class="Type">-&gt;</span>parse<span class="Delimiter">(</span>'<span class="String">.block { padding: 3 + 4px }</span>'<span class="Delimiter">)</span><span class="Operator">.</span>
+    '<span class="String">&lt;/style&gt;</span>';
+</pre>
+
+
+	<h2>Import Directoy</h2>
+	<p>When using the <code>@import</code> directive, the compiler searches for files 
+	in the <code>$importDir</code> public property of <code>lessc</code>. If the compiler is loaded with a filename
+	(either in the constructor or using <code>ccompile</code>) it will extract the directory and set that as the 
+	import directory</p>
+
+
+	<h2>Library Functions</h2>
+	<p>Functions within the compiler class that are prefixed with <code>lib_</code> are visible visible to the less
+	code while it is being parsed. The easiest way to add your own functions is to subclass <code>lessc</code> and insert
+	the implementations.</p>
+
+	<br />
+	<br />
+	<hr />
+	<p class="foot">
+		<a href="http://leafo.net/lessphp/">http://leafo.net/lessphp</a> - Last updated March 9th 2010</p>
+
+	</div>
+
+  </body>
+</html>
+

File includes/wp-less/lessc/docs/docs.md

+    title: v0.3.0 documentation
+    link_to_home: true
+--
+
+<h2 skip="true">Documentation v0.3.0</h2>
+
+<div style="margin-bottom: 1em;">$index</div>
+
+**lessphp** is a compiler that generates CSS from a superset language which
+adds a collection of convenient features often seen in other languages. All CSS
+is compatible with LESS, so you can start using new features with your existing CSS.
+
+It is designed to be compatible with [less.js](http://lesscss.org), and suitable
+as a drop in replacement for PHP projects.
+
+## Getting Started
+
+The homepage for **lessphp** can be found at [http://leafo.net/lessphp/][1].
+
+You can follow development at the project's [GitHub][2].
+
+Including **lessphp** in your project is as simple as dropping the single
+include file into your code base and running the appropriate compile method as
+described in the [PHP Interface](#php_interface).
+
+  [1]: http://leafo.net/lessphp "lessphp homepage"
+  [2]: https://github.com/leafo/lessphp "lessphp GitHub page"
+
+## Installation
+
+**lessphp** is distributed entirely in a single stand-alone file. Download the
+latest version from either [the homepage][1] or [GitHub][2].
+
+Development versions can also be downloading from GitHub.
+
+Place `lessphp.inc.php` in a location available to your PHP scripts, and
+include it. That's it! you're ready to begin.
+
+## The Language
+
+**lessphp** is very easy to learn because it generally functions how you would
+expect it to. If you feel something is challenging or missing, feel free to
+open an issue on the [bug tracker](https://github.com/leafo/lessphp/issues).
+
+It is also easy to learn because any standards-compliant CSS code is valid LESS
+code. You are free to gradually enhance your existing CSS code base with LESS
+features without having to worry about rewriting anything.
+
+The following is a description of the new languages features provided by LESS.
+
+### Line Comments
+
+Simple but very useful; line comments are started with `//`:
+
+    ```less
+    // this is a comment
+    body {
+      color: red; // as is this
+      /* block comments still work also */
+    }
+    ```
+
+### Variables
+Variables are identified with a name that starts with `@`. To declare a
+variable, you create an appropriately named CSS property and assign it a value:
+
+    ```less
+    @family: "verdana";
+    @color: red;
+    body {
+      @mycolor: red;
+      font-family: @family;
+      color: @color;
+      border-bottom: 1px solid @color;
+    }
+    ```
+
+Variable declarations will not appear in the output. Variables can be declared
+in the outer most scope of the file, or anywhere else a CSS property may
+appear. They can hold any CSS property value.
+
+Variables are only visible for use from their current scope, or any enclosed
+scopes.
+
+### Expressions
+
+Expressions let you combine values and variables in meaningful ways. For
+example you can add to a color to make it a different shade. Or divide up the
+width of your layout logically. You can even concatenate strings.
+
+Use the mathematical operators to evaluate an expression:
+
+    ```less
+    @width: 960px;
+    .nav {
+      width: @width / 3;
+      color: #001 + #abc;
+    }
+    .body {
+      width: 2 * @width / 3;
+      font-family: "hel" + "vetica";
+    }
+    ```
+
+Parentheses can be used to control the order of evaluation. They can also be
+used to force an evaluation for cases where CSS's syntax makes the expression
+ambiguous.
+
+The following property will produce two numbers, instead of doing the
+subtraction:
+
+    ```less
+    margin: 10px -5px;
+    ```
+
+To force the subtraction:
+
+    ```less
+    margin: (10px -5px);
+    ```
+
+It is also safe to surround mathematical operators by spaces to ensure that
+they are evaluated:
+
+    ```less
+    margin: 10px - 5px;
+    ```
+
+Division has a special quirk. Due to CSS font shorthand syntax, we need to be
+careful about how we place spaces. In the following example we are using font
+size and lineheight shorthand. No division should take place:
+
+    ```less
+    .font {
+      font: 20px/80px "Times New Roman";
+    }
+    ```
+
+In order to force division we can surround the `/` by spaces, or we can wrap
+the expression in parentheses:
+
+    ```less
+    .font {
+      // these two will evaluate
+      font: 20px / 80px "Times New Roman";
+      font: (20px/80px) "Times New Roman";
+    }
+    ```
+
+### Nested Blocks
+
+By nesting blocks we can build up a chain of CSS selectors through scope
+instead of repeating them. In addition to reducing repetition, this also helps
+logically organize the structure of our CSS.
+
+    ```less
+    ol.list {
+      li.special {
+        border: 1px solid red; 
+      }
+
+      li.plain {
+        font-weight: bold;
+      }
+    }
+    ```
+
+
+This will produce two blocks, a `ol.list li.special` and `ol.list li.plain`.
+
+Blocks can be nested as deep as required in order to build a hierarchy of
+relationships.
+
+The `&` operator can be used in a selector to represent its parent's selector.
+If the `&` operator is used, then the default action of appending the parent to
+the front of the child selector separated by space is not performed.
+
+    ```less
+    b {
+      a & {
+        color: red;
+      }
+
+      // the following have the same effect
+
+      & i {
+        color: blue;
+      }
+
+      i {
+        color: blue;
+      }
+    }
+    ```
+
+
+Because the `&` operator respects the whitespace around it, we can use it to
+control how the child blocks are joined. Consider the differences between the
+following:
+
+    ```less
+    div {
+      .child-class { color: purple; }
+
+      &.isa-class { color: green; }
+
+      #child-id { height: 200px; }
+
+      &#div-id { height: 400px; }
+
+      &:hover { color: red; }
+
+      :link { color: blue; }
+    }
+    ```
+
+The `&` operator also works with [mixins](#mixins), which produces interesting results:
+
+    ```less
+    .within_box_style() {
+      .box & {
+        color: blue;
+      }
+    }
+
+    #menu {
+      .within_box_style;
+    }
+    ```
+
+### Mixins
+
+Any block can be mixed in just by naming it:
+
+    ```less
+    .mymixin {
+      color: blue;
+      border: 1px solid red;
+
+      .special {
+        font-weight: bold;
+      }
+    }
+
+
+    h1 {
+      font-size: 200px;
+      .mixin;
+    }
+    ```
+
+All properties and child blocks are mixed in.
+
+Mixins can be made parametric, meaning they can take arguments, in order to
+enhance their utility. A parametric mixin all by itself is not outputted when
+compiled. Its properties will only appear when mixed into another block.
+
+The canonical example is to create a rounded corners mixin that works across
+browsers:
+    
+    ```less
+    .rounded-corners(@radius: 5px) {
+      border-radius: @radius;
+      -webkit-border-radius: @radius;
+      -moz-border-radius: @radius;
+    }
+
+    .header {
+      .rounded-corners();
+    }
+
+    .info {
+      background: red;
+      .rounded-corners(14px);
+    }
+    ```
+
+If you have a mixin that doesn't have any arguments, but you don't want it to
+show up in the output, give it a blank argument list:
+
+    ```less
+    .secret() {
+      font-size: 6000px;
+    }
+    
+    .div {
+      .secret;
+    }
+    ```
+
+If the mixin doesn't need any arguments, you can leave off the parentheses when
+mixing it in, as seen above.
+
+You can also mixin a block that is nested inside other blocks. You can think of
+the outer block as a way of making a scope for your mixins. You just list the
+names of the mixins separated by spaces, which describes the path to the mixin
+you want to include. Optionally you can separate them by `>`.
+
+    ```less
+    .my_scope  {
+      .some_color {
+        color: red;
+        .inner_block {
+          text-decoration: underline;
+        }
+      }
+      .bold {
+        font-weight: bold;
+        color: blue;
+      }
+    }
+
+    .a_block {
+      .my_scope .some_color;
+      .my_scope .some_color .inner_block;
+    }
+
+    .another_block {
+      // the alternative syntax
+      .my_scope > .bold;
+    }
+    ```
+
+### Import
+
+Multiple LESS files can be compiled into a single CSS file by using the
+`@import` statement. Be careful, the LESS import statement shares syntax with
+the CSS import statement. If the file being imported ends in a `.less`
+extension, or no extension, then it is treated as a LESS import. Otherwise it
+is left alone and outputted directly:
+
+    ```less
+    // my_file.less
+    .some-mixin(@height) {
+      height: @height;
+    }
+
+    // main.less
+    @import "main.less" // will import the file if it can be found
+    @import "main.css" // will be left alone
+
+    body {
+      .some-mixin(400px);
+    }
+    ```
+
+All of the following lines are valid ways to import the same file:
+
+    ```less
+    @import "file";
+    @import 'file.less';
+    @import url("file");
+    @import url('file');
+    @import url(file);
+    ```
+
+When importing, the `importDir` is searched for files. This can be configured,
+see [PHP Interface](#php_interface).
+
+### String Interpolation
+
+String interpolation is a convenient way to insert the value of a variable
+right into a string literal. Given some variable named `@var_name`, you just
+need to write it as `@{var_name}` from within the string to have its value
+inserted:
+
+    ```less
+    @symbol: ">";
+    h1:before {
+      content: "@{symbol}: ";
+    }
+
+    h2:before {
+      content: "@{symbol}@{symbol}: ";
+    }
+    ```
+
+There are two kinds of strings, implicit and explicit strings. Explicit strings
+are wrapped by double quotes, `"hello I am a string"`, or single quotes `'I am
+another string'`. Implicit strings only appear when using `url()`. The text
+between the parentheses is considered a string and thus string interpolation is
+possible:
+
+    ```less
+    @path: "files/";
+    body {
+      background: url(@{path}my_background.png);
+    }
+    ```
+
+### String Format Function
+
+The `%` function can be used to insert values into strings using a *format
+string*. It works similar to `printf` seen in other languages. It has the
+same purpose as string interpolation above, but gives explicit control over
+the output format.
+
+    ```less
+    @symbol: ">";
+    h1:before {
+      content: %("%s: ", @symbol);
+    }
+    ```
+
+The `%` function takes as its first argument the format string, following any
+number of addition arguments that are inserted in place of the format
+directives.
+
+A format directive starts with a `%` and is followed by a single character that
+is either `a`, `d`, or `s`:
+
+    ```less
+    strings: %("%a %d %s %a", hi, 1, 'ok', 'cool');
+    ```
+
+`%a` and `%d` format the value the same way: they compile the argument to its
+CSS value and insert it directly. When used with a string, the quotes are
+included in the output. This typically isn't what we want, so we have the `%s`
+format directive which strips quotes from strings before inserting them.
+
+The `%d` directive functions the same as `%a`, but is typically used for numbers
+assuming the output format of numbers might change in the future.
+
+### String Unquoting
+
+Sometimes you will need to write proprietary CSS syntax that is unable to be
+parsed. As a workaround you can place the code into a string and unquote it.
+Unquoting is the process of outputting a string without its surrounding quotes.
+There are two ways to unquote a string.
+
+The `~` operator in front of a string will unquote that string:
+
+    ```less
+    .class {
+      // a made up, but problematic vendor specific CSS
+      filter: ~"Microsoft.AlphaImage(src='image.png')";
+    }
+    ```
+
+If you are working with other types, such as variables, there is a built in
+function that let's you unquote any value. It is called `e`.
+
+    ```less
+    @color: "red";
+    .class {
+      color: e(@color);
+    }
+    ```
+
+### Built In Functions
+
+**lessphp** has a collection of built in functions:
+
+* `e(str)` -- returns a string without the surrounding quotes.
+  See [String Unquoting](#string_unquoting)
+
+* `floor(number)` -- returns the floor of a numerical input
+* `round(number)` -- returns the rounded value of numerical input
+
+* `lighten(color, percent)` -- lightens color by percent and returns it
+* `darken(color, percent)` -- darkens color by percent and returns it
+
+* `saturate(color, percent)` -- saturates color by percent and returns it
+* `desaturate(color, percent)` -- desaturates color by percent and returns it
+
+* `fadein(color, percent)` -- makes color less transparent by percent and returns it
+* `fadeout(color, percent)` -- makes color more transparent by percent and returns it
+
+* `spin(color, amount)` -- returns a color with amount degrees added to hue
+
+* `rgbahex(color)` -- returns a string containing 4 part hex color.
+   
+   This is used to convert a CSS color into the hex format that IE's filter
+   method expects when working with an alpha component.
+   
+       ```less
+       .class {
+          @start: rgbahex(rgba(25, 34, 23, .5));
+          @end: rgbahex(rgba(85, 74, 103, .6));
+          // abridged example
+          -ms-filter:
+            e("gradient(start=@{start},end=@{end})");
+       }
+       ```
+
+## PHP Interface
+
+The PHP interface lets you control the compiler from your PHP scripts. There is
+only one file to include to get access to everything:
+
+    ```php
+    <?php
+    include "lessc.inc.php";
+    ```
+
+To compile a file to a string (of CSS code):
+
+    ```php
+    $less = new lessc("myfile.less");
+    $css = $less->parse();
+    ```
+
+To compile a string to a string:
+
+    ```php
+    $less = new lessc(); // a blank lessc
+    $css = $less->parse("body { a { color: red } }");
+    ```
+
+### Compiling Automatically
+
+Often, you want to write the compiled CSS to a file, and only recompile when
+the original LESS file has changed. The following function will check if the
+modification date of the LESS file is more recent than the CSS file.  The LESS
+file will be compiled if it is. If the CSS file doesn't exist yet, then it will
+also compile the LESS file.
+
+    ```php
+    lessc::ccompile('myfile.less', 'mystyle.css');
+    ```
+
+`ccompile` is very basic, it only checks if the input file's modification time.
+It is not of any files that are brought in using `@import`.
+
+For this reason we also have `lessc::cexecute`. It functions slightly
+differently, but gives us the ability to check changes to all files used during
+the compile. It takes one argument, either the name of the file we want to
+compile, or an existing *cache object*. Its return value is an updated cache
+object.
+
+If we don't have a cache object, then we call the function with the name of the
+file to get the initial cache object. If we do have a cache object, then we
+call the function with it. In both cases, an updated cache object is returned.
+
+The cache object keeps track of all the files that must be checked in order to
+determine if a rebuild is required.
+
+The cache object is a plain PHP `array`. It stores the last time it compiled in
+`$cache['updated']` and output of the compile in `$cache['compiled']`.
+
+Here we demonstrate creating an new cache object, then using it to see if we
+have a recompiled version available to be written:
+
+
+    ```php
+    $less_file = 'myfile.less';
+    $css_file = 'myfile.css';
+
+    // create a new cache object, and compile
+    $cache = lessc::cexecute('myfile.less');
+    file_put_contents($css_file, $cache['compiled']);
+
+    // the next time we run, write only if it has updated
+    $last_updated = $cache['updated'];
+    $cache = lessc::cexecute($cache);
+    if ($cache['updated'] > $last_updated) {
+        file_put_contents($css_file, $cache['compiled']);
+    }
+
+    ```
+
+In order for the system to fully work, we must save cache object between
+requests. Because it's a plain PHP `array`, it's sufficient to
+[`serialize`](http://php.net/serialize) it and save it the string somewhere
+like a file or in persistent memory.
+
+An example with saving cache object to a file:
+
+    ```php
+    function auto_compile_less($less_fname, $css_fname) {
+      // load the cache
+      $cache_fname = $less_fname.".cache";
+      if (file_exists($cache_fname)) {
+        $cache = unserialize(file_get_contents($cache_fname));
+      } else {
+        $cache = $less_fname;
+      }
+
+      $new_cache = lessc::cexecute($cache);
+      if (!is_array($cache) || $new_cache['updated'] > $cache['updated']) {
+        file_put_contents($cache_fname, serialize($new_cache));
+        file_put_contents($css_fname, $new_cache['compiled']);
+      }
+    }
+
+    auto_compile_less('myfile.less', 'myfile.css')
+
+    ```
+
+`lessc:cexecute` takes an optional second argument, `$force`. Passing in true
+will cause the input to always be recompiled.
+
+### Error Handling
+
+All of the following methods will throw an `Exception` if the parsing fails:
+
+    ```php
+    $less = new lessc();
+    try {
+        $less->parse("} invalid LESS }}}");
+    } catch (Exception $ex) {
+        echo "lessphp fatal error: ".$ex->getMessage();
+    }
+    ```
+### Setting Variables From PHP
+
+The `parse` function takes a second optional argument. If you want to
+initialize variables from outside the LESS file then you can pass in an
+associative array of names and values. The values will parsed as CSS values:
+
+    ```php
+    $less = new lessc();
+    echo $less->parse(".magic { color: @color;  width: @base - 200; }", 
+        array(
+            'color' => 'red';
+            'base' => '960px';
+        ));
+    ```
+
+You can also do this when loading from a file, but remember to set the first
+argument of the parse function to `null`, otherwise it will try to compile that
+instead of the file:
+
+    ```php
+    $less = new lessc("myfile.less");
+    echo $less->parse(null, array('color' => 'blue'));
+    ```
+
+### Custom Functions
+
+**lessphp** has a simple extension interface where you can implement user
+functions that will be exposed in LESS code during the compile. They can be a
+little tricky though because you need to work with the  **lessphp** type system.
+
+By sub-classing `lessc`, and creating specially named methods we can extend
+**lessphp**. In order for a function to be visible in LESS, its name must
+start with `lib_`.
+
+Let's make a function that doubles any numeric argument.
+
+    ```php
+    <?php
+    include "lessc.inc.php";
+
+    class myless extends lessc {
+        function lib_double($arg) {
+            list($type, $value) = $arg;
+            return array($type, $value*2);
+        }
+    }
+
+    $myless = new myless();
+    echo $myless->parse("div { width: double(400px); }");
+    ```
+
+Although a little verbose, the implementation of `lib_double` gives us some
+insight on the type system. All values are stored in an array where the 0th
+element is a string representing the type, and the other elements make up the
+associated data for that value.
+
+The best way to get an understanding of the system is to make a dummy `lib_`
+function which does a `vardump` on the argument. Try passing the function
+different values from LESS and see what the results are.
+
+The return value of the `lib_` function must also be a LESS type, but if it is
+a string or numeric value, it will automatically be coerced into an appropriate
+typed value. In our example, we reconstruct the value with our modifications
+while making sure that we preserve the type.
+
+All of the built in functions are implemented in this manner within the `lessc`
+class.
+
+## Command Line Interface
+
+**lessphp** comes with a command line script written in PHP that can be used to
+invoke the compiler from the terminal. On Linux an OSX, all you need to do is
+place `plessc` and `lessc.inc.php` somewhere in your PATH (or you can run it in
+the current directory as well). On windows you'll need a copy of `php.exe` to
+run the file. To compile a file, `input.less` to CSS, run:
+
+    ```bash
+    $ plessc input.less
+    ```
+
+To write to a file, redirect standard out:
+
+    ```bash
+    $ plessc input.less > output.css
+    ```
+
+To compile code directly on the command line:
+
+    ```bash
+    $ plessc -r "@color: red; body { color: @color; }"
+    ```
+
+To watch a file for changes, and compile it as needed, use the `-w` flag:
+
+    ```bash
+    $ plessc -w input-file output-file
+    ```
+
+Errors from watch mode are written to standard out.
+
+
+## License
+
+Copyright (c) 2010 Leaf Corcoran, <http://leafo.net/lessphp>
+ 
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+ 
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+ 
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+*Also under GPL3 if required, see `LICENSE` file*
+

File includes/wp-less/lessc/docs/style.css

+
+body {
+	margin: 0;
+	padding: 0;
+	font: 14px verdana, sans-serif;
+}
+
+#content, .content  {
+	width: 966px;
+	margin-bottom: 1.0em;
+}
+
+h1,h2 {
+	padding: 0.5em;
+	font-family: calibri, helvetica, sans-serif;
+	margin: 0;
+}
+
+h1 {
+	background: #E7F3FB;
+	color: #182F51;
+}
+
+h2 {
+	color: #3AA6EE;
+	color: #1C97E8;
+}
+
+
+p {
+	margin: 0px;
+	padding: 0px 1.0em 0.5em 1.0em;
+}
+
+a:link, a:visited {
+	color: #4570B8;
+	border-bottom: 1px solid #4570B8;
+	text-decoration: none;
+}
+
+a:hover {
+	background-color: #E7F3FB;
+}
+
+ul {
+	margin: 0px;
+}
+
+ul#nav {
+	margin: 1.0em 0.0em;
+}
+
+hr {
+	border: 0;
+	height: 1px;
+	background-color: #afafaf;
+	margin: 0px 1em;
+}
+
+.foot {
+	color: #afafaf;
+	font-size: 80%;
+	text-align: center;
+	margin: 1.0em 0em;
+}
+
+.foot a {
+	text-decoration: none;
+	color: #777777;
+	border-bottom: 1px solid #777777;
+}
+
+.foot a:hover {
+	color: #000000;
+	background: none;
+}
+
+
+p.important {
+	background-color: #FBE7E7;
+	background-color: #FFD6D7;
+	background-color: #FFDEE2;
+	padding: 1em 0.5em;
+	margin: 0.5em 0.0em 0.5em 0.5em;
+}
+
+.info {
+	background: #ECFBE7;
+	background: #E0FAD7;
+	-moz-border-radius: 8px;
+	-webkit-border-radius: 8px;
+	padding: 1em;
+	margin-left: 0.5em;
+	float: right;
+	width: 200px;
+}
+
+.info h3 {
+	padding: 0.5em;
+	margin: 0px;
+	font-size: 18px;
+	font-family: calibri, helvetica, sans-serif;
+}
+