[Zope] Plone ?

[Ausum Studio]

I really would've liked to avoid to say a word regarding this question, but
it's kind of true that newcomers do get confused in-between names. How to be
crystal clear about what implementations are (and do) when it's true
that -for example-  they can rely on others implementations' classes and
methods, the same as they do on Core's?

For people already familiar to Zope idiosyncracies, the more they stick to
mother Python, the less they get confused, but that's not the case of new
people coming to Zope's beaches from different worlds.

Jonas, Plone is written arround one concept about what portals should be.
It's suitable for a large number of uses, and it's up to you to evaluate how
much it fits your current needs. If you find it doesn't, or if you in
general need to do a site that behaves and looks completely different,
according to your own portal concept, then you need the CMF, which happens
to be the portal framework on top of which Plone is built.


Ausum


----- Original Message -----
From: "Jonas Nielsen" <jonasn@diku.dk>
To: <zope@zope.org>
Sent: Monday, October 28, 2002 8:23 AM
Subject: [Zope] Plone ?


> I have recently discovered the product called Plone. Isn't this "just"
> an improvement on the CMF ? When could it be good idea not to use
> plone if you want to use CMF ?
>
> _______________________________________________
> Zope maillist  -  Zope@zope.org
> http://lists.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope-dev )
>