Free plonenewsletter 2.0 software for linux

PloneNewsLetter provides a product for sending newsletters based on new Plone content to an email address in TXT or HTML format.
PloneNewsLetter gives you the possibility to create your custom newsletters. The newsletter is prepared for being sent using your favourite mass mailer, and can be directly published on your site.
The process of creating your PloneNewsLetter:
- You create a new PloneNewsLetter
- Using PloneNewsLetter, you search your Plone site for content
- You select the documents that you want to make it into the newsletter
- You can click on the "create" button, and an html and text version of the newsletter are created.
- The html and text versions can now be edited and viewed quickly in a preview window.
- Once you are satisfied with the result, you can send the newsletter to your email address.
- You can use your favourite mass mailer to distribute the newsletter Features:
- The templates used for production of the newsletter are fully customizable.
- The selection of objects for the newsletter is remembered, so you dont have to reselect everything just because you changed the templates.
- If the user publishes the newsletters content, all users will see the HTML version of the newsletter. That way the the newsletter is automatically archived online.
- PloneNewsLetter consists of two object:
- A content type, for users
- A Portal Tool, for settings

FONTpage is a Python font viewing and image-generating utility. It displays system fonts and allows you to change the font size and color, background color, font face, bold, and italics.
It also has the ability to input the text to be displayed, which you can choose to save as a PNG file. It is handy to view fonts and styles quickly, or to make "logo" graphics.
It was written to supersede wxFontView, as the pyGTK toolkit is much lighter and more widely used.
Enhancements:
- New "Display Font" feature opens popup window with complete alphabet (upper and lower case) and 0-9.
- Window shows current font with current size -- use multiple windows to compare different fonts.
- Font size now scales up to 256 pts (was 128)
- Config file will now track last window dimensions when the application is restarted.
- If user font directory directory (~/.fonts) does not exist, FONTpage will create one. This is to facilitate installing and deleting fonts, which FONTpage will only do on a per-user basis. (This is to avoid problems.)

pBeans project is a Object/Relational (O/R) database mapping layer. It is designed to be simple to use and automated.
The idea is that you save time and effort by simply focusing on writing Java classes, and not worrying about maintenance of matching SQL scripts, schema evolution, XML based schemas, or generating code. The pBeans framework takes care of persisting JavaBeans with little assistance from the developer.
Main features:
- Automatic Table Creation and Schema Evolution- Tables corresponding to JavaBean classes are created on demand. Field types are based, by default, on JavaBean compile-time types. Field type changes and new fields are detected. Manually changing tables (user-managed mode) is also supported.
- Based on Annotated JavaBeans- You define a getter and setter for each bean property. Persisent bean classes only need to be tagged with a @PersistentClass annotation.
- Transitive Persistence- If object A is persisted and it refers to Persistent object B, then object B is automatically persisted. If Persistent object C also refers to B, and C is also persisted, the record for object B in the database is not duplicated.
- Instance Consistency- If you retrieve an object from persistent storage that is already known to exist in main memory, you get a reference to the object in main memory. (Garbage collection is allowed to happen via weak references.)
- Near-Zero Configuration- There is no need to define schemas or anything of the sort in a language other than Java, and there are no code generation steps of any kind. No XML or SQL need to be written, except the necessary to create a database and grant user permissions. However, you can instruct pBeans to let you manage database modifications manually.
- Database features- Transactions and auto-increment IDs (MySQL only) are now supported.
- Flexibility- Via annotations users are allowed to define their own table and field names, the name of the primary key, whether fields are nullable, whether tables are user-managed (not automatically modified), table indexes, unique or otherwise, whether unused fields should be deleted, whether a field is nullable, whether it is renamed from another field (to prevent loss of data when a property is renamed), etc.
- Servlet support- A pBeans store may be easily configured using servlet context parameters (see ServletAccess.)

Landell project is a Voip GUI write in C#, based in Tapioca-Voip framework, compatible with Gtalk.
Main features:
- Voip connections;
- Multiples accounts login;
- Buddy group support;
- Plugins support;
- Style chat compatible with Adium;
- Notification icon;
- Banshee interaction for show on user status the current playing song;
- Autoaway message and time configuration;
- Buddy Avatar support;

PostGIS adds support for geographic objects to the PostgreSQL object-relational database. In effect, PostGIS "spatially enables" the PostgreSQL server, allowing it to be used as a backend spatial database for geographic information systems (GIS), much like ESRIs SDE or Oracles Spatial extension.

PostGIS follows the OpenGIS "Simple Features Specification for SQL" and will be submitted for conformance testing at version 1.0.

PostGIS has been developed by Refractions Research Inc as a research project in open source spatial database technology. PostGIS is released under the GNU General Public License. Our list of future projects includes enhanced technology for data loading and dumping, user interface tools for direct data access and manipulation, and support for advanced topologies at the server side, such as coverages, networks, and surfaces.

There are now several open source tools which work with PostGIS. The uDig project is working on a full read amd write desktop environment that can work with PostGIS directly.

For internet mapping, the University of Minnesota Mapserver can use PostGIS as a data source. The GeoTools Java GIS toolkit has PostGIS support, as does the GeoServer Web Feature Server.

GRASS now supports PostGIS as a data source, through the PostGRASS driver. The JUMP Java desktop GIS viewer has a simple plugin for reading PostGIS data, and the QGIS desktop has good PostGIS support.

PostGIS data can be exported to several output GIS formats using the OGR C++ library and commandline tools (and of cource with the bundled Shape file dumper). And of course any language which can work with PostgreSQL can work with PostGIS -- the list includes Perl, PHP, Python, TCL, C, C++, Java, and more.

Installation:

Un-tar the PostGIS tar-ball in the contrib directory of your PostgreSQL source tree. You must untar the PostGIS source there or the Makefile will not work. You must have the PL/pgSQL prodedural language installed before installing PostGIS.

cd contrib
gunzip postgis-0.9.0.tar.gz
tar xvf postgis-0.9.0.tar
cd postgis-0.9.0
make
make install
createlang plpgsql yourtestdatabase
psql -d yourtestdatabase -f postgis.sql
psql -d yourtestdatabase -f spatial_ref_sys.sql

IVJLogger project is a small library of classes and functions written in Java designed to assist you with your logging needs. "Why another logger?" you may ask. Well, the main purpose of it is keeping it simple.
Simplicity means less bugs, more extensibility, better performance, and happier users. Many loggers Ive seen out therer take forever to set up, I am not even talking about all the initialization code, and all the clean-up you have to do just to get them to log one line of code.
With IVJLogger you dont need any external files, no clean-up, and initialization code is as simple as instantiating an object.
Main features:
- Simplicity
- High performance - thanks to very efficient thread pool
- Less coding - one line to initialize, one line to log, no clean-up
- No external objects used - include the source with your project and youre ready to go
- Most recent JVM friendly - created and tested on Java 1.4.2 SE
- Cross-platform - well, Java kind of took care of that :)
- Thread-safe - multiple threads may use the same logger to log data simultaneously.

XMLBeans project is a technology for accessing XML by binding it to Java types. XMLBeans provides several ways to get at the XML, including:
- Through XML schema that has been compiled to generate Java types that represent schema types. In this way, you can access instances of the schema through JavaBeans-style accessors after the fashion of "getFoo" and "setFoo".
- The XMLBeans API also allows you to reflect into the XML schema itself through an XML Schema Object model.
- A cursor model through which you can traverse the full XML infoset.
- Support for XML DOM.
Start off with your own stuff:
If you want to get right to it with your own XML schema and instance, follow these basic steps:
Install XMLBeans.
Compile your schema. Use scomp to compile the schema, generating and jarring Java types. For example, to create a employeeschema.jar from an employeesschema.xsd file:
scomp -out employeeschema.jar employeeschema.xsd
Write code. With the generated JAR on your classpath, write code to bind an XML instance to the Java types representing your schema. Heres an example that would use types generated from an employees schema:
File xmlFile = new File("c:employees.xml");
// Bind the instance to the generated XMLBeans types.
EmployeesDocument empDoc =
EmployeesDocument.Factory.parse(xmlFile);
// Get and print pieces of the XML instance.
Employees emps = empDoc.getEmployees();
Employee[] empArray = emps.getEmployeeArray();
for (int i = 0; i < empArray.length; i++)
{
System.out.println(empArray[i]);
}
Enhancements:
- Updated to the latest XMLSchema.xsd - January 25, 2006
- Updated XmlBeans to work with SaxonB-8.6.1 in place of SaxonB8.1
- XQuery external variable binding support