zxial

This plugin provides JSON data to mobile APPs. Here’s the scenarios that you 
could use this plugin: you want to develop a mobile app or app on mac, and the 
app is to show the list of your blogs(in category, tag, or keywords), after 
the app user click one item in the blog list, you would like to show him the 
detail page of the item, but the logos/banners/sidebar of blog is suitable 
only for a desktop other than a mobile device or you want to do something 
different. In the case here, wp_app_json mayble could help.
Code: 
Author: Zxial 
Web: http://zxial.me

WP APP JSON

The WP-APP-JSON is a plugin that provide json data to mobile apps, you can use keywords to search your posts and get detail webpage.

C. Johnson

This plugin implements a <a href="http://www.humanized.com/weblog/2006/04/25/no_more_more_pages" rel="nofollow ugc">“Humanized History”</a> feature for WordPress 
archives, using some PHP glue on the back end and some unobtrusive 
JavaScript on the front-end. In JavaScript-enabled browsers, Humanized 
History eliminates the need for users to click on “previous posts” links to 
read back through your archives; instead, when users get near the bottom of 
the current page of posts, the included JavaScript automatically displays 
more posts for them at the bottom of the page, providing a magic endless 
scrollbar that scrolls through your entire archives, in place of traditional 
page chunking.
Search robots and browsers without JavaScript enabled will see the same old 
pages with previous page/next page links, so you lose nothing in accessibility 
or friendliness to search engines.
The plugin was inspired by the discussion of the concept by Aza Raskin at 
<a href="http://www.humanized.com/weblog/2006/04/25/no_more_more_pages" rel="nofollow ugc">Humanized (2006-04-25): No More Pages?</a>. To see a sample of the feature as 
implemented in WordPress, go to <a href="http://projects.radgeek.com/" rel="nofollow ugc">http://projects.radgeek.com/</a> and scroll down 
toward the bottom of the page.
Don’t make your readers ask you for more content. Just give it to them.
<h3>Templates and Styling</h3>
If your <code>index.php</code> and <code>archive.php</code> templates provide previous page / next 
page links at the bottom of the content, you will probably want to remove these 
links from your templates. The plugin automatically provides its own previous 
page / next page links at the bottom of the front page and archive pages.
Many WordPress templates (including the default “Kubrick” template) display 
posts differently depending on whether they are in archives or in search 
results. “Kubrick,” for example, doesn’t display the post’s contents in search 
results. If you want to keep different formats for displaying archives as 
against search results, then use code something like this in your 
 template_post_display() function:
<pre><code>function template_post_display () {
 if (is_search()) {
 // display post for paged search results
} else {
 // display post for paged archives
}
}
</code></pre>
You may also want to add some styling to your template’s stylesheet for the 
navigation links that the plugin automatically generates. Here is what I use to 
display the “older posts” link at the far left side of the content column, and 
the “newer posts” link at the far right side on the same line:
<pre><code>#content .navigation {
 display: block; position: relative; list-style: none;
 text-align: center;
 margin-top: 10px; margin-bottom: 60px; margin-left: 0px; margin-right: 0px;
 padding: 0;
}

#content .navigation .prev {
 display: block; position: relative; list-style: none;
 top: 0; bottom: auto; left: 0; right: auto; width: 45%;
 margin: 0; padding: 0;
 text-align: left;
}

#content .navigation .next {
 display: block; position: absolute; list-style: none;
 top: 0; bottom: auto; left: auto; right: 0; width: 45%;
 margin: 0; padding: 0;
 text-align: right;
}
</code></pre>
If you want to change the appearance of the “Getting more content for you…” 
status indicator, then add a rule to your CSS stylesheet for the class 
 humanized-history-getting-more. E.g., to create a dark translucent box that 
floats over the footer material below:
<pre><code>.humanized-history-getting-more {
 position: absolute;
 width: auto; height: auto;
 border: 3px solid #505050;
 padding: 0.25em 1.0em;
 background-color: #777777;
 opacity: 0.85;
 z-index: 10000;
}<h3>Feedback</h3>
</code></pre>
Comments, questions, applause, brickbats, and bug reports should be directed to 
Charles Johnson at <a href="mailto:technophilia@radgeek.com" rel="nofollow ugc">technophilia@radgeek.com</a>. Other ways to get in touch with 
me can be found through my web page at <a href="http://radgeek.com/contact" rel="nofollow ugc">http://radgeek.com/contact</a>. If you have 
a bug or odd behavior to report, please be sure to include as much of the 
following information as you can ascertain:
<ul>
<li>The version of the Humanized History plugin you are using</li>
<li>The version of WordPress you are using</li>
<li>The version of PHP that you are using</li>
</ul>
Enjoy!
<h3>License</h3>
The Humanized History for WordPress plugin is copyright © 2007-2008 by Charles 
Johnson. This program is free software; you can redistribute it and/or modify it 
under the terms of the <a href="http://www.gnu.org/copyleft/gpl.html" rel="nofollow ugc">GNU General Public License</a> as published by the Free 
Software Foundation; either version 2 of the License, or (at your option) any 
later version.
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. See the GNU General Public License for more details.

Humanized History for WordPress

Readers with JavaScript can scroll back automagically through your entire archives without "older posts" links.

WP APP JSON vs Humanized History for WordPress