Package: bluebream
Table of ContentsBlueBreamIntroductionFeaturesInstallationUsageResourcesChangelog1.0 (2011-01-18)1.0b4 (2010-08-26)1.0b3 (2010-07-11)1.0b2 (2010-06-30)1.0b1 (2010-04-27)1.0a5 (2010-03-28)1.0a4 (2010-03-07)1.0a3 (2010-03-07)1.0a2 (2010-03-02)1.0a1 (2010-02-06)0.1.9 (2010-01-13)0.1.8 (2010-01-12)0.1.7 (2010-01-10)0.1.6 (2010-01-07)0.1.5 (2010-01-07)0.1.4 (2010-01-04)0.1.3 (2010-01-04)0.1.2 (2010-01-03)0.1.1 (2010-01-02)0.1.0 (2010-01-02)DownloadBlueBreamIntroductionBlueBream– formerly known asZope
3– is a web framework written in the Python programming language.BlueBream is free/open source software, owned by theZope Foundation, licensed under theZope Public
License(BSD
like, GPL compatible license).FeaturesHere are the features distinguishing BlueBream from other Python web frameworks:BlueBream is built on top of theZope Toolkit(ZTK), which has many years of
experience proving it meets the demanding requirements for stable,
scalable software.BlueBream uses the powerful and familiarBuildoutbuilding system written in
Python.BlueBream employs the Zope Object DatabaseZODB, a transactional
object database, providing extremely powerful and easy to use
persistence.BlueBream registers components with Zope Component Markup Language
(ZCML), an XML
based configuration language, providing limitless flexibility.BlueBream features theZope Component Architecture(ZCA) which implementsSeparation of concernsto create highly cohesive reusable
components (zope.component).BlueBream implements theWSGIspecification (Web Server Gateway Interface) with the help ofPasteDeploy.BlueBream includes a number of well tested components to implement
common activities.  A few of these are:zope.publisherpublishes Python objects on the web, emphasizingWSGIcompatibilityzope.securityprovides a generic mechanism for pluggable
security policieszope.testingandzope.testbrowseroffer unit and functional testing
frameworkszope.pagetemplateis an XHTML-compliant language for developing
templateszope.schemais a schema engine to describe your data modelszope.formlibis a tool for automatically generating forms from your schemasInstallationIf you have installedsetuptoolsordistributeaneasy_installcommand will be available.  Then, you can install BlueBream usingeasy_installcommand like this:$ easy_install bluebreamInternet access toPyPIis required
to perform installation of BlueBream.Thebluebreamdistribution provides a quick project
creation tool based on PasteScript templates.  Once BlueBream is installed,
runpastercommand to create the project directory structure.
Thecreatesub-command provided by paster will show a wizard to
create the project directory structure.$ paster create -t bluebreamThis will bring a wizard asking details about your new project.  If you provide
a package name and version number, you will get a working application which can
be modified further.  The project name will be used as the egg name. You can
also change the values provided later.The project name can be given as a command line argument:$ paster create -t bluebream sampleprojectYou can provide a dotted name so that the package be created in a namespace,
with any number of levels, such as “sample.main” or “sample.app.main”. It will
result in a nested structure allowing you to split large projects into several
packages.If you provide an option from the command line, it will not be
prompted by the wizard. The other variables are given below, you can
give the values from the command line, if required:interpreter– Name of the custom Python interpreterbluebream– The version of BlueBreamversion– The version of your project (eg:- 0.1)description– One-line description of the packagelong_description– Multi-line description (in reStructuredText)keywords– Space-separated keywords/tagsauthor– Author nameauthor_email– Author emailurl– URL of the homepagelicense_name– License nameIf you are in a hurry, you can simply pressEnter/Returnkey and
change the values later.  But it would be a good idea, if you provide
a good name for your project.UsageThe generated package is bundled with Buildout configuration and the
Buildout bootstrap script (bootstrap.py).  First you need to
bootstrap the buildout itself:$ cd sampleproject
$ python bootstrap.pyThe bootstrap script will install thezc.buildoutanddistributepackages.  Also, it will create the basic directory structure.  Next step is
building the application.  To build the application, run the buildout:$ ./bin/buidoutThe buildout script will download all dependencies and setup the
environment to run your application.The most common thing you need while developing an application is
running the server.  BlueBream use thepastercommand provided by
PasteScript to run the WSGI server.  To run the server, you can pass
the PasteDeploy configuration file as the argument toservesub-command as given here:$ ./bin/paster serve debug.iniOnce you run the server, you can access it here:http://localhost:8080/.  The port number (8080) can be changed
from the PasteDeploy configuration file (debug.ini).The second most common thing must be running the test cases.
BlueBream creates a testrunner using thezc.recipe.testrunnerBuildout recipe.  You can see atestcommand inside thebindirectory.  To run test cases, just run this command:$ ./bin/testSometimes you may want to get the debug shell.  BlueBream provides a
Python prompt with your application object.  You can invoke the debug
shell like this:$ ./bin/paster shell debug.iniMore about the test runner and debug shell will be explained in the
BlueBream Manual.  You can continue reading about BlueBream from thedocumentation site.ResourcesWebsite with documentationProject blogThe bugs and issues are tracked atlaunchpad.BlueBream WikiPyPI HomeTwitterMailing listIRC Channel:#bluebream at irc.freenode.netBuildbotThe source code is managed atZope reposistory.  You can perform a read-only
checkout of trunk code like this (Anonymous access):svn co svn://svn.zope.org/repos/main/bluebream/trunk bluebreamYou can alsobecome a source code contributor (committer) after signing a
contributor agreementYou can seemore details about contributing in wiki.Changelog1.0 (2011-01-18)Includezope.location,zope.keyreference,zope.intidandzope.contentprovider,zope.i18nfromsite.zcmlfile.Reorganized zcml files (for deploy, debug and testing)updated to ZTK 1.0.11.0b4 (2010-08-26)Change custom interpreter name: s/breampy/bbpyFixed the generated buildout and make it repeatableAdded the “extends-cache” Buildout option to cache
the extended configuration fileswarn the user if the project template has significant changesAdded empty overrides.zcml - show best practices to developersupdated to ZTK 1.0a3Automatically find and suggest the latestminorversion onlineadded zope.app.http registrations to get the correct unauthorized view1.0b3 (2010-07-11)Directly depend on the ZTK!Removed the bbkit packageAsk the version of BlueBream at project creationAutomatically find and suggest the latest version online1.0b2 (2010-06-30)Include zope.error & zope.principalregistry from site.zcml1.0b1 (2010-04-27)Setname&descriptionfor the sample applicationUse project name as i18n_domain in base templateMerge the two templates into a single one by allowing to create a
flat or nested namespace structure, and choose the package name.Enabled Distribute by default instead of SetuptoolsAdded zope.app.schema registrations to be able to register a named vocabularyremoved buildout templating and include two zope.conf files,
one for deployment and one for debugging with devmode1.0a5 (2010-03-28)Include the sample application in thebluebream_simpletemplateMove the sample application provided bybluebreamtemplate
to a sub-package namedwelcomesimilar tobluebream_simpleThe sample application can be easily removed.The sample application object use ‘zope.site.interfaces.IFolder`
instead ofzope.container.interfaces.IContainerIncludezope.sessionfromsite.zcmlIncludebrowsernamespace insite.zcmlfor convenience.Added an empty[versions]part inversions.cfgwith
a recommendation to pin-down versions of other dependencies.Removezope.app.twistedfrom dependency listSince BlueBream requires ZODB 3.9, FileStorage need not be
wrapped with BlobStorage proxy to get ZODB blobs support.The default ZODB blob layout should be ‘bushy’
Fix LP #543525Use relative paths in etc/zope.conf Fix LP #543451Specify i18n domain in ftesting.zcml Fix LP #543516zope.browserresource package registration was missing
Fix LP #5414571.0a4 (2010-03-07)Added an empty PKG-INFO
Work around fix for “empty directory” problem.
(refer: LP #503301)1.0a3 (2010-03-07)The summary ofbluebream_basetemplate changed to:
“A BlueBream project, base template”Enablebluebream_simpleagain.  Documentation is
available here:http://wiki.zope.org/bluebream/AlternateProjectTemplates1.0a2 (2010-03-02)Use a template to display default page for the root
folderUsezope.formlib.form.DisplayFormas base class for
views instead ofzope.publisher.browser.BrowserViewSample application add form view name is changed from@@addto@@add_sample_appAdd links to to BlueBream website & mailing listAdded license fileImprove “Usage” section in README.txtIncludezest.releaseto prepare releaseIncludebluebream_simpletemplate (This will not be released
with 1.0a2 as the documentation is not ready yet)Movebluebreamtemplate code tobluebream_baseAdd static resource directory with CSS tobluebream_base(based onbluebream_simple).  The new style applied to main page.1.0a1 (2010-02-06)Use released package distribution versions:http://download.zope.org/bluebream/bluebream-1.0a1.cfgInclude new packages tosite.zcmltemplate:zope.app.publisher.xmlrpc(meta.zcml)zope.copypastemovezope.app.pagetemplateChanged template summary into: A BlueBream projectRemovedSphinx-PyPI-upload– no more used as the
website is moved tohttp://bluebream.zope.orgAddedzope.traversing.browserfrom site.zcml
in the project template. Ref:http://bit.ly/80xltO0.1.9 (2010-01-13)LP #506879: debug shell added. Basic usage:./bin/paster shell debug.ini0.1.8 (2010-01-12)UsezopeZCML namespace as default in configure.zcmlDocumentation improvementsCreate a sample application by default0.1.7 (2010-01-10)Update version: zope.tales = 3.5.0LP #505362: Fix. Main package name is hard-coded as ‘main’Change ‘defaultView’ registration location and interfaceLP #505413: Name of default custom Python interpreter
should be able to customize0.1.6 (2010-01-07)LP #502819: Main page after a fresh installationRemovedhelloview from template.LP #502941: Add trove classifiers.Mention all resources in PyPI page.0.1.5 (2010-01-07)LP #503388: Value of “namespace_package” should not be
empty string.Updated description, added promotional video.0.1.4 (2010-01-04)LP #503301: Work around fix for “empty directory” problem.Change author as “BlueBream” team and email to zope-dev list.0.1.3 (2010-01-04)LP #502817: var directory and its subdirectories not existDocumentation improvements: added “Usage” section0.1.2 (2010-01-03)Added functional testing support for projectSphinx based documentation infrastruture improvementsLP #502529: Update wizard to ask all package meta to
be updated in setup.py0.1.1 (2010-01-02)Fix missing package data. The 0.1.0 releases was broken.Improve documentation.0.1.0 (2010-01-02)Initial release.Download