Stefane Fermigier wrote:
Zed/The Component Architecture Formerlyknown as Zope/GoldEgg/whatever
that's not called Zope something: YUCK!
(Who's Zed? Zed's dead, baby!)
+ sys.maxint
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
___
Jeff Shell wrote:
Yes it does. And I hate it. At Bottlerocket, we're a very small
company. We look at Plone and go "alright, how do we make it do less?
how do we turn this thing off, and this thing off, and this thing off,
and this thing off? why is it so slow? and it still doesn't do the
page w
On Mar 2, 2006, at 6:41 AM, Peter Bengtsson wrote:
I'm with Max on this one.
What's the point? To save a few megabytes of harddisk space?
If you don't want the zope.bobo part of your zope3, ignore it. You
don't have to use it if you don't want to.
...
Let's keep it simple, bundle it all in one
Marko Mikulicic wrote:
On 02.03.2006., at 12:41, Peter Bengtsson wrote:
I'm with Max on this one.
What's the point? To save a few megabytes of harddisk space?
If you don't want the zope.bobo part of your zope3, ignore it. You
don't have to use it if you don't want to.
not sure of what to t
Stefane Fermigier a écrit :
Paul Winkler wrote:
On Thu, Mar 02, 2006 at 10:23:17AM +0100, Max M wrote:
Canonical releases of compatible package collections is a *must*.
Splitting it all up in small chunks that are out of sync would be a
disaster.
but we already have that situation wi
On 3/2/06, Max M <[EMAIL PROTECTED]> wrote:
> Jeff Shell wrote:
>
> >I think this keeps Zope 3 as we know it alive, keeps the Zope brand
> >intact, and offers a future for Zope 2 and similar caliber desires for
> >a Big App Server while not interfering with the more "pure" and simple
> >concepts th
Paul Winkler wrote:
> On Thu, Mar 02, 2006 at 10:23:17AM +0100, Max M wrote:
>
>> Canonical releases of compatible package collections is a *must*.
>> Splitting it all up in small chunks that are out of sync would be a
>> disaster.
>>
>
> but we already have that situation with current Pr
On Thu, Mar 02, 2006 at 10:23:17AM +0100, Max M wrote:
> Canonical releases of compatible package collections is a *must*.
> Splitting it all up in small chunks that are out of sync would be a
> disaster.
but we already have that situation with current Products.
How many sites are still running
Jeff Shell wrote:
> - Zope 3 CA: The Zope Component Architecture. Core services. Would
> include zope.publisher and most other current top level zope.* things.
> Usable as a library, as a publisher for other environments, perhaps as a
> simple standalone server. Easy to deploy against WSGI, P
On 02.03.2006., at 12:41, Peter Bengtsson wrote:
I'm with Max on this one.
What's the point? To save a few megabytes of harddisk space?
If you don't want the zope.bobo part of your zope3, ignore it. You
don't have to use it if you don't want to.
not sure of what to think about this vision bu
I'm with Max on this one.
What's the point? To save a few megabytes of harddisk space?
If you don't want the zope.bobo part of your zope3, ignore it. You
don't have to use it if you don't want to.
It's been a while but the last time I installed Plone it came with
stuff like CookieCrumbler and For
Jeff Shell wrote:
I think this keeps Zope 3 as we know it alive, keeps the Zope brand
intact, and offers a future for Zope 2 and similar caliber desires for
a Big App Server while not interfering with the more "pure" and simple
concepts that makes Zope 3 appealing for developers like me.
I
I think packaging efforts are really the key to being able to tell a
story like this. The efforts happen to be couched in a process of
converting z3 packages into eggs, but really the process of
identifying dependencies and eliminating the silly ones is the
valuable work here, and it seems
On Mar 1, 2006, at 7:42 PM, Jeff Shell wrote:
[...]
- Zope 3 CA: The Zope Component Architecture. Core services. Would
include zope.publisher and most other current top level zope.*
things.
Usable as a library, as a publisher for other environments,
perhaps as a
simple standalone ser
We've been through a lot lately. You know it, I know it. Zope has a
reputation. Sometimes it's good, sometimes it's bad. This has affected
Zope 3, since Zope 3 is very much "not Zope 2". But it's affecting
Zope 2 as well, as Jim has brought to our attention. Zope 3 is Mature.
Zope 3 sounds like Zop
15 matches
Mail list logo
