%HEADLINES{"..."}%
| Parameter | Explanation | Default |
|---|---|---|
"..." |
source of RSS feed; this can be an url (starting with http) or a web.topic location for internal feeds | None; is required |
href="..." |
(Alternative to above) | N/A |
refresh="60" |
Refresh rate in minutes for caching feed; "0" for no caching |
Global REFRESH setting |
limit="12" |
Maximum number of items shown | Global LIMIT setting |
header |
Header. Can include these variables: - $channeltitle, $title: title of channel (channel.title) - $channellink, $link: link of channel (channel.link) - $channeldescription, $description: description (channel.description) - $channeldate, $date: publication date of the channel (channel.pubDate) - $rights: copyrights of the channel (channel.copyright) - $imagetitle: title text for site (image.title) - $imagelink: link for site (image.link) - $imageurl: URL of image (image.url) - $imagedescription: description of image (image.description) |
Global HEADER setting |
format |
Format of one item. Can include these variables: - $title: news item title (item.title) - $link: news item link (item.link) - $description: news item description (item.description) - $date: the publication date (item.pubDate, item.date) - $category: the article category (item.category) |
Global FORMAT setting |
header and format parameters might also use variables rendering the dc, image and
content namespace information. Note, that only bits of interest have been implemented
so far and those namespaces might not be implemented fully yet.
dc namespace dc namespace info,
that could be used in header and format. Nnote, that some of the variables are
already used above. This is done by purpose to use different feeds with the
same formating parameters. If there's a conflict the non-dc tags have higher precedence,
i.e. a <title> content </title> is prefered over
<dc:title> content </dc:title> . image namespace image:item is converted into an <img> tag using the following mappings: src: image url (rdf:about attribute of the image.item tag)
alt: image title (title)
width: image width (image:width)
height: image height image:height)
content namespace
%HEADLINES{"http://slashdot.org/slashdot.rdf"
header="*[[$link][$title]]:* $description"
format="$t* [[$link][$title]]"
}%
to get the latest Slashdot news as a bullet list format:
%HEADLINES{"http://www.business-opportunities.biz/feed" limit="3"}%
to get the latest postings on the "Business Opportunities" weblog:

The rise of 5-Hour began in the spring of 2003, when Bhargava found himself at a natural products trade show in Anaheim, Calif. At one booth the sales reps peddled a 16-ounce concoction claiming to boost productivity for hours. Bhargava took a swig. ''For the next six or seven hours I was in great shape,'' he says. ''I thought, Wow, this is amazing. I can sell this.''
Right away, though, he knew 16 ounces wouldn't sell. He didn't want to compete with Red Bull, at the time new to the market. Nor did he want to share fridge space with Coke or Pepsi. ''I thought, If I'm tired, am I also thirsty? Is that like having a headache and a stomachache? It didn't make any sense.'' He glanced at the ingredients label and made a mental note. Six months later his version was on the shelves, two ounces of caffeine-infused B vitamins such as niacin mixed with acids like taurine.
Bhargava's team still had to convince stores and buyers alike that their product was safe. The initial job of getting 5-Hour Energy on the shelves went to Rise Meguiar, Living Essentials' vice president of sales and the only woman on a team of 17. Health chain GNC was the first to bite, agreeing to stock 5-Hour in 1,200 of its stores in 2004. Slowly but surely, Walgreens, Rite Aid and regional chains like Sheetz followed.

Yesterday I posted that Apple’s iPhone business was larger than all of Microsoft. Some of you said, “well good for them, but what about us?” Today, I’ve found a report that indicates that nearly half a million programmer jobs/small businesses have been created by people programming apps for devices like the Apple iPhone and iPad since 2007!
Where the Jobs Are: The App Economy [PDF]:
The incredibly rapid rise of smartphones, tablets, and social media, and the applications-“apps”-that run on them, is perhaps the biggest economic and technological phenomenon today. Almost a million apps have been created for the iPhone, iPad and Android alone, greatly augmenting the usefulness of mobile devices.
On an economic level, each app represents jobs-for programmers, for user interface designers, for marketers, for managers, for support staff. But how many? Conventional employment numbers from the Bureau of Labor Statistics are not able to track such a new phenomenon. So in this paper we analyze detailed information from The Conference Board Help-Wanted OnLine database, a comprehensive and up-to-the-minute compilation of want ads, to estimate the number of jobs in the App Economy.
This analysis shows that the App Economy now is responsible for roughly 466,000 jobs in the United States, up from zero in 2007 when the iPhone was introduced.

Now the economics of large-scale production runs carried out overseas are being disrupted by the possibility of making, selling and delivering millions of manufactured items one unit at a time, right next to the customer.
The question most people ask when thinking about the possibilities of 3D printing is: which of our existing products could we make with it? This is what happened when people first discovered mechanical power of steam engines: they started asking whether it would be possible to make a mechanical horse and cart? For a long time, the results were impractical mechanical replicas of a horse and cart, like the weird contraption shown above. It took more than a hundred years before people were able to think through the possibilities of mechanical power and developed comfortable and convenient transportation devices (cars) that were unlike any horse and cart we had ever seen.
Similarly, with digital manufacture, the important question is not which of our existing products can we make but rather: what can we do with this new technology that we couldn't even dream of doing before?
%<plugin>_<setting>%, for example, %HEADLINES_SHORTDESCRIPTION%
0, default: 60 100 getUrl() method, Default: yes 20
* Set HEADER = <div class="headlinesChannel"><div class="headlinesLogo"><img src="$imageurl" alt="$imagetitle" border="0" />%BR%</div><div class="headlinesTitle">$n---+!! <a href="$link">$title</a></div><div class="headlinesDate">$date</div><div class="headlinesDescription">$description</div><div class="headlinesRight">$rights</div></div>
* Set FORMAT = <div class="headlinesArticle"><div class="headlinesTitle"><a href="$link">$title</a></div>$n<span class="headlinesDate">$date</span> <span class="headlinesCreator"> $creator</span> <span class="headlinesSubject"> $subject </span>$n<div class="headlinesText"> $description</div></div>
| File: | Description: |
|---|---|
data/TWiki/HeadlinesPlugin.txt | plugin topic |
pub/TWiki/HeadlinesPlugin/style.css | default css |
lib/TWiki/HeadlinesPlugin.pm | plugin perl module |
lib/TWiki/HeadlinesPlugin/Core.pm | plugin core |
HeadlinesPlugin_installer.pl to automatically check and install other TWiki modules that this module depends on. You can also do this step manually.
| Name | Version | Description |
|---|---|---|
| Digest::MD5 | >=2.33 | Required. Download from CPAN:Digest::MD5 |
| LWP::UserAgent | >=5.803 | Optional. Download from CPAN:LWP::UserAgent |
| Plugin Author: | TWiki:Main.PeterThoeny, TWiki:Main.MichaelDaum |
| Copyright ©: | 2002-2006, Peter Thoeny; 2005-2007, Michael Daum http://wikiring.de |
| License: | GPL (GNU General Public License) |
| Plugin Version: | v2.12 |
| Change History: | |
| 13 Sep 2007: | fixed parsing of content:encoded |
| 23 Jul 2006: | improved atom parser; if a posting has no title default to 'Untitled' |
| 26 Apr 2006: | added lazy compilation |
| 10 Feb 2006: | packaged using the TWiki:Plugins/BuildContrib; minor fixes |
| 03 Feb 2006: | off-by-one: limit="n" returned n+1 articles; make FORMAT and HEADER format strings more robust |
| 23 Jan 2006: | released v2.00 |
| 05 Dec 2005: | internal feed urls must be absolute |
| 02 Dec 2005: | added web.topic shorthand for internal feeds |
| 29 Nov 2005: | fixed CDATA handling |
| 21 Nov 2005: | added ATOM support; extended RSS support; added dublin core support; added content support; optionally using LWP to fetch feeds to follow redirections; corrected CPAN dependencies ; recoding special chars from html integer to entity encoding to increase browser compatibility; added css support; use getWorkArea() if available |
| 11 May 2005: | TWiki:Main.WillNorris: added DevelopBranch compatability |
| 31 Oct 2004: | Fixed taint issue by TWiki:Main.AdrianWeiler; small performance improvement |
| 29 Oct 2004: | Fixed issue of external caching if mod_perl or SpeedyCGI is used |
| 02 Aug 2002: | Implemented caching of feeds, thanks to TWiki:Main/RobDuarte |
| 11 Jun 2002: | Initial version (V1.000) |
| Perl Version: | 5.8 |
| TWiki:Plugins/Benchmark: | GoodStyle 100%, FormattedSearch 99.5%, HeadlinesPlugin 94% |
| Plugin Home: | TWiki:Plugins/HeadlinesPlugin |
| Feedback: | TWiki:Plugins/HeadlinesPluginDev |
| Appraisal: | TWiki:Plugins/HeadlinesPluginAppraisal |