Permalink
Browse files

updated docs

  • Loading branch information...
1 parent 03f5d55 commit 4fbe71e6e46370d6c6b41083861729674a38953a @robert-hoffmann robert-hoffmann committed Nov 23, 2013
Showing with 11 additions and 13 deletions.
  1. +1 −1 README.md
  2. +5 −5 _includes/api/2.0.0/screen.html
  3. +4 −7 _posts/2013-11-22-HeadJS-v1.0.3-Update.md
  4. +1 −0 site/api/v2.00.html
View
@@ -1,6 +1,6 @@
[![Head JS](http://headjs.com/site/assets/img/logo-big.png)](http://headjs.com)
-###Latest Version: 1.0.3 :: [Downloads](http://headjs.com/site/download.html) | [Docs](http://headjs.com/site/api/v1.00.html) | [News](http://headjs.com/site/blog.html) | [Intro](http://headjs.com)
+###Latest Version: v1.0.3 :: [Downloads](http://headjs.com/site/download.html) | [Docs](http://headjs.com/site/api/v1.00.html) | [News](http://headjs.com/site/blog.html) | [Intro](http://headjs.com)
#####Status
[![Build Status](https://travis-ci.org/headjs/headjs.png?branch=master)](https://travis-ci.org/headjs/headjs)
@@ -43,16 +43,16 @@ <h2 id="screen">Screen Information</h2>
<p>Viewport width information is exposed via CSS so you can apply responsive design principles to your website. These have the advantage of working even on browsers that do not support media queries !</p>
{% highlight css %}
-.lt-800 {
- /* code specific to VIEWPORT < 800 */
+.h-lt1024 {
+ /* code specific to VIEWPORT HEIGHT < 1024 */
}
-.gt-800 {
- /* code specific to VIEWPORT > 800 */
+.w-gt800 {
+ /* code specific to VIEWPORT WIDTH > 800 */
}
{% endhighlight %}
- <p>You can select which variables (lt, lte, gt, gte, eq) and which breakpoints (480, 640, 800, etc) are exposed via CSS in the <a href="#configuration">configuration</a> section.</p>
+ <p>You can select which variables (lt, gt) and which breakpoints (480, 640, 800, etc) are exposed via CSS in the <a href="#configuration">configuration</a> section.</p>
<div style="width:100%;">
<div onclick="blog.loadComments(this, 'api/2.0.0/screen', 'Leave a comment')" style="cursor: pointer;">
@@ -15,20 +15,17 @@ Callbacks now work properly with CSS, a patch was added thank's to [xhaggi](http
An error timeout was also added ..while it's not yet possible to use this timeout to take other actions, it at least assures that callbacks are always fired.
Detecting CSS files when using load is much sturdier. We still can't tell if it's a CSS file when loading a .aspx, .php ...but this will likely change soon.
-__Hopefully this will be the last update on the 1.x branch ..time for [2.x to advance](http://headjs.com/2013/11/08/head.responsive-v2.0.0-alpha.html) ! ;-)__
+__This will probably be the _before last_ update on the 1.x branch ..time for [2.x to advance](http://headjs.com/2013/11/08/head.responsive-v2.0.0-alpha.html) ! ;-)__
- New: Timeout added to resource loading
- New: CSS callbacks now executed for all browsers
- - View
- - [https://github.com/headjs/headjs/pull/273](https://github.com/headjs/headjs/pull/273)
+ - Details: [https://github.com/headjs/headjs/pull/273](https://github.com/headjs/headjs/pull/273)
- New: Changed how file extensions are parsed for detecting css files
- in the future, we will need to add a way to supply a filetype, for when loading resources via scripts like style.php
- Fix: Array loading & trigger not functioning correctly on old browsers
- - View
- - [https://github.com/headjs/headjs/issues/274](https://github.com/headjs/headjs/issues/274)
+ - Details: [https://github.com/headjs/headjs/issues/274](https://github.com/headjs/headjs/issues/274)
- Fix: ready() sometimes does not trigger if assets are loaded too fast
- - View
- - [https://github.com/headjs/headjs/issues/271](https://github.com/headjs/headjs/issues/271)
+ - Details: [https://github.com/headjs/headjs/issues/271](https://github.com/headjs/headjs/issues/271)
<br/><br/>
<hr style="border: thin dashed" />
View
@@ -5,6 +5,7 @@
---
<h2>API documentation v2.0.0 (work in progress)</h2>
+<h4>This is evolving and will probably change as things advance</h4>
<div class="intro">
Tidy up and accelerate your workflow
</div>

0 comments on commit 4fbe71e

Please sign in to comment.