• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Lennart Regebro   What Zope Did Wrong (And What To Do Instead)
 

Lennart Regebro What Zope Did Wrong (And What To Do Instead)

on

  • 4,257 views

An overview about the problems with Zope2 and Zope3 and how to fix them.

An overview about the problems with Zope2 and Zope3 and how to fix them.

Statistics

Views

Total Views
4,257
Views on SlideShare
4,256
Embed Views
1

Actions

Likes
0
Downloads
62
Comments
0

1 Embed 1

http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Lennart Regebro   What Zope Did Wrong (And What To Do Instead) Lennart Regebro What Zope Did Wrong (And What To Do Instead) Presentation Transcript

    • What Zope did wrong (and what to do instead) Lennart Regebro EuroPython 2007, Vilnius
    • Zope is zuper!
    • First!
    • Object oriented!
    • Python!
    • Open source!
    • Batteries included!
    • Secure!
    • Easy!
    • And many other exclamation marks!!!
    • What Zope2 did right
    • Used Python
    • ZODB
    • DTML/ZPT
    • Batteries included
    • Easy entry into development
    • Zope2: The dead-ends
    • The ZODB pile of scripts
    • ZClasses
    • Disk-based products
    • Never ends Starts o easy
    • It's unpythonic!
    • Products instead of modules
    • Way to much magick!
    • Zope is the Application (not the library)‫‏‬
    • Maybe more?
    • Zope 3: Knight in shining armour!
    • Zope 3?
    • Zope 3!
    • To complicated
    • <configure xmlns=quot;http://namespaces.zope.org/zopequot; xmlns:browser=quot;http://namespaces.zope.org/browserquot; xmlns:hello=quot;http://namespaces.zope.org/helloquot;> <content class=quot;.hello.Helloquot;> <require permission=quot;zope.Publicquot; interface=quot;.interfaces.IHelloquot; set_schema=quot;.interfaces.IHelloquot; /> </content> <browser:defaultView for=quot;.interfaces.IHelloquot; name=quot;edit.htmlquot; /> <browser:addMenuItem class=quot;.hello.Helloquot; title=quot;Add Helloquot; permission=quot;zope.Publicquot; for=quot;*quot; />
    • Phew... Ugh.. .
    • Zope3: Death by abstraction
    • It's unpythonic!
    • XML
    • (So, not so unpythonic as people think)‫‏‬
    • In J2EE: A mail service API Implementation neutral Req: J2EE Not web-only The JavaMail API!
    • In Zope 3: A mail service API Implementation neutral Req: components Not web-only zope.app.mail
    • Zope 3: The long march
    • Development of Zope 2 slowed down
    • Documentation no longer updated
    • A general waiting for Godot
    • Backwards compatibility
    • Didn't happen
    • Forwards compatibility
    • Not Yet
    • Never ends Starts o easy
    • Phew... Ugh.. .
    • 2 + 3 = Five Argh! Ugh.. .
    • Low entry treshold and all the power of a big framework without dead ends?
    • GUI schema/form editor Information Manager TTW Layer GUI workflow editor IT department A CMS, ERP or similar Site Layer Site developer A Web application server Application Layer Application developer Application Layer API Language Component Architecture Core Layer Core developer Loads of components
    • Pythonic Use existing modules and APIs if possible − The whole application framework is a library − Highly modular Pick and choose from the modules − Modify and replace internal components −
    • Too much freedom?
    • Start with a finished application!
    • How can we accomplish this?
    • Python
    • A setup framework
    • Zope Component Architecture
    • Zope 3 the libraries
    • Grok
    • Information Manager GUI Tools IT department The CMS/ERP Site developer Application developer Grok Component Core developer Architecture