[BlueBream] Starting Point, names, caching and security

Christopher Warner cwarner at kernelcode.com
Thu Sep 27 15:37:27 UTC 2012

Your incessant, detailed nagging is productive only in surfacing problems
and not solving them. Unfortunately that is not conducive to moving
anything forward and only promotes angst and animosity.

What would be much more productive and may actually garner the help you
need is to point out the issues and ask if anyone was interested in helping
to fix it, or working with you in finding a solution. Right now, you make
that proposition very difficult.

There are problems, there are limited lack of resources and we need
positive, insightful and useful attitudes in helping to get things done.
That and much less whining, nagging and woe is me in the form of a question
for help.

On Sun, Sep 16, 2012 at 12:14 PM, Christopher Lozinski <
lozinski at freerecruiting.com> wrote:

> So if you want to use Bluebream, how do you start? They have not updated
> the downloand in two years, and more recently it disappeared off the
> bluebream website.
> On Feb 13th 2012, there was an announcement of a new release of ztk, on
> the zope-dev mailing list, with completely cryptic instructions on how to
> install it.
> https://mail.zope.org/pipermail/zope-dev/2012-February/044114.html
> Fine if you are an expert on buildout.
> So I went over to find the instruction on the buildout.org website and
> look what I found.
> http://pypi.python.org/pypi/zc.zope3recipes#id1
> From Feb 7th of 2012, by Jim Fulton,  a release of zope 3.
> It is a nice tar.gz file for installation.  I presume that the two
> announcements, being so close together, are basically the same thing.
> Now just last week we saw the following post.
> On 9/10/12 7:00 AM, Alex Clark wrote
>  Well, let's get the terminology straight. "Zope 3" is entirely dead.
> Its remnants have been divided up into (more or less) the ZTK and
> Bluebream. ZTK is a set of reusable libraries (more or less) and
> Bluebream is the application server.
>  So different people, are saying different things.  It is indeed
> confusing.
> The other way you can get started is by using ztfy.org or wiki.ztfy.org
> That is more in the content management world.  And thierry provides great
> support.
> I hope that helps other people going down this very difficult path.
> To speed things up you may want to have an egg cache.
> From
> http://jacobian.org/writing/more-buildout-notes/
> You’ll basically add a couple of lines to your buildout.cfg:
> [buildout]
> eggs-directory = /home/you/.buildout/eggs
> download-cache = /home/you/.buildout/dlcache
> You can also put these same lines in a ~/.buildout/default.cfg; Buildout
> picks up user-level settings from that file.
> I also took a look at the zope.app.security directories.  Everything was
> there that i expected to see, permissions, principals, principaldirectory,
> and some other stuff I did not quite understand.  Of course most of those
> files linked to some other files somewhere else.  That is okay.  But I
> certainly did not see much documentation.  High level class descriptions,
> data type definitions, and message flow diagrams seem to be sorely
> missing.  Fortunately we are all trained in software archeology.
> I wonder if any of the Zope books describe this stuff well.  I have the
> general idea that Twisted serves the web, then it traverses the zodb, and
> dispatches to a particular python class.  I now have to figure out exactly
> where it does that, and how permissions are defined on interfaces, and how
> to make permissions be defined on individual methods instead.   That way I
> can hide ZCA from initial BlueBream development.
> Regards
> Chris
> _______________________________________________
> bluebream mailing list
> bluebream at zope.org
> https://mail.zope.org/mailman/listinfo/bluebream

Christopher Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.zope.org/pipermail/bluebream/attachments/20120927/8ed7eaa7/attachment.html>

More information about the bluebream mailing list