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

1. What Zope did wrong
(and what to do instead)
Lennart Regebro
EuroPython 2007, Vilnius

2. Zope is zuper!

3. First!

4. Object oriented!

5. Python!

6. Open source!

7. Batteries included!

8. Secure!

9. Easy!

10. And many other exclamation marks!!!

11. What Zope2 did right

12. Used Python

13. ZODB

14. DTML/ZPT

15. Batteries included

16. Easy entry into development

17. Zope2: The dead-ends

18. The ZODB pile of scripts

19. ZClasses

20. Disk-based products

21. Never ends
Starts o easy

23. It's unpythonic!

24. Products instead of modules

25. Way to much magick!

26. Zope is the Application
(not the library)‫‏‬

27. Maybe more?

28. Zope 3: Knight in shining armour!

30. Zope 3?

31. Zope 3!

32. To complicated

33. 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;
/

34. Phew...
Ugh..
.

35. Zope3: Death by abstraction

37. It's unpythonic!

38. XML

39. (So, not so unpythonic as people think)‫‏‬

40. In J2EE:
A mail service API
Implementation
neutral
Req: J2EE
Not web-only
The JavaMail API!

41. In Zope 3:
A mail service API
Implementation
neutral
Req: components
Not web-only
zope.app.mail

42. Zope 3: The long march

43. Development of Zope 2 slowed down

44. Documentation no longer updated

45. A general waiting for Godot

46. Backwards compatibility

47. Didn't happen

48. Forwards compatibility

49. Not Yet

50. Never ends
Starts o easy

51. Phew...
Ugh..
.

52. 2 + 3 = Five
Argh!
Ugh..
.

53. Low entry treshold
and
all the power of a big
framework
without
dead ends?

56. 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

57. 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
−

58. Too much freedom?

59. Start with a finished application!

60. How can we accomplish this?

61. Python

62. A setup framework

63. Zope Component Architecture

64. Zope 3 the libraries

65. Grok

66. Information Manager
GUI Tools
IT department
The CMS/ERP
Site developer
Application developer Grok
Component
Core developer
Architecture