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:

Tue, 21 Jan 2025 06:24:38 +0000
The original blog about business opportunities and business ideas for small business entrepreneurs
Mon, 20 Jan 2025 23:32:02 +0000 Carrol Strain

The financial industry is evolving rapidly, and banks are under immense pressure to provide seamless, digital-first banking experiences. An important component of this variation is the core banking infrastructure. Traditionally, economic institutions have relied on core banking systems (CBS) to manage their operations. However, with the upward push of digital banking, core banking platforms (CBP) are rising as a more flexible and future-proof alternative.

This article explores the important variations between core banking systems and core banking platforms, highlighting why financial institutions should consider upgrading to a next-generation solution.

Core Banking Systems Explained

A core banking system is the centralized backend software program utilized by banks to control critical operations. In effect, these functions include account management, transactions, loans, and customer records. These structures have been the backbone of banking for decades, enabling institutions to offer constant services across branches as well as digital channels.

Many conventional core banking systems function on legacy infrastructure, which may be both inflexible and expensive. Moreover, while they have served banks quite well in the past, their obstacles in scalability and innovation no longer serve customers’ needs.

But core banking systems must now compete with core banking platforms. These innovative solutions provide agility and real-time processing, as well as seamless integration with new financial technologies.

Core Banking Platforms Defined

A core banking platform is a new technology. It is based on a modern-day, cloud-native, and API-driven alternative to standard core banking systems. What’s more, unlike legacy structures, these platforms provide flexibility, since they permit monetary establishments to conform quickly to market changes and client needs.

Basically, core banking platforms leverage superior technology. This is because they rely on artificial intelligence, blockchain, and real-time facts analytics to enhance banking operations. They are designed to guide digital-first banking practices. This therefore allows quicker product improvement and seamless integration with fintech solutions.

Key Features of Core Banking Platforms

  • Cloud-based total infrastructure for improved scalability and cost performance.
  • Open APIs to integrate with third-party applications and services.
  • Real-time transaction processing for better consumer experience.
  • Advanced safety features to defend sensitive banking information.
  • Modular architecture, allowing banks to personalize functions as needed.

RELATED ARTICLE: HOW DOES DIGITAL MEDIA AFFECT OUR LIVES?

A Comparative Analysis of the Two Approaches

Understanding the essential variations between traditional systems and core banking platforms is crucial for financial institutions planning to modernize their operations.

360w" sizes="auto, (max-width: 480px) 150px" src="https://www.business-opportunities.biz/wp-content/uploads/2025/01/Table-for-banking-article-2.jpg" alt="" class="uag-image-310673" width="900" height="388" title="Table for banking article 2" loading="lazy" role="img"/>

Why Financial Institutions Should Move to Core Banking Platforms

With developing digital competition and constantly shifting client expectations, banks must embrace next-generation solutions. Otherwise, they cannot remain competitive. Specifically, here are the key reasons why upgrading to a core banking platform is a smart move:

1. Enhanced Agility and Speed

A core banking platform allows financial establishments to release new services and products faster. Thus, they can keep up with evolving market trends and changing consumer needs.

2. Cost Savings and Efficiency

Cloud-based core banking platforms decrease the need for costly on-premises infrastructure. This leads to sizeable price savings in IT operations and preservation.

RELATED ARTICLE: ACCOUNTING SOFTWARE: STREAMLINING BUSINESS FINANCES

3. Seamless Digital Integration

With open APIs, banks can easily incorporate fintech solutions such as digital wallets and third-party applications, thus improving their service offerings and customer engagement.

4. Improved Customer Experience

Real-time transaction processing, customized banking reports, and improved safety features improve clients’ experience.

5. Future-Proofing the Business

By adopting a flexible, cloud-native platform, economic institutions can foresee enterprise disruptions. They can therefore future-proof their operations against technological advancements.

RELATED ARTICLE: HOW TECHNOLOGY IS CHANGING FINANCIAL OPERATIONS

Conclusion

The shift from core banking systems to core banking platforms is inevitable for financial establishments looking to increase their agility and innovation. This is because while conventional banking solutions have performed well overall, they have increasingly become a bottleneck due to rapid changes in the digital space.

However, by selecting an innovative platform, banks and other financial providers can streamline their operations, enhance user experiences, and remain aggressive in a rapidly evolving monetary landscape. Moreover, making the transition now will ensure long-lasting functionality in the digital age.

Featured image by F01 PHOTO

The post Core Banking Platforms: State-of-the-Art Operations appeared first on BUSINESS OPPORTUNITIES.

Thu, 16 Jan 2025 23:36:17 +0000 Carrol Strain

Jet engines are among the most remarkable inventions of modern engineering, powering everything from commercial airliners to military aircraft and spacecraft. At the heart of these powerful machines lies the turbine, a component that is essential for transforming energy into motion. Turbine design is a masterful blend of science, technology, and precision engineering. This article takes a deep dive into the intricacies of the design of this marvelous invention, exploring its components and operation, as well as the cutting-edge technologies driving its evolution.

The Role of the Turbine in a Jet Engine

The turbine is a key component of a jet engine, responsible for converting high-pressure, high-temperature gases from the combustor into mechanical energy. This energy drives the compressor and, in some cases, additional systems such as electrical generators or hydraulic pumps.

Jet engines are powered by the Brayton cycle, a thermodynamic process that involves compressing air, adding energy through combustion, and then expanding the hot gases through a turbine to produce thrust. The turbine's role in this cycle is to efficiently extract as much energy as possible from the exhaust gases while maintaining durability and reliability under extreme conditions.

Core Components of a Turbine

A typical turbine consists of the following key components:

  1. Rotor Blades: These are the rotating components of the turbine, designed to extract energy from the flow of hot gases. Their shape maximizes aerodynamic efficiency while withstanding immense centrifugal forces and high temperatures.
  2. Stator Blades (Nozzles): These are stationary blades that direct the flow of gases onto the rotor blades at the correct angle. They also play a critical role in maintaining the turbine's aerodynamic performance.
  3. Disk: The rotor blades are mounted onto a disk, which is connected to the shaft that transfers mechanical energy to other parts of the engine.
  4. Shaft: The shaft transmits the mechanical energy generated by the turbine to the compressor and other engine systems.
  5. Casing: This is basically a protective enclosure that supports the turbine's structure and prevents gas leakage.

Materials and Manufacturing

Turbines must operate in some of the harshest conditions known to engineering. Therefore, the materials used in turbine construction need to withstand high temperatures, mechanical stresses, and corrosive environments. Engineers commonly use nickel-based superalloys due to their ability to retain strength at extreme temperatures. These materials are often enhanced with coatings that improve resistance to oxidation and thermal fatigue.

Modern manufacturing techniques have revolutionized the production of this extraordinary device. Advanced methods such as precision casting, machining, and 3D printing enable the creation of intricate blade designs that optimize performance. The use of single-crystal blades, which eliminate grain boundaries and improve durability, represents a significant advancement in turbine technology.

RELATED ARTICLE: SHOULD YOU START A MANUFACTURING PARTNERSHIP?

The Science of Aerodynamics in Turbine Design

Aerodynamics plays a pivotal role in turbine design. The shape and arrangement of rotor and stator blades are meticulously engineered to maximize the extraction of energy from the gas flow while minimizing losses.

Key aerodynamic considerations include:

  • Blade Profiles: Blades are designed with airfoil shapes that balance lift and drag forces to achieve optimal performance.
  • Cooling Systems: To prevent overheating, many turbine blades incorporate internal cooling channels that allow air to circulate and dissipate heat.
  • Minimizing Turbulence: Smooth gas flow is critical for efficiency. Therefore, engineers rely on advanced computational fluid dynamics (CFD) tools to refine blade designs and reduce turbulence.

RELATED ARTICLE: TOP AIR TRAVEL HACKS FOR FREQUENT BUSINESS TRAVELERS

Efficiency and Performance Enhancements

Efficiency is a cornerstone of turbine design, as even minor improvements can lead to significant gains in fuel economy and thrust. Engineers focus on:

  • High-Pressure Ratios: Increasing the pressure ratio across the turbine improves the overall thermal efficiency of the engine.
  • Advanced Blade Coatings: Ceramic coatings can reflect heat and reduce thermal degradation, extending the lifespan of the components.
  • Variable Geometry Turbines: Some advanced engines use adjustable stator vanes to optimize performance across different operating conditions.

Challenges in Turbine Design

Despite decades of innovation, turbine design remains one of the most challenging aspects of jet engine development. Engineers must balance competing priorities such as efficiency, durability, weight, and cost. The need for constant reliability under extreme operating conditions leaves no room for error.

Additionally, environmental regulations are pushing for lower emissions and better fuel efficiency, requiring further advancements in the technology. Achieving these goals involves exploring new materials, manufacturing techniques, and aerodynamic designs.

RELATED ARTICLE: THE LOWDOWN ON CFD AND TURBINE DESIGN

Innovations Shaping the Future of Turbine Design

The future of turbine design lies in sustainable aviation. Engineers are developing:

  • Hybrid-Electric Systems: Integrating turbines with electric propulsion to reduce emissions and fuel consumption.
  • Hydrogen-Powered Engines: These turbines are designed to operate on hydrogen fuel, offering a zero-carbon alternative to traditional jet fuel.
  • Additive Manufacturing: 3D printing enables the creation of lightweight, high-performance components with complex geometries that were previously impossible to manufacture.

These innovations, coupled with trusted turbine parts and services, ensure that jet engines will continue to evolve to meet the demands of a changing world.

Conclusion

Breaking down the design of a jet engine turbine reveals a complex interplay of science, engineering, and technology. From the materials and manufacturing methods to the aerodynamic principles and performance enhancements, every aspect of the design of these devices is meticulously crafted to achieve maximum efficiency and reliability.

As aviation advances toward a more sustainable future, turbines will remain at the forefront of innovation. With their unparalleled ability to convert energy into motion, these engineering masterpieces continue to push the boundaries of what is possible in modern flight.

Featured image by Gorodenkoff

The post Breaking Down the Jet Engine: A Deep Dive into Turbine Design 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

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.