
%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:

On this day in 1843, the first major wagon train heading for the Pacific Northwest sets out on the Oregon Trail with one thousand pioneers from Elm Grove, Missouri.
The Oregon Trail is a 2,000-mile (3,200 km) historic east-west wagon route and emigrant trail that connected the Missouri River to valleys in Oregon and locations in between. The eastern part of the Oregon Trail spanned part of the future state of Kansas and nearly all of what are now the states of Nebraska and Wyoming. The western half of the trail spanned most of the future states of Idaho and Oregon.
The beginnings of the Oregon Trail were laid by fur trappers and traders from about 1811 to 1840 and were only passable on foot or by horseback. By 1836, when the first migrant wagon train was organized in Independence, Missouri, a wagon trail had been cleared to Fort Hall, Idaho. Wagon trails were cleared further and further west, eventually reaching all the way to the Willamette Valley in Oregon. What became called the Oregon Trail was complete even as improved roads, “cutouts”, ferries and bridges made the trip faster and safer almost every year. From various “jumping off points” in Missouri, Iowa or Nebraska Territory, the routes converged along the lower Platte River Valley near Fort Kearny, Nebraska Territory and led to rich farmlands west of the Rocky Mountains.
From the early to mid 1830s and particularly through the epoch years 1846-1869 the Oregon Trail and its many offshoots were used by about 400,000 settlers, ranchers, farmers, miners, and businessmen and their families.
A young man in India has created a robot that’s already made its way into record books. How he hopes to enlist it in the army, reports Bangalore Mirror.
Shirur, who completed his engineering from Basaveshwara Engineering College, Bagalkot, has developed a 61mm x 54mm x 51mm robot that is so tiny that it's bound to go unnoticed by enemies.
It is meant for surveillance and destruction of the enemy through remote control.
Shirur, who was at Sahyadri College of Engineering to participate in Srishti 2012, a state-level project exhibition and competition, told Bangalore Mirror: ''Cameras fixed in the robot can send audio and video signals from a particular spot to the servers and one can operate it from remote places.
It can also function as an explosive when enemies lift it off the ground.''
Photo by Crystal
During World War II, wives of American military officers who lived at the Eagle Pass. Texas. base would often venture over the Rio Grande River to the nearby Mexican town of Piedras Negras. On one of these excursions, a group of women stopped at the Victory Club, a popular restaurant, for a bite to eat. And while happy to receive business, the maitre d’ who greeted the women, Ignacio Anaya, found himself in a bit of a predicament:
He couldn't locate the cook. Not wanting to turn away the patrons, he put on his chef's hat. He looked around the kitchen and threw together what he had, which according to “The Oxford Companion to American Food and Drink” consisted of neat canapes of tortilla chips, cheese, and jalapeno peppers.”
Ignacio was often called Nacho for short, and the dish was named after him. Nachos continued to gain popularity for the next 20 years, but really took off thanks to a man by the name of Frank Liberto, who began to sell them as stadium food at Arlington Stadium (home of baseball's Texas Rangers at the time). Liberto made one major tweak to Anaya’s nachos:
…because real cheese didn't have a great shelf life (and melting it would require an oven or broiler), Liberto devised a fast food form of Anaya's masterpiece that was part cheese and part secret ingredients. The new sauce didn't need to be heated and, when it came to shelf life, it could likely survive a nuclear blast.
And so the nacho was born, with a missing chef to thank for it.
Photo by Luca
%<plugin>_<setting>%, for example, %HEADLINESPLUGIN_SHORTDESCRIPTION%. Note: Don't modify the settings here; copy and customize the settings in Main.TWikiPreferences. For example, to customize the USERAGENTNAME setting, create a HEADLINESPLUGIN_USERAGENTNAME setting in Main.TWikiPreferences.
0, default: 60 100 getUrl() method. Default: yes 20 TWikiHeadlinesPlugin/2.21
* Set USERAGENTNAME = TWikiHeadlinesPlugin/2.21
* 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>
$TWiki::cfg{PROXY}{HOST} - proxy host, such as "proxy.example.com";
$TWiki::cfg{PROXY}{PORT} - proxy port, such as "8080";
$TWiki::cfg{PROXY}{SkipProxyForDomains} - domains excluded from proxy, such as "intra.example.com, bugs.example.com";
| 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-2009, Peter Thoeny, TWIKI.NET; 2005-2007, Michael Daum http://wikiring.de |
| License: | GPL (GNU General Public License) |
| Plugin Version: | v2.21 - 12 Feb 2009 |
| Change History: | |
| 12 Feb 2009: | {PROXY}{HOST} supports domain with and without protocol -- Peter Thoeny |
| 06 Feb 2009: | added {PROXY}{SkipProxyForDomains} configure setting, added USERAGENTNAME plugin setting -- Peter Thoeny |
| 11 Dec 2008: | added {PROXY}{HOST} and {PROXY}{PORT} configure settings -- Peter Thoeny |
| 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 |