hamzarauf

Show Latest posts news ticker at bottom…
For backwards compatibility, if this section is missing, the full length of the short description will be used, and 
Markdown parsed.
A few notes about the sections above:
<ul>
<li>“Contributors” is a comma separated list of wordpress.org usernames</li>
<li>“Tags” is a comma separated list of tags that apply to the plugin</li>
<li>“Requires at least” is the lowest version that the plugin will work on</li>
<li>“Tested up to” is the highest version that you’ve successfully used to test the plugin. Note that it might work on 
higher versions… this is just the highest one you’ve verified.</li>
<li>
Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use <code>/trunk/</code> for 
stable.
Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so 
if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>4.3</code>, then it is <code>/tags/4.3/readme.txt</code> that’ll be used 
for displaying information about the plugin. In this situation, the only thing considered from the trunk <code>readme.txt</code> 
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in 
your in-development version, without having that information incorrectly disclosed about the current stable version 
that lacks those changes — as long as the trunk’s <code>readme.txt</code> points to the correct stable tag.
If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where 
you put the stable version, in order to eliminate any doubt.
</li>
</ul>
<h3>Arbitrary section</h3>
You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated 
plugins where more information needs to be conveyed that doesn’t fit into the categories of “description” or 
“installation.” Arbitrary sections will be shown below the built-in sections outlined above.
<h3>A brief Markdown Example</h3>
Ordered list:
<ol>
<li>10 Latest Blog posts </li>
<li>Rotating text </li>
<li>Current time</li>
</ol>
Here’s a link to <a href="https://wordpress.org/" title="Your favorite software" rel="ugc">WordPress</a> and one to <a href="http://daringfireball.net/projects/markdown/syntax" title="Markdown is what the parser uses to process much of the readme file" rel="nofollow ugc">Markdown’s Syntax Documentation</a>. 
Titles are optional, naturally.
Markdown uses email style notation for blockquotes and I’ve been told:
<blockquote>
Asterisks for emphasis. Double it up for strong.
</blockquote>
<pre><code><?php code(); // goes in backticks ?>
</code></pre>

Posts News Ticker

Awesome !

michael.bartel

A simple ticker plugin for wordpress. It supports multiple tickers. You can define an update interval 
in minutes in which the client updates it’s message list from the server. This update request includes 
new messages, which have been posted until the last update. You can also specify the amount of messages that 
the client fades through and the time each message stays on the screen. Each message is stored with an 
creation timestamp. You can tell the ticker only to show messages not older than a defined number of minutes. 
If there are no messages to display, then the ticker turns itself invisible.
Every ticker has it’s own RSS Feed, which can be received by either given it’s ID or name.
If you want to use the SimpleTicker data from an other application such as an iPhone or Android App, you can 
get all ticker data and messages via an JSON based API. It is also possible to add and delete messages 
with the JSON API. Your application will need a password for each ticker, if it want’s to add or delete messages.
<h3>Copyright</h3>
WordPress – Plugin “SimpleTicker” 
(c) 2013 Michael Bartel, MIT/X11-license 
eMail: Michael.Bartel@gmx.net
<h3>History</h3>
Version 0.95 
 – Refactoring
Version 0.9 
 – Bugfixing
Version 0.8 
 – Improvements to the Android App
Version 0.7 
 – Android App improvments
Version 0.6 
 – Android App and Bug fixes
Version 0.5 
 – added RSS Feed
Version 0.4 
 – added Template-Engine and XML API
Version 0.3 
 – added JSON API
Version 0.2 
 – added auto-hide
Version 0.1 
 – first version V3.1
<h3>Use Ticker</h3>
To use the ticker on your wordpress pages or articles copy the following text into the page. After that replace #id# with the id of your ticker.
[simpleticker id=#id#]
Example for ticker 1 (with id 1): [simpleticker id=1]
<h3>RSS Feed</h3>
You will receive the content of the RSS Feed for a specific ticker when you call SimpleTicker.php from your plugin folder (URL) and append ‘?action=rssFeed&id=1’. Instead of id=1 you can use name=Tickername.
<h3>APIs</h3>
All APIs are handled with GET paramters. The ‘action’ parameter specifys which function you want to call.
<h3>JSON API</h3>
Instead of the using the id parameter with the tickers ID, you can use the name parameter with it’s name. The JSON API provides the following functionalities:
<ul>
<li>jsonGetTickerList – Returns a full list of all available tickers containing the tickers id and name.</li>
<li>jsonGetTickerMessages – Returns a list with the last 50 messages of a ticker. You have to specify the ticker by giving it’s ID in the parameter ‘id’. The list contains the message id, the message itself and the createdOn timestamp.</li>
<li>jsonManageTicker – You need a password to call the action. All further parameters are given in a BASE64 encoded encrypted JSON string provided as GET parameter named ‘data’. You have to set the ‘id’ parameter as above to define a ticker. The JSON string contains an action attribute which can either be ‘addMessage’ or ‘removeMessage’. The ‘addMessage’ actions takes an additional ‘message’ attribute containing the new message and the ‘removeMessage’ action takes an ‘id’ attribute.</li>
</ul>

SimpleTicker

A simple ticker plugin for wordpress. It supports multiple tickers. You can define an update interval

Posts News Ticker vs SimpleTicker