Free portlet software for linux

PloneiCalendar allows you to share and browse calendar files in Plone, and manage them in your calendar application.
PloneiCalendar is a product designed by Ingeniweb to handle calendar files in Plone. It is based on the iCalendar file format.
Once an PloneiCalendar is created in Plone, you can share it with other users or groups (you can give read or write permissions), browse it by day, week and month or modify it by using standard calendar applications like Mozilla Calendar or Apple iCal (or Ximian Evolution or KOrganizer or whatever you want - may be even Microsoft Outlook ;) ).
Main features:
- Upload and download your calendars in Plone
- Give permissions to users or groups to view/modify your calendars
- Browse your calendars by day, week or month
- Instantly find all your calendars with the included portlet
- View the event details
- All-day events and most recurring events are supported
- Handling of simultaneous events, even in complex cases (see screenshot)
- Handling of i18n date formats (currently, english and french formats can be displayed)
- Cool looknfeel : color integration with your plone site, personalization of the color of your calendars, 100% pure CSS in the calendar views (no table used)

Pluto is the Reference Implementation of the Java Portlet Specfication. The current version of this specification is JSR 168.
Portlets are designed to run in the context of a portal. They are written to the Portlet API which are similar to the Servlet API.
In contrast to servlets, portlets may not do things like sending redirects or errors to browsers directly, forwarding requests or writing arbitrary markup to the output stream to assure that they don?t distract the portal web application which uses them.
Another difference compared to servlets is that portlets rely on portal specific infrastructure functions such as access to user profile information, standard interface for storing/retrieving persistent settings, getting client information, etc. Generally,
portlets are administrated more dynamically than servlets typically are.
A portlet container provides a runtime environment for portlets implemented according to the Portlet API. In this environment portlets can be instantiated, used and finally destroyed. The portlet container is not a stand-alone container like the servlet container; instead it is implemented as a thin layer on top of the servlet container and reuses the functionality provided by the servlet container.
Pluto serves as portlet container that implements the Portlet API and offers developers a working example platform from which they can test their portlets. However, its cumbersome to execute and test the portlet container without a driver, in this case, the portal.
Plutos simple portal component is built only on the portlet containers and the JSR 168s requirements. (In contrast, the more sophisticated, Jetspeed project concentrates on the portal itself rather than the portlet container, and considers requirements from other groups.)
Enhancements:
- Added Pluto 1.1 index page and basic documentation
- PLUTO 164: response contentType can change after getWriter()
- PLUTO 155: URL encoding in pluto 1.0.1-RC4 issue when using apache with jk2
- PLUTO 157: portlet.tld taglib is using jsp version 1.1. JSR168 spec requires JSP version 1.2
- PLUTO 152: Support maven deployment to a remote repository
- PLUTO 130: portlet:namespace fails inside JSTL c:set
- PLUTO-107: Admin portlet fails to add page. Hot deployment now supported.
- PLUTO-92: Deployer strips elements from web.xml (Deploy War Portlet)

PloneSearchBox project is a portlet integrating different search engines.
PloneSearchBox is a compoment for Plone. It allows users to access quickly to a search tool. The Search can be done on the entire site, the current section of the site, or directly in search engine like google.
A tool is installed on the root site : portal_searchbox. Through the ZMI it allows to change what are the search engines proposed. In the textarea enter a search engine per line. This must be formated like folowed :
engine_name;engine_url?search=%(text)s
Dont forget the semi colon. %(text)s is the pattern that will be replaced by the ressearched text. If there are several pattern, text will be the label of the input box in the generated form.
If what is between the parantheses is different of text, it will be taken as label for the input field.
In the search_tool engines list, add commented line with #.
Enhancements:
- Make Installation work with Plone 2.1
- Zope Security added in portal_searchbox
- When engine list is empty, the list is really deleted.

Weather Forecast for Plone provides a product that will display weather information.
Weather Forecast for Plone is a small product that let your Plone site shows the weather forecast using the weather.com wether service retrieval.
Plone Weather Forecast contains:
- one portlet that will be (by default) placed at the end of the right column.
- one configlet that will easily let you enters all the configuration information Weather Forecast needs to run.
Weather Forecast for Plone has been design with a cache system: the weather service will not be asked on every request on your site.
Weather Forecast for Plone is translated in english, french, spannish, italian and dutch. You can participate to this project by sending a translation of your tongue.
Enhancements:
- Fix index handling when values are changed via ZMI

External Site Catalog allows you to index and search external sites in a Plone site.

ExternalSiteCatalog is a web crawler that can index external sites and make them searchable in Plone.

You can specify the sites to index in a Plone Configlet, and directly index them from Plone, or let a scheduler do the job.

Searching the external sites is done in a special portlet that is installed with ExternalSiteCatalog.

External sites are not searchable in the normal Plone catalog, but are only available in a separate catalog in the portal_externalcatalog tool.

ExternalSiteCatalog allows you to index and search external sites in a Plone site.

ExternalSiteCatalog is a web crawler that can index external sites and make them searchable in Plone. You can specify the sites to index in a Plone Configlet, and directly index them from Plone, or let a scheduler do the job. Have a look at some of the screenshot in the doc folder of the product to get a first impression of what it looks like. Searching the external sites is done in a special portlet that is installed with ExternalSiteCatalog. External sites are not searchable in the normal Plone catalog, but are only available in a separate catalog in the portal_externalcatalog tool.

Direct indexing

All external sites are configured in the ExternalSiteCatalog configlet.
If you want to index external sites immediately, you can do so after
defining all the parameters, selecting your site, and clicking on
the "index" button in the configlet.

Crawling external sites regularly

If you want external sites to be crawled regularly every day or month,
youll have to do some extra work. Make sure to install PloneMaintenance
starting from version 1.3. Make sure that you are also regularly calling
PloneMaintenance from cron or one of the Zope schedulers.

Follow the installation instructions in PloneMaintenance!

Have a look at the portal_maintenance tool in the Zope Management
interface! It contains a lot of useful information!

Console indexing utility

The console indexing utility is a bit more complicated than doing everything
from Plone. In many cases you dont have the resources to administrate an
external utility, but if you can afford it, this tool gives you the possibility
to decouple the long running work of fetching external sites from Zope.
Basically, you can be sure that there is no Zope thread blocked with
crawling external sites for a long time. Zope is only called from the external
tool when it should index a page, so there is still some load on the
Zope server!

Please note that this external tool is not making use of the information
entered in the Plone configlet. It is completely independent! It also does
not make use of PloneMaintenance, and it is up to you to configure and
call it with a scheduler like cron.

h3270 is a program that allows you to use IBM 3270 hosts from within a web browser.
h3270 is different from other, similar systems because of its highly configurable layout engine that is based on regular expressions.
Classical mainframe applications are still part of the IT infrastructure of most large enterprises. The challenge is often to integrate them with more recent, browser-based systems. h3270 allows you to do that in two steps:
- It renders 3270 host screens in HTML and makes them operable from within a web browser. This process works out of the box in a simple, character-based layout that resembles the original terminal screen. Optionally, the layout can be enhanced using a configurable engine so that it looks and feels like a real web application.
- The HTML adapter is available both as a servlet and a portlet, so that it can be used either as a stand-alone web application, or inside a portal server, which allows for seamless integration with other applications at the user interface level.
h3270 is a server-side Java application that is compliant with the J2EE standard and the Portlet API (JSR-168). To access the 3270 data stream, it uses the s3270 program written by Paul Mattes, which in turn relies on the TN3270 format to access the host via Telnet (TCP/IP).
Enhancements:
- h3270 version 1.3.3 improves the keyboard handling again. The change in the previous release, where we attached keyboard handlers to individual input fields, has shown not to be sufficient for many people. You could no longer input anything on screens with no input fields.
- In version 1.3.3, keyboard handlers are again global, on a per-page basis. To support multiple sessions within the same browser (or on the same portal page), keyboard handlers are now installed dynamically. When the mouse moves into a terminal window, a global, page-scoped keyboard handler is installed for that window. You can also force installation of a keyboard handler by clicking somewhere within the terminal window.
- We hope this method proves practical for everybody, please let us know if not. Another change in this release is improved error reporting in case of unknown (mis-spelled) or unreachable hosts.