Tags:
create new tag
, view all tags

Headlines Plugin

Show headline news in TWiki pages based on RSS and ATOM news feeds from external sites

Description

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

Notes:

  • RSS (Rich Site Summary) is an XML standard used to publish frequently updated works such as blog entries, news headlines and audio.
  • Atom is an XML syndication format used for web feeds.
  • Syndic8.com at http://www.syndic8.com/ lists many RSS and ATOM feeds.

Syntax Rules

%HEADLINES{"..."}%

ParameterSorted descending Explanation Default
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
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
href="..." (Alternative to above) N/A
header="..." Header. May 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. May 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
"..." Source of RSS or ATOM feed; this can be an url (starting with http) or a web.topic location for internal feeds None; is required

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. Note that some of the variables are already used above. This is done by purpose to use different feeds with the same formatting parameters. If there's a conflict the non-dc tags have higher precedence, i.e. a <title> content </title> is preferred 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 referring 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:

Business Opportunities Weblog

Write

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

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

Fri, 22 Nov 2019 02:02:02 +0000
The original blog about business opportunities and business ideas for small business entrepreneurs
Fri, 22 Nov 2019 02:01:59 +0000 Carrol Strain
Featured image from Fauxels on Pexels

In order to amplify the output of your business or department, you have to drill down to the core of what makes your company tick: people. Moreover, if you want to maximize your human resources, you must understand what factors influence individual workplace performance. Here's a rundown of some of the most potent elements.

Workplace Culture and Environment

People are directly influenced by their physical surroundings. They're also affected by the intangible factors within an office, such as the company culture. If the workplace environment is dark, gloomy, and hostile, that will show in employee performance. If the workplace is positive, upbeat, and inviting, good things will follow.

Therefore, strive to cultivate a workplace environment and culture that people want to be a part of. As employees feel more comfortable and engaged at work, you'll discover that this elevated state positively influences collaboration, communication, and creativity.

Expectations and Their Effect on Workplace Stress

Different people respond to unique motivating factors. Expectations are a good thing in business. However, you have to be careful in drawing the line between reasonable and overwhelming. When expectations are unrealistic, the pressure negatively affects performance.

''Workplace stress is a performance killer,'' writes Andra Picincu, MBA. ''In this competitive age, employees feel pressured to meet work demands and organizational goals. Approximately 40 percent say that their jobs are very or extremely stressful. About 73 percent of workers experience psychological symptoms due to stress, while 77 percent report stress-related physical symptoms.''

Expectations should be used to challenge and put healthy pressure on employees. However, they also need to be clear and realistic. Therefore, listen to your employees when they're stressed. Then figure out ways to get everyone in your workplace on the same page.

Management and Leadership

Think back to the best job you ever had, the one you really loved. In all likelihood, you had a pretty awesome boss. Now consider the worst job you ever had, the one that you made you hate waking up in the morning. Your boss was horrible, right?

There's a saying that people don't leave their jobs; they leave their bosses. If you want to maximize workplace performance, you have to consider the company management. Are the leaders hostile and aggressive, or are they highly supportive?

Health

Employee health matters, even in the workplace, in more ways than one. While you technically don't have any say in your employees' personal health issues, it's important to recognize just how influential chronic conditions can be in terms of morale and productivity. This goes for both minor and serious issues.

For example, take something like acid reflux. Employees who suffer from chronic acid reflux are overwhelmed by thoughts and feelings of discomfort. These feelings keep them from focusing on their jobs.

It also requires them to be on certain medications-such as Zantac-which have serious side effects, possibly including cancer of the stomach or bladder. Therefore, what starts as a minor problem can become a major issue that squashes every bit of an employee's productivity. Additionally, it can have a ripple effect throughout the workplace.

The same goes for chronic pain related to sitting at a desk all day. The less mobile people are, the more likely they are to suffer back, neck, and wrist pain. Again, you can't fix these health issues.

However, you can put systems in place that make it less likely for health problems to arise. For example, prioritizing superior ergonomics in the design of each individual workspace goes a long way toward addressing issues of repetitive stress.

RELATED ARTICLE: DIRECT AND INDIRECT COSTS INVOLVED IN WORKPLACE ACCIDENTS

Motivation in the Workplace

According to BusinessManagementIdeas.com, ''Motivation is the primary force that drives a person to action. It has a multiplier effect on increasing [a person’s] ability and willingness to work. Motivation engages [that person] in goal-directed behavior which helps in satisfying [their] needs. It is, therefore, the prime force that promotes job performance.''

So take the time to get to know each individual employee within your organization. In this way, you can begin to understand what motivates people on a case-by-case basis. For one person, it might be the opportunity to make a difference in the lives of others. For another person, it's strictly money. Understanding which factors motivate which people will help you implement superior leadership initiatives.

Cultivating a High-Performance Workplace

From a leadership perspective, cultivating a productive workplace that's characterized by high-performing individuals and exceptional output isn't easy. It takes hard work, strategic planning, and careful execution. Moreover, it must be optimized to the individuals within the four walls of your company.

However, once you have an idea of the factors that control and influence your team members, it becomes easier to push buttons and pull levers in a way that maximizes their value to the organization.

Take some time to review this article through the lens of your team and consider how you can make changes to your company's workplace performance.

Browse our blog for more great ideas about managing your office.

The post Factors That Affect Workplace Performance appeared first on Business Opportunities.

Thu, 21 Nov 2019 23:08:01 +0000 Carrol Strain
Featured image from Sazonoff on Yay Images

Most experienced Forex traders rely on more than one indicator.

However, beginning traders often feel overwhelmed by the number of indicators available. Should you use them all? Pick only one or two?

If you’re just starting out as a Forex trader, how can you know which indicator is right for you?

RELATED ARTICLE: HOW TO START A BUSINESS BASED ON YOUR BEST TALENTS

What Indicators Do Experienced Traders Use?

If you’re brand new to technical FX trading, you might think that your best bet would be to do what the masters do. In other words, all you’d need to do is follow the lead of some traders you admire and choose the indicators they use. Right?

Well, maybe not. An indicator that works well for an experienced Forex trader might not be all that great for a beginner.

For example, the MACD is a sophisticated and versatile Forex trading tool. However, all that sophistication is more than most beginners can deal with when they’re just getting used to the market.

Okay. So What Is a Good Indicator for a Beginner?

When you’re first starting out, you have a whole lot to learn. There’s everything you need to know about the market itself, for one thing. Then you need to choose a trading strategy and develop your routine.

That’s why most experts will tell you to take full advantage of your broker’s Forex demo account for the first few weeks at least.

Over time, you can educate yourself about the various indicators, learning each indicator thoroughly as you go.

However, in the beginning, moving averages are the best indicator for beginners.

Why?

It’s because when you use moving averages in your Forex trading, you’ll be learning the basics. Most of the other more sophisticated indicators are based on moving averages anyway.

So once you graduate to those more advanced indicators, you’ll have a better understanding of how they work. This can only be to your benefit in the long run.

Are There Others?

Of course there are other indicators that are relatively simple to use, especially in the beginning. For example, the relative strength index (RSI), used in conjunction with moving averages, can bring more clarity to your trading strategies.

Many traders agree that moving averages, whether simple or exponential, can be frustrating to work with because they give you only a limited amount of information. But you can use RSI along with moving averages, confirming one indicator against the other, before jumping into the market.

How Does the RSI Work?

The relative strength index works by reading the price action. In other words, it looks at currency pairs and determines whether a particular pair is being oversold or overbought.

If the price moves more than 70 in either direction, you’ll know the market is likely about to change direction. This gives you an opportunity to make a move.

Use Them Together for Best Results

Both the RSI and moving averages, used together, provide a good place to start for beginning Forex traders.

Once you master these two indicators, you can begin to learn about other more advanced ones.

It’s true that these two are fairly simple to use. However, they are versatile nonetheless. And they will help you to learn about the market as you develop your Forex trading strategies and gain experience as a trader.

The post Which Forex Indicator Is Right for You? appeared first on Business Opportunities.

Plugin Settings

Plugin settings are stored as preferences settings. Do not change the settings here, they are here only for illustration purposes showing the default values. Define the settings in Main.TWikiPreferences. For example, to customize the HEADLINESPLUGIN_USERAGENTNAME setting, add a * Set HEADLINESPLUGIN_USERAGENTNAME = ... bullet in Main.TWikiPreferences.

  • Refresh rate in minutes for cached feeds. Set to 0 to disable caching:
    • Set HEADLINESPLUGIN_REFRESH = 60

  • Maximum number of items shown:
    • Set HEADLINESPLUGIN_LIMIT = 100

  • Use LWP::UserAgent if set to 1, or fallback to TWiki's internal getUrl() method if set to 0:
    • Set HEADLINESPLUGIN_USELWPUSERAGENT = 1

  • Timeout fetching a feed using the LWP::UserAgent:
    • Set HEADLINESPLUGIN_USERAGENTTIMEOUT = 20

  • Name of user agent:
    • Set HEADLINESPLUGIN_USERAGENTNAME = TWikiHeadlinesPlugin/2011-07-08

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

This is a pre-installed plugin. TWiki administrators can upgrade the plugin as needed on the TWiki server.

Note: You do not need to install anything on the browser to use this plugin. The following instructions are for the administrator who installs the plugin on the TWiki server.

  • For an automated installation, run the configure script and follow "Find More Extensions" in the in the Extensions section.

  • Or, follow these manual installation steps:
    • Download the ZIP file from the Plugins home (see below).
    • Unzip HeadlinesPlugin.zip in your twiki installation directory. Content:
      File: Description:
      data/TWiki/HeadlinesPlugin.txt Plugin topic
      pub/TWiki/HeadlinesPlugin/style.css Default CSS
      lib/TWiki/Plugins/HeadlinesPlugin.pm Plugin Perl module
      lib/TWiki/HeadlinesPlugin/Core.pm Plugin core
    • Set the ownership of the extracted directories and files to the webserver user.
    • 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 configuration and testing:
    • Run the configure script, enable the plugin in the Plugins section
    • Configure the plugin: See plugin settings above.
    • Test if the installation was successful: See example above.

Plugin Info

  • 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

Plugin Author: TWiki:Main.PeterThoeny, TWiki:Main.MichaelDaum
Copyright: © 2002-2013 Peter Thoeny, TWiki.org
© 2005-2007 Michael Daum wikiring.de
License: GPL (GNU General Public License)
Plugin Version: 2013-02-16
2013-02-16: TWikibug:Item7091: Use TWISTY in installation instructions section and change history
2013-01-29: TWikibug:Item7131: HeadlinesPlugin doesn't match pattern in multiple lines.
2012-12-10: TWikibug:Item7070: HeadlinesPlugin doesn't support multiple disks.
2012-11-13: TWikibug:Item7016: Restore changes for earlier versions with LWP
2012-11-13: TWikibug:Item7020: Categorize TWiki Variable
2012-10-31: TWikibug:Item7016: Utilize <guid> value when it is available
2012-09-05: TWikibug:Item6837: Doc fixes
2011-07-17: TWikibug:Item6764: Add VarHEADLINES variable documentation; doc improvements; setting NO_PREFS_IN_TOPIC
2011-07-08: TWikibug:Item6725: Change global package variables from "use vars" to "our"
2010-05-16: TWikibug:Item6433: More doc improvements
2010-04-25: TWikibug:Item6433: Doc fix: Changing TWIKIWEB to SYSTEMWEB
2010-02-27: TWikibug:Item6313: Fixed bug in ATOM feed with <link ...></link> instead of <link ... /> -- Peter Thoeny
2009-09-30: fixed bug in lastBuildDate of feeds affecting touch parameter functionality -- Peter Thoeny
2009-08-29: 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
Plugin Benchmark: GoodStyle 100%, FormattedSearch 99.5%, HeadlinesPlugin 94%
Plugin Home: http://TWiki.org/cgi-bin/view/Plugins/HeadlinesPlugin
Feedback: http://TWiki.org/cgi-bin/view/Plugins/HeadlinesPluginDev
Appraisal: http://TWiki.org/cgi-bin/view/Plugins/HeadlinesPluginAppraisal

Related Topics: VarHEADLINES, TWikiPlugins, AdminDocumentationCategory, TWikiPreferences

Topic revision: r8 - 2013-02-16 - 18:01:51 - TWikiContributor
 
Copyright © 1999-2019 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.