Wednesday, October 27, 2004
An early version of peak.web is now available, as I previously promised. At this point, it's more of a proof-of-concept than a working web framework, since it only includes features aimed at creating static sites and dynamic read-only sites (e.g. from databases). In other words, no authentication and no forms handling. For the moment, however, it's a very easy way to create pages to go with your objects. Searching or modifying objects, well, that's a bit harder.
I also now have a personal blog at dirtSimple.org, which will sometimes touch on PEAK-related topics. The blog, combined with the work I've been doing for my wife's lingerie and adult toy store (not safe for work!), has been taking up a lot of my time lately. (And no, the store's website isn't written in peak.web, it's using an open source PHP package -- why do you think I've been so motivated to get peak.web working? PHP the language isn't so much the issue, as it is that adding components to the site equals applying diffs to various segments of it. Ugh. peak.web will be much more modular; I guarantee it.)
Tuesday, July 6, 2004
The first release candidate for PyProtocols 0.9.3 is now available. This release mainly improves compatibility and API symmetry between PyProtocols and Zope, such as the ability to use IFoo(bar) as a shortcut for adapt(bar,IFoo), and the ability to use adapter factories that take only one argument.
I've tried to make it as backwards-compatible with 0.9.2 as possible, but depending on how deeply you've used certain obscure features, you may notice changes. So make sure that you read UPGRADING.txt and CHANGES.txt before you upgrade any production code to 0.9.3.
Wednesday, February 18, 2004
PEAK 0.5a3 is finally out. There's no unifying theme to this release, unless "it's been too long since the last release" counts. Lots of new frameworks and other cool features. But then, if you've actually been using PEAK, chances are good you've been following the CVS version and the mailing list, and so you've already been using all the new stuff for a while.
So, I'm not sure what else I should say here. I still don't want to excessively promote PEAK to people who aren't willing to do a little digging and experimenting, so I guess I should shut up now.
Friday, December 5, 2003
PyProtocols 0.9.2 is out; I goofed and missed adding a unit test for the new protocols.Variation class. As a result, it was unusably broken. Thanks to Radek Kanovsky for pointing this out. I guess this just shows what happens when you don't write the tests first.
Friday, November 28, 2003
PyProtocols 0.9.1 is out. Highlights include fixed bugs, compatibility with the latest versions of Python, Zope, and Twisted, and lots of new convenience features for automatically or semi-automatically creating protocols and adapters. See the full list of changes.
Also, I recently completed the pre-forking process manager I talked about in August. And in the process, I added a new mini-framework for managing signals and child processes. With luck, I hope to get the rest of the 0.5a3 features done before year-end.
Wednesday, October 15, 2003
There's now a developer wiki available at http://peak.telecommunity.com/DevCenter/. There are a few official documentation semi-drafts floating around there, plus some promising volunteer efforts and examples. Also, a mostly-complete set of IRC channel logs is available at http://peak.telecommunity.com/irc-logs/, but keep in mind that most days logged consist mostly of "so-and-so came, so-and-so left", and other days are missing. The Twisted-based logbot seems susceptible to being bumped offline and never coming back. I keep meaning to ask for help with it on the Twisted mailing list, but never quite getting around to it.
Work is in progress on developing a full-blown logical query language for PEAK. Actually, not so much a language as a Python API for creating query objects that can be either executed on objects directly (the way peak.model.queries does now) or translated to other query languages like SQL. The API's expressive power should be roughly equivalent to that of ConQuer, a conceptual query language that's a superset of SQL in functionality, and much easier to use. I'm currently posting design notes to the mailing list, and posting links to useful papers in the wiki.
Saturday, June 28, 2003
There's now an IRC channel for discussing PEAK: #peak on irc.freenode.net. I'm not there that often, but there seem to be a few regulars there whenever I do drop by.
The 0.5 alpha 2 release also came out this month, and I'm hard at work on alpha 3. Alpha 3 will include the beginnings of the peak.web framework, and the peak.security framework for rule-based access control is already in CVS.
Last, but far from least, I've started work on an example application, "Bulletins", which will demonstrate how to use data managers, configuration, peak.running, and indeed most of PEAK's major subsystems. It is basically a web-based announcement system, a sort of very primitive blog. But its main purpose is to be a "shakedown cruise" for PEAK 0.5, to find out what, if anything, is missing from the framework for building complete applications.
Thursday, May 1, 2003
PEAK version 0.5 alpha 1 is released! Read the release announcement, then go check out the downloads area.
Friday, April 18, 2003
It's such a wonderful time to be a Python programmer! You get to use all the best packages... Twisted, Zope X3, ZConfig, logging, csv... There's a whole new meaning these days to the "Batteries Included" slogan. Nowadays, if the batteries aren't enough for you, you can go download entire power plants...
Speaking of power, PEAK has been quietly amassing power in the last few months. Of particular note, the peak.model refactoring is pretty much complete, and we can now generate Python code from MOF metamodels for things like UML and CWM. There's also a cool new set of process management interfaces along with basic components implementating those interfaces.
We're getting pretty close to an 0.5 alpha 1 release, probably in early May. Targeted features for 0.5a1 include integration with (surprise!) Twisted, Zope X3, ZConfig, and the PEP 282 logging package.
Wednesday, January 1, 2003
At the moment PEAK addresses almost all my concerns as an application developer and I can really see that it will make maintaining applications orders of magnitude easier.
-- Roché Compaan
A recent thread on the mailing list covers Roché's first attempt to use the peak.storage package, and a variety of tips on using other parts of the system, particularly peak.naming and peak.config, to develop flexible and configurable applications. Above, Roché offers some feedback about PEAK's design.
|
|
![[Link opens in new window]](/web/20050409082546im_/http://peak.telecommunity.com/Images/LinkInNewWindow.gif){kind=small}