%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]]$n $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:

There’s a lot of excitement about the potential of autonomous drones, be they nimble quadcopters or longer-range fixed wing or hybrid aircraft. A group of students from Singularity University, for example, has a project called MatterNet working to provide transportation infrastructure for light cargo in regions of Africa where roads wash out for half the year.
Closer to home, these drones are not yet legal for commercial use, while government agencies are using them secretly.
Here’s one useful idea: A small set of medical drones scattered around the city. Upon emergency call, they can fly, via a combination of autonomous navigation and remote-human-operated flying at the end, to any destination in the city within a couple of minutes. Call 911 and as soon as you say it’s a medical emergency the drone is on the way. When it gets there, the human operator lands it or even sends it in a balcony on tall buildings with balconies. Somebody has to carry it to the patient if they are far from the outside.
When it gets to the patient it has a camera and conferencing ability to a remote doctor can examine the patient and talk to people around the patient to ask them questions or give them instructions. It also could contain one of those “foolproof defibrillator” modules able to deal with many kinds of heart attacks. They are already in many buildings but this way they could be anywhere. It’s more useful than a taco.

Weather Underground, a site that compiles local data collected by 24,000 weather geeks with sensors on their roofs, this week released a free tool for businesses to use to look for patterns in their sales related to the weather. Anyone can punch in a location and time period to download a spreadsheet with detailed weather data. The file also has a place to enter daily sales (which comes prepopulated with fake sales numbers) and charts that show the sales numbers in relation to temperatures, precipitation, and dew point (a measure of humidity). The spreadsheet calculates the correlation between sales and those three weather metrics to show which have a meaningful relationship.
Weather Underground's main business since it started in 1995 has been targeting ads on its site for brands that want to reach consumers during certain weather conditions. Companies can, for example, offer getaway deals to Hawaii during nasty winter storms, or hawk lawn furniture and garden supplies on the first sunny weekend of spring.

Once you pop the top of a tube of potato chips, it can be hard to stop munching its contents. But Cornell researchers may have found a novel way to help: Add edible serving size markers that act as subconscious stop signs.
As part of an experiment carried out on two groups of college students (98 students total) while they were watching video clips in class, researchers from Cornell’s Food and Brand Lab served tubes of Lays Stackables, some of which contained chips dyed red.
In the first study of the research, which is published online this month in Health Psychology, a journal of the American Psychological Association, the red chips were interspersed at intervals designating one suggested serving size (seven chips) or two serving sizes (14 chips); in the second study, this was changed to five and 10 chips.
Unaware of why some of the chips were red, the students who were served those tubes of chips nonetheless consumed about 50 percent less than their peers: 20 and 24 chips on average for the seven-chip and 14-chip segmented tubes, respectively, compared with 45 chips in the control group; 14 and 16 chips for the five-chip and 10-chip segmented tubes, compared with 35 chips in the control group.
Photo by Robin Wishna.
%<plugin>_<setting>%, for example, %HEADLINESPLUGIN_SHORTDESCRIPTION%. Note: Don't modify the settings here; copy and customize the settings in Main.SitePreferences. For example, to customize the USERAGENTNAME setting, create a HEADLINESPLUGIN_USERAGENTNAME setting in Main.SitePreferences.
0, default: 60 100 getUrl() method. Default: yes 20 FoswikiHeadlinesPlugin/2.21.2
* Set USERAGENTNAME = FoswikiHeadlinesPlugin/2.21.2
* 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>
$Foswiki::cfg{PROXY}{HOST} - proxy host, such as "proxy.example.com";
$Foswiki::cfg{PROXY}{PORT} - proxy port, such as "8080";
$Foswiki::cfg{PROXY}{SkipProxyForDomains} - domains excluded from proxy, such as "intra.example.com, bugs.example.com";
configure, then you can still install manually from the command-line. See http://foswiki.org/Support/ManuallyInstallingExtensions for more help.
Check if above examples show a news feed instead of variable.
| Plugin Author: | TWiki:Main.PeterThoeny, Foswiki:Main.MichaelDaum (2005-2007) |
| Copyright: | © 2002-2009, Peter Thoeny, TWIKI.NET; 2005-2007, Michael Daum http://wikiring.de |
| License: | GPL (GNU General Public License) |
| Release: | 2.21.2 |
| Version: | 6822 (2010-03-21) |
| Change History: | |
| 09 Mar 2010: | can now use 0 properly with HEADLINESPLUGIN_REFRESH, HEADLINESPLUGIN_LIMIT, HEADLINESPLUGIN_USERAGENTTIMEOUT |
| 08 Mar 2009: | Ported without changes to Foswiki namespace by Kenneth Lavrsen and put under "Feel Free To Modify" in Foswiki context. |
| 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.008 |
| Home: | Foswiki:Extensions/HeadlinesPlugin |
| Support: | Foswiki:Support/HeadlinesPlugin |
Copyright © by the contributing authors. All material on this site is the property of the contributing authors.