Installation

Automated Tests

Webware includes a suite of automated tests to make sure everything is working on your platform. To run the tests, go to the Webware root folder and run python AllTests.py . The first time you run the tests, it creates a file AllTests.config. This file has configuration options required for some tests to run, such as database connections. If you don't adjust this file, then any tests that need a database are skipped. The file includes comments that describe each option. You should find it easy to understand.

If some of the tests fail on your system, please enter it on the Bug Tracker link of the Webware home page. Also, if you find a bug that doesn't show up in the automated tests, it will be much easier for us to fix if you can submit a test case with your bug report.

Components

Each Webware component has a focused purpose and can often be used on its own. At the same time, the components are designed to work together where appropriate. You can use as much or as little of Webware as you want to.

The core component is WebKit, which is the Webware application server.

Status

Webware is a pretty mature and stable software that has been used in production for a long time by a variety of people in different environments. With support from the webware-discuss mailing list, you should feel comfortable developing with Webware.

In the Component Index you will see the status of each component such as alpha and beta. For beta components we are successfully striving for backwards compatibility of the API as the components mature.

Design Points

Webware is pro-Python. These software components are not about Java, C++ or any other programming languages.

The various software components are meant to be accessible in a stand alone fashion except in those cases where one component builds on another. That doesn't preclude the idea that the components can provide hooks for integration or even automatically integrate other components when their presence is detected.

A clean, object-oriented style of development is used as much as possible.

However, Webware components don't provide a special class for each type of HTML tag. It's generally easier and more efficient to use strings like '<br><hr>' than to say something like 'BreakLine() + HorizontalRule()'.

Documentation is meant to be of the highest caliber so that users can more quickly get up and running with Webware.

All components are accompanied by examples (that also serve as tests).

Over time, regression tests are created and expanded upon for each component.

Although Webware includes more than one independent component, it's not intended to be a hodge-podge repository of any kind of web component written in Python. New components should fit into the 'feel' of what's there already and provide integration with other components wherever possible. The emphasis is on high-quality, object-oriented components (with the mild exception of the utility collections, MiscUtils and WebUtils).

Future

Webware for Python has been created in the year 2000 (even before Python 2.0 was released) and stood the test of time. However, this also brings some problems. A lot of things could be realized in simpler ways today, using new Python features and other recent developments such as setuptools. Some Python standards such as WSGI or PEP8 did not exist when Webware has been designed, and thus things have been implemented in Webware's own ways, some of which may look quirky today. Also, many other great web frameworks for Python and components for such frameworks (e.g. templating systems, object-relational mapping) have emerged in recent years.

There are ideas to radically modernize, streamline and refactor Webware for Python after version 1.0, heeding and utilizing all currently available Python standards and components, maybe even requiring Python 3.0. Ian Bicking has already made an experiment in this direction with Wareweb. However, such a radical rewrite is a lot of work and does not seem to be possible without breaking backward compatibility and removing non-essential Webware components to a great extend. The question is whether this effort is justifiable in view of the plethora of already existing modern Python web frameworks.

So probably the next Webware for Python versions will see only gradual adaptations to newer Python versions and clean-ups. The current stable Webware for Python version 1.0 will still support the old Python versions and will continue to be maintained with bug fix releases in the foreseeable future.