r2 - 2009-08-29 - 21:55:14 - TWikiContributorYou are here: TWiki >  TWiki Web  > HeadlinesPlugin

Headlines Plugin

Description

This plugin displays RSS and ATOM feeds from news sites. Use it to build news portals that show headline news.

Note: Syndic8.com ( http://www.syndic8.com/ ) lists many RSS feeds.

Syntax Rules

%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
touch="..." Touch (edit/save) topics if the feed has updates. Specify a comma-space delimited list of TopicNames or Web.TopicNames, such as "%TOPIC%, NewsLetter". Useful to send out newsletter using MailerContrib, showing new feeds since last newsletter. To update feeds, visit topics with feeds in regular intervals (using cron with wget or the like). N/A
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

The 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.

Rendering the dc namespace

The following variables are extracting the 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> .

  • $title: channel/article title (dc:title)
  • $creator: channel creator (dc:creator)
  • $subject: subject text; this will also add an image according to the subject hash list, see above (dc:subject)
  • $description: ... (dc:description)
  • $publisher: the channel/article publisher (dc:publisher)
  • $contributor: ... (dc:contributor)
  • $date: ... (dc:date)
  • $type: ... (dc:type)
  • $format: ... (dc:format)
  • $identifier: ... (dc:identifier)
  • $source: ... (dc:source)
  • $language: ... (dc:language)
  • $relation: ... (dc:relation)
  • $coverage: ... (dc: coverage)
  • $rights: ... (dc: rights)

Rendering the image namespace

An 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)

Rendering the content namespace

The variable $content is refering to the <content:encoding> content </content:encoding>.

Examples

Slashdot News

Write

%HEADLINES{ "http://slashdot.org/slashdot.rdf" 
  header="*[[$link][$title]]:* $description" 
  format="$t* [[$link][$title]]"
  limit="4"
}%
to get the latest Slashdot news as a bullet list format:

HeadlinesPlugin ERROR: 501 Protocol scheme 'https' is not supported (Crypt::SSLeay or IO::Socket::SSL not installed)

Business Opportunities Weblog

Write

%HEADLINES{ "http://www.business-opportunities.biz/feed" limit="2" }%

to get the latest postings on the "Business Opportunities" weblog:

Tue, 27 Sep 2016 15:20:14 +0000
The original blog about business opportunities and business ideas for small business entrepreneurs
Mon, 26 Sep 2016 14:11:30 +0000 Laurie B

4 Simple Businesses You Can Run From Home

There are many compelling reasons to want to work from home. Perhaps you have small children at home or you can't stand office politics. Or, maybe you just cannot take the one hour commute to work every day - each way. Whatever your reason, I'm sure it's a good one. For me, I just like waking up a bit later, working in my pajamas if I want to and never listening to a boss I find to be a complete imbecile.

The good news is, as technology progresses, working from home (or telecommuting) is becoming much more accessible. Both self-employment and job opportunities are popping up everywhere; making it that much easier for you to work and/or make money from the comfort of home.

Here are few suggestions we have for you:

 

1. Open An Online Store:     

Online marketplaces such as Ebay and Amazon have made it very easy to set up a business selling goods online. You don't need a website or any expensive overhead. All you need is a product and a Selling account and you are in business.

If you need help selecting a product, check out sites like Alibaba where you can find almost any type of product imaginable. I recommend you sell what you like. For instance, if you are really into mountain biking and know a lot about quality bikes and gear, you could specialize in that. It really helps to enjoy what you sell so choose a product you really like or believe in.

While you won’t need to pay business rent or have expensive overhead costs (at least not at first), you will need to set up a home office for you to comfortably work in. I recommend you find some out-of-the-way place inside your home that is quiet. You will most likely need a desk, printer, phone and file cabinet to store your important work. As you begin to set up your office, you will find there are many online stationery suppliers  that have everything you need to set up the perfect home office – with a click of a button.

2. Become a Personal Tutor: 

If you have a talent, this can be a great business for you. Do you play an instrument, can you speak a different language, play the flute or or are you crazy good at math? If so, why not share your talent with others through tutoring and receive payment for all that knowledge you have. Tutoring is a huge industry and people can make a nice living doing what they know and love. All you need is your knowledge, some basic people skills and maybe some patience. List your business on Craigslist.com or find an agency to sign up with. Today, it is easier than ever to become a tutor for virtually no cost at all.

3. Become A Stock Trader: 

This one is not for the faint of heart as it certainly comes with a lot of risk. However, if you do have a love of the stock market, and the personality type to deal with the rise and fall of the stock market, perhaps trading could be for you. The invention of the internet and trading sites such as Trading 212, have certainly lowered the barriers to entry in this profession and made trading a profession that can easily be done from home.

Trading is a very flexible occupation and you can do it as little or as much as you like. It is important to remember that trading is not an easy occupation. It may take many months and perhaps thousands of dollars in courses to become good at it. You also have to do a lot of research on the companies you are interested in investing in – and the changes in the market can wipe out all of your investment if you are not careful.

4. Become A Child Care Provider:

Taking care of children for parents who need to work, shop, date, dine out and even travel has been a profession for centuries and is a great way to earn money from home. If you love children, then this may well be the perfect business opportunity for you. You can watch one child or open your business up to watching a few at a time. It’s up to you. Craigslist.com, local school’s, agencies and word of mouth are the best ways to get your message out there about our business. This is another great business you can start with little to no investment and if you love children, it is  a no brainers.

 

 

Wed, 21 Sep 2016 00:31:33 +0000 Laurie B

Working in a field service environment such as the utilities sector, comes with challenging environments and conditions in which the standard consumer device simply cannot perform.

Water, dust and debris can all spell disaster for today's modern devices, never mind dramatic changes in temperature or falls from a height. Products that offer constant functionality and extreme durability are essential for the mobile worker and provide greater overall performance. Software and devices that are suitable in the field service environment can be hard to come by, so here's a list of key points and features to look out for when searching for your next device.

Latest technology

Having access to the latest technology is a must in this day and age. Being able to work productively and efficiently is essential for all roles regardless of where and when you work. Working in most field service roles means you need the ability to access and communicate information in order to work effectively. Most work will inevitably be carried out in hazardous or remote locations, both of which provide far from optimal working conditions.

Rugged laptops and devices with the technological ability to perform are the answer to this problem. These mobile devices offer super-fast processor flash storage, high quality graphics, quick performance and the multi-tasking capability that's necessary in challenging work environments. For example, covering a full shift or deployment can be a challenge without using the latest developments in technology, like hot-swappable batteries that allow you to switch batteries without shutting down or interruption.

 

Security features

Keeping your data, information and work safe is always important, although it can be a difficult task. Tablets and mobile devices can be equipped with a variety of security features and software to increase security and protection. For example, incorporating software which disables your device once it detects an unauthorised entrance should be a first precaution.

You can even equip yourself with anti-tampering devices and access scanners to add extra layers of protection to your data.

 

Hardwearing screens

Screens are by far the most important part of any device, but they're also the most susceptible to damage. Finding a screen that's functional, good quality and durable is a challenge, but they are available and almost essential for operatives working out in the field. One manufacturer's revolutionary Lumibond 2.0 technology, for example, offers an extremely durable screen which bonds a glass display with a touch screen and an LCD, enhancing touch functionality whilst providing a more readable display in all conditions.

While tapping, pinching and zooming is second nature to consumer device users, projected capacitive multi-touch technology doesn’t work with gloves on or in the rai. Lumibond screens, on the other hand, allow you to use gloves and pens as well as your fingers, even when the screen is wet.

 

RUGGED-LAPTOP 300w, RUGGED-LAPTOP-640x437.jpg 640w" sizes="(max-width: 588px) 100vw, 588px" />

Built for extreme environments

Being able to work in any environment is critical. Altitude, temperature, precipitation, water and dust can all spell disaster for most standard electronic devices, which isn't ideal for the operative in the field trying to communicate with their base.  From the freezing cold to heat as high as 60°C, you need ruggedized equipment with integrated heaters and optically bonded displays that can cope in extreme temperatures.

Many rugged devices built for utility engineers are ATEX certified, meaning the product has been tested for performance and functionality in Zone 2, where there is the risk of potentially explosive atmospheres from flammable gases, vapours, liquids, dust and ignitable fibres.

 

Multi-functional tools

Working in the field often means the number of devices you can carry are limited so it makes sense to purchase items that can complete multiple tasks. Rugged devices that are designed with utility engineers in mind are often able to capture a wide range of data, enabling maintenance staff to maintain assets and manage parts. For example, rugged devices often come fully equipped with barcode scanners that are capable of capturing both 1D and 2D codes, up to three times faster and more accurately than standard scanners, from a distance of nine inches.

You can find models that also feature integrated high-frequency RFID readers, so your staff can scan electronic data from tags and capture positioning data, in addition to tracking purposes; saving businesses from buying multiple devices to complete different tasks effectively.

Plugin Settings

Plugin settings are stored as preferences variables. To reference a plugin setting write %<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.

  • One line description, shown in the TextFormattingRules topic:
    • Set SHORTDESCRIPTION = Show headline news in TWiki pages based on RSS and ATOM news feeds from external sites

  • Refresh rate in minutes for cached feeds. Disable caching: 0, default: 60
    • Set REFRESH = 60

  • Maximum number of items shown. Default: 100
    • Set LIMIT = 100

  • Use LWP::UserAgent, or fallback to TWiki's internal getUrl() method. Default: yes
    • Set USELWPUSERAGENT = yes

  • Timeout fetching a feed using the LWP::UserAgent. Default: 20
    • Set USERAGENTTIMEOUT = 20

  • Name of user agent. Default: TWikiHeadlinesPlugin/2.21
      * Set USERAGENTNAME = TWikiHeadlinesPlugin/2.21

  • Default header: (variables are explained in the syntax rules)
      * 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>

  • Default format of one item: (variables are explained in the syntax rules)
      * 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>

  • Values taken from configure: (only supported if CPAN:LWP is installed)
    • $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";

Style Sheets

The default HEADER and FORMAT settings use the following styles. See the style.css file defining the default CSS properties (indentation illustrates enclosure).

  • headlinesRss: output of the HeadlinesPlugin (div)
    • headlinesChannel: channel header (div)
      • headlinesLogo: channel logo (div)
      • headlinesTitle: channel title (div)
      • headlinesDate: channel date (div)
      • headlinesDescription: channel description (div)
      • headlinesRight: channel copyright (div)
    • headlinesArticle: one news item (div)
      • headlinesTitle: article title (div)
      • headlinesDate: article date (span)
      • headlinesCreator: author of article (span)
      • headlinesSubject: subect category of the article (span)
      • headlinesText: article text (div)

Plugin Installation Instructions

  • Download the ZIP file.
  • Unzip it in your twiki installation directory. Content:
    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
    Check if above examples show a news feed instead of variable.
  • Optionally, run HeadlinesPlugin_installer.pl to automatically check and install other TWiki modules that this module depends on. You can also do this step manually.
  • Alternatively, manually make sure the dependencies listed in the table below are resolved.
    NameVersionDescription
    Digest::MD5>=2.33Required. Download from CPAN:Digest::MD5
    LWP::UserAgent>=5.803Optional. Download from CPAN:LWP::UserAgent

Plugin Info

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.3 - 29 Aug 2009
Change History:  
29 Aug 2009: added touch parameter -- Peter Thoeny
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

-- TWiki:Main.PeterThoeny - 29 Aug 2009

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r2 < r1 | More topic actions
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
Note: Please contribute updates to this topic on TWiki.org at TWiki:TWiki.HeadlinesPlugin