[PEAK] Where to start?

[Victor Ng]

For what it's worth - a lot of the ideas in PEAK started to clear up 
for me after I read "Patterns of Enterprise Application Architecture" 
by Martin Fowler.  At least now I can understand what the role of the 
DataManager and domain models are supposed to be within the context of 
an application.

Taking a peak (no pun intended) at the bulletins example application 
should also help out.  There's still nothing like working code to give 
you an idea of how stuff works - even if some bits of code in there 
aren't necessarily the best way of doing things.

vic

On 27-Nov-03, at 9:53 AM, Phillip J. Eby wrote:

> At 01:39 AM 11/27/03 -0600, rand at speakeasy.net wrote:
>> I am a fairly experienced python programmer, however the
>> PEAK package seems fairly daunting to understand.
>
> PEAK is a little easier to grasp if you realize that it's actually two 
> things:
>
> 1. A "framework for frameworks", known as the PEAK core framework
> 2. A collection of task-area frameworks built on the core
>
> So, to use PEAK, you need to be able to understand the core concepts, 
> and then you can make use any of the non-core frameworks.