TransWarp Release 0.2 preview 1 |
PEAK Release 0.5 alpha 1 |
|
|
Copyright (C) 2001,2002 by Phillip J. Eby, All rights reserved. |
Copyright (C) 1996-2003 by Phillip J. Eby and Tyler C. Sarna. |
This software may be used under the same terms as Zope or Python. |
All rights reserved. This software may be used under the same terms |
THERE IS ABSOLUTELY NO WARRANTY. Code quality varies from "alpha" |
as Zope or Python. THERE ARE ABSOLUTELY NO WARRANTIES OF ANY KIND. |
to "experimental pre-alpha". :) |
Code quality varies between modules, from "beta" to "experimental |
|
pre-alpha". :) |
|
|
|
|
Package Description |
Package Description |
|
|
TransWarp is a toolkit for software automation in Python, where the term |
PEAK is the "Python Enterprise Application Kit". If you develop |
"software automation" is considered to include CASE, code templating, |
"enterprise" applications with Python, or indeed almost any sort of |
metaprogramming, generative programming, subject- and aspect-oriented |
application with Python, PEAK may help you do it faster, easier, on a |
programming, etc. It is also a collection of frameworks which use the |
larger scale, and with fewer defects than ever before. The key is |
toolkit for integration with applications and other frameworks. |
component-based development, on a reliable infrastructure. |
|
|
|
PEAK is an application kit, and applications are made from components. |
|
PEAK provides you with a component architecture, component infrastructure, |
|
and various general-purpose components and component frameworks for |
|
building applications. As with J2EE, the idea is to let you stop |
|
reinventing architectural and infrastructure wheels, so you can put more |
|
time into your actual application. |
|
|
|
But PEAK is different from J2EE: it's a single, free implementation of |
|
simpler API's based on an easier-to-use language that can nonetheless |
|
scale with better performance than J2EE. |
|
|
|
PEAK is the successor to TransWarp, an experimental toolkit for software |
|
automation in Python. PEAK takes the best of the techniques and ideas |
|
from TransWarp, and repackages them as an enterprise software toolkit. |
|
Where TransWarp emphasized techniques like generative programming and |
|
aspect-oriented programming, PEAK emphasizes enterprise applications, |
|
and hides the computer science stuff "under the hood", so you can focus |
|
on building your application. |
|
|
|
PEAK tools can be used with other "Python Enterprise" frameworks such as |
|
Zope and the Python DBAPI to construct web-based, GUI, or command-line |
|
applications, interacting with any kind of storage, or with no storage |
|
at all. Whatever the application type, PEAK can help you put it together. |
|
|
|
|
|
Third-Party Software Included with PEAK |
|
|
|
The 'kjbuckets' module is Copyright Aaron Watters and contributors; |
|
please see the 'src/kjbuckets/COPYRIGHT.txt' file for details of its |
|
license. |
|
|
|
The 'Interface' and 'Persistence' packages are Copyright Zope Corporation |
|
and contributors; please see the 'LICENSE.txt' files for details of their |
|
licenses. |
|
|
As Zope is to web publishing, as Twisted Python is to internet protocols, |
|
and as AnyGUI is to graphical user interfaces, so TransWarp is (or wants |
|
to be) to the guts of your application, whatever its external interface. |
|
|
|
The high-level vision of TransWarp is "Metadata + Metaclasses = Programs". |
Installation Instructions |
|
|
|
|
Changes Since Last Release |
|
|
|
Darn near everything. :) Read the new docs and tutorials. |
|
|
|
|
Please see the INSTALL.txt file. |
|
|
Installation Instructions |
|
|
|
See the INSTALL.txt file. |
|