| | |
|---|
| | | |
|---|
| | | Implementations of these features were *required* to allow the :app:`Pyramid` |
|---|
| | | authors to build the bread-and-butter CMS-type systems for customers in the |
|---|
| | | way they were accustomed to building them. No other system save Zope itself |
|---|
| | | way they were accustomed to building them. No other system, save for Zope itself, |
|---|
| | | had such features. And Zope itself was beginning to show signs of its age. |
|---|
| | | We were becoming hampered by consequences of its early design mistakes. |
|---|
| | | Zope's lack of documentation was also difficult to work around: it was hard |
|---|
| | |
|---|
| | | particular, :term:`URL dispatch` is a more direct mechanism to map URLs to |
|---|
| | | code. |
|---|
| | | |
|---|
| | | So although we couldn't find a framework save for Zope that fit our needs, |
|---|
| | | So, although we couldn't find a framework, save for Zope, that fit our needs, |
|---|
| | | and while we incorporated a lot of Zope ideas into BFG, we also emulated the |
|---|
| | | features we found compelling in other frameworks (such as :term:`url |
|---|
| | | dispatch`). After the initial public release of BFG, as time went on, |
|---|
