The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
efge
- "CMFSetup: provide non-ascii im- and exports",
[Accepted] http://www.zope.org/Collectors/CMF/292
jens
- "Discussion replies removal",
thanks for starting up this conversation Rocky!
I think these assertions are more or less deadon. The next step is
charting a path for transition. for CMF, zope3 / five provides
lighterweight analogs of AT features. What is currently lacking is a
mapping layer to allow AT users to use the z
sorry for the cross post, but I know there are a number of other
reference engines out there and I would like to get input as we look
at moving the AT ref engine being a component.
here is a rough list of steps:
1) move current storage of references to use IAnnotations for new
content / refere
whit wrote:
> sorry for the cross post, but I know there are a number of other
> reference engines out there and I would like to get input as we look
> at moving the AT ref engine being a component.
>
> here is a rough list of steps:
>
> 1) move current storage of references to use IAnnotations f
Rocky Burt wrote:
> 1) Ease of development - AT helps cut down on boilerplate code
> as compared to building a regular CMF type (without AT)
>
> 2) Schema - The ability to declare which fields a content type has
> and what "types" those fields are
>
> 3) Widgets - The ability to d
On Mon, 09 Jan 2006 14:29:06 -, Rocky Burt
<[EMAIL PROTECTED]> wrote:
Hi all,
Sorry about the cross post, but I thought this topic concerned CMF,
Plone, and Archetypes equally.
I had a discussion with Alec Mitchell recently where we talked about the
components that made up Archetypes and
