Re: [Zope3-dev] Re: [Zope-dev] Two visions
Jim Fulton wrote: I think a lack of a realistic vision means that we are pulling in different directions. I think this is causing a lot of harm. I think the crux of the issue here is that presently, we do not have a consistent answer to the question What is `Zope'?. I think what Jim is attempting is to solve this problem. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope 3 web root
Shane Hathaway wrote: Zope is a feast with many kinds of food. When people come to the feast, most are not willing to try everything at once, particularly the entrees from the land of OODBMS. First let them have some familiar foods. When they find out how finely prepared the food is, they'll be ready to try the meaty main course. Although many will still prefer the RDBMS salads. Sometimes the ZODB (the OODBMS you speak of) isn't appropriate for the environment your app will live in. Many apps aren't stand-alone.. they need to integrate and share data with other systems. Most of those systems already know how to use an RDBMS, so the path of least resistance is to use one of those. I'm sure the ZODB is probably the best solution for most applications that are stand-alone, Zope only - but as soon as you need to start architecting a complex set of tools that all interoperate an RDBMS seems like a better idea. ... or perhaps I'm simply suffering from RDBMS brain-damage, after using them for so long. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Pluggins vs Application Definition
Jim Fulton wrote: In summary, I think we need *both* approaches, as they serve different needs. I'd have to agree... so +1 .. but I'd suggest that the application/plugin should have a way of defining which ways it can (or prefers, if it can't be enforced) to be included, so it is clear that Package-X is really a plugin for Product-Y, rather than a whole new stand-alone product. rob ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: [Zope3-Users] Selecting a code name
Stephan Richter wrote: Okay, I am giving in on this. There is a three step process that will have to be fullfilled to assign a codename to the Zope 3.3 release. Surely codenames are only really useful or meaningful for software that is going to be branded, but the marketing/branding teams haven't yet come up with the brand? You need some way to describe the project, so you use a codename until the real name and brand have been decided upon. We've already got Zope 3 .. I don't really see any need to start using codenames. Unless, of course, people just want to feel cool by saying I'm currently working on Glubberzortlet or whatever. rob ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Selecting a code name
Paul Winkler wrote: Mac OSX in itself, on the other hand, was brilliant. With one letter they managed to establish: [...] Right... but that is a brand, not a codename. As I understand it, people are discussing things like Tiger, and Panther, to follow your example. rob ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
