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.

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:

Business Opportunities Weblog

Write

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

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

Sun, 25 May 2025 21:12:31 +0000
The original blog about business opportunities and business ideas for small business entrepreneurs
Sun, 25 May 2025 21:12:27 +0000 Carrol Strain

Retractors, both hand-held and self-retaining, are essential operating room tools. Each kind has particular abilities for different treatments. Surgeon- or assistant-operated hand-held retractors are active and responsive. For this reason, sensitive dissections requiring quick adjustments make hand-held retractors essential.

On the other hand, self-retaining retractors hold tissues apart. During protracted procedures, their qualities increase output by freeing the surgeon’s hands for other tasks.

Selecting the right tool calls for knowledge of each design’s advantages and disadvantages. The right selection influences both patient safety and surgical outcome. Therefore, examine the operating features of both retractor designs to assist in selecting the correct one for particular surgical scenarios.

RELATED ARTICLE: 5 TIPS FOR A BETTER MEDICAL PRACTICE

Understanding Hand-Held Retractors

Surgical retractors such as the June Medical Retractor are hand-held tools needing direct manual force to retract tissue. Clear visualization and operative field access call for constant manipulation. Made of surgical-grade stainless steel or other strong metals, these devices have numerous varieties. They come in an array of form and size so as to conform to specific anatomical sites and surgical requirements.

They allow for the dynamic nature of surgery so that the surgeon can make quick, sophisticated changes. However, they call for human endurance, and this is a drawback. Prolonged surgical procedures can cause operator fatigue, which could in turn affect the outcome. In other words, hand-held retractors require continual hands-on control.

Exploring Self-Retaining Retractors

Self-retaining retractors increase operative efficiency because they can retract without human intervention. Their frames or locking systems hold the retractor blades in place. Surgeons can then be freed to concentrate on technical operations. Famous frame systems such as the Balfour or Bookwalter can change to fit various surgical techniques and patient anatomies. This hands-free capability lessens physical strain on the surgical crew. Especially in deep cavities or under complicated, time-consuming operations, sight and accessibility are improved while exposure remains the same.

Comparing the Benefits and Limitations

Different features and pros and cons of hand-held and self-retaining retractors influence their application. Hand-held models are adaptable, as well as quick and easy to use. They are easy to maneuver, making them ideal for tasks that require frequent changes in the surgical field. Their Achilles heel? Long-term manual operation could lead to muscular fatigue.

Self-retaining techniques, in contrast, free the surgeon’s hands and enhance focus and flow by providing continuous tissue tension. However, in tiny surgical areas, they could be less nimble. A clumsy posture could unintentionally restrict access or sight. Choosing the finest equipment for optimal exposure calls for close attention to these pros and cons.

RELATED ARTICLE: WHAT ARE THE TOP SELLING MEDICAL DEVICES?

Choosing the Right Retractor for Your Needs

Several elements influence the choice of the ideal retractor. The kind of surgery, patient anatomy, and the surgeon’s knowledge and taste are all very important. Some prefer hand-held instruments for precise, sensitive exposure changes. Their adaptability and direct control are priceless. For lengthier scenarios needing consistent retraction, self-retaining devices provide obvious benefits. They prevent workers’ fatigue and allow for more speed and efficiency. Nonetheless, a team’s knowledge of retractors is important. The final choice should always be guided by patient safety with an eye toward the best patient outcome.

RELATED ARTICLE: INVESTING IN OVERSEAS AESTHETIC CLINICS

Conclusion

The choice between hand-held and self-retaining retractors significantly shapes the conduct of a surgical procedure. Success often hinges on this selection. Each category presents unique advantages for different surgical scenarios. Hand-held retractors offer superior flexibility for dynamic adjustments. Self-retaining models provide steady exposure, freeing the surgeon’s attention and reducing manual burden, which is critical during some cases. The decision integrates the specific surgical challenge, the patient’s anatomical landscape, and the collective expertise of the operating room team. Prioritizing patient well-being and effective surgical execution remains the guiding principle.

Image from Mikhail Nilov on Pexels.com

The post Which Is Better: Hand-Held or Self-Retaining Retractors? appeared first on BUSINESS OPPORTUNITIES.

Sat, 24 May 2025 17:39:45 +0000 Carrol Strain

In an industry notorious for high turnover and challenging working conditions, Chris Rapczynski has built Sleeping Dog Properties on a distinctly different model: prioritizing employees as the company’s most valuable asset. This approach has created an unusually stable workforce. Moreover, it directly contributed to the firm’s reputation for exceptional quality and client satisfaction.

The Value of Human Capital

Rapczynski’s commitment to his team starts with a fundamental recognition of their worth. “The human stock of our company is held in the highest regard,” he states. He uses financial terminology to emphasize that he views employees as investments rather than expenses.

This philosophy manifests concretely, beginning with compensation exceeding industry standards. “We are constantly entrenched with head hunters trying to recruit or steal my people, and so I’m always having to defend against that, which means I have to pay people more than the market,” Rapczynski explains.

While higher wages increase project costs, Rapczynski views this as an investment that yields returns through superior workmanship and efficiency. “I think where we make it up is we make it up in durability,” he notes. He stresses that he is referring to both project quality and employee retention. The continuity of having long-term employees who understand company standards and procedures creates value that offsets higher payroll expenses.

This financial commitment extends beyond base salaries to include comprehensive benefits and professional development opportunities. Rapczynski creates a workforce with exceptional capabilities and loyalty by investing in employees’ well-being and growth.

The results speak for themselves. While the construction industry averaged a 13% voluntary turnover rate in 2022, Sleeping Dog Properties maintains significantly better retention. In fact, many team members remain with the company for years or even decades.

Beyond economic benefits, Rapczynski fosters a workplace culture that values input from all team members. Field supervisors, project managers, and tradespeople are encouraged to contribute ideas and raise concerns. This creates both better solutions for clients and higher job satisfaction for employees.

Creating a Culture of Excellence

Beyond compensation, Rapczynski’s leadership philosophy centers on three core principles that guide the company: communication, competency, and cleanliness. These fundamentals create a structured yet supportive environment where employees can thrive.

“I feel like competency is underrated, underappreciated until it goes wrong,” Rapczynski observes. “My team and I present the best candidates that there are on the market, and that’s costly and valuable to a project. But if something’s done incorrectly, that’s even more costly.”

This focus on competency translates to comprehensive training programs and careful hiring practices. Rather than rushing to fill positions during busy periods, Sleeping Dog Properties maintains rigorous standards for new team members, ensuring they possess both technical skills and the right temperament for client-focused luxury construction.

Perhaps most distinctive is Rapczynski’s emphasis on jobsite cleanliness-a principle that might seem superficial but reflects deeper values. “If I threw a bunch of popcorn down on the carpet and asked you to find me the two white wire nuts that were there, the popcorn would camouflage the wire nuts,” Rapczynski explains. “Cleanliness is next to godliness.”

RELATED ARTICLE: SAFETY MEASURES FOR A CONSTRUCTION BUSINESS

This attention to order creates multiple benefits: safer working conditions, more efficient operations, and a visible demonstration of the company’s commitment to quality. Clean jobsites also communicate respect for clients’ homes, for the work itself, and for fellow team members.

The company’s culture extends beyond the workday through team-building activities, family events, and community service initiatives. Rapczynski believes these connections strengthen working relationships and reinforce shared values. The result is a team that functions cohesively across projects, with members who understand each other’s working styles and communicate effectively under pressure.

Rapczynski’s Thoughts on Developing Future Industry Leaders

Rapczynski’s employee-first approach includes substantial investment in career development and mentorship. Unlike firms that fear training employees who might eventually leave, Sleeping Dog Properties actively nurtures growth, recognizing that skilled, engaged employees deliver superior results while they remain with the company.

This commitment extends beyond his own team to the broader construction community. Rapczynski has mentored “disadvantaged and career-path-challenged individuals” interested in construction, helping them develop skills that create career opportunities. Through this outreach, he contributes to a more diverse, skilled construction workforce in the Boston area.

“I’ve always sought that from people who’ve gone ahead of me and seen the challenges that they presented,” Rapczynski says, describing his own experience with mentors. This perspective informs his willingness to guide others, creating a cycle of knowledge-sharing that strengthens the entire industry.

His leadership development philosophy focuses on transferring not just technical knowledge but also problem-solving approaches and client relationship skills. Team members learn to think independently and make decisions aligned with company values rather than simply following rigid protocols. This empowerment creates a more resilient organization capable of handling the complex challenges inherent in high-end construction.

The long-term vision includes preparing the company for eventual succession. “I think for the next generation is where my mindset is right now because I have to be forward-thinking about the long planning that it takes to get a company into a position where it can have a second generation,” Rapczynski explains. This planning demonstrates his commitment to creating an organization that outlasts his own leadership-a goal few construction company founders achieve.

“Most construction companies only survive a first generation of ownership,” he notes. “And I think that our company serves by empowering our leadership to take on the responsibilities in an ownership-type of capacity.”

RELATED ARTICLE: GUIDE TO BOOSTING EMPLOYEE ENGAGEMENT

Through this comprehensive approach to employee development, Rapczynski builds not just structures but people, creating a legacy that extends beyond physical buildings to the skills, values, and opportunities he’s provided to his team and the wider construction community. This human-centered philosophy may prove to be his most enduring contribution to Boston’s built environment.

For ideas on keeping your business running at its best, be sure to browse our blog often.

The post Chris Rapczynski’s Employee-First Philosophy at Sleeping Dog Properties appeared first on BUSINESS OPPORTUNITIES.

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-2010, Peter Thoeny, Twiki, Inc.; 2005-2007, Michael Daum http://wikiring.de
License: GPL (GNU General Public License)
Plugin Version: v2.6 - 2010-05-16
Change History:  
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
TWiki:Plugins/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: TWikiPlugins, AdminDocumentationCategory, TWikiPreferences


This topic: TWiki > HeadlinesPlugin Topic revision: r1 - 2010-05-17 - TWikiContributor
 
This site is powered by the TWiki collaboration platformCopyright &© 1999-2025 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.