[Framework-Team] Question on folderish types | Impact on visual diffing in versioned content

[Nathan Van Gheem]

anecdotal, but I vaguely remember testing diffs and versioning on a
folderish type branch months ago and it worked fine to my surprise.

It's pretty easy to change the base classes in plone.app.contenttypes and
try for yourself.

On Fri, Nov 14, 2014 at 2:36 AM, Johannes Raggam <raggam-nl at adm.at> wrote:

> @armin I don't know, but thanks for the pointer. We have to check
> this...
>
> On Fri, 2014-11-14 at 09:29 +0100, Armin Stroß-Radschinski wrote:
> > as far as I remember, I followed a discussion in the lunch waiting queue
> in Bristol (Frisi was involved), that mentioned that there is an issue with
> visual diffing data in versioned folderish types in the Plone UI. Time was
> too short to get all the details there. But is was because those
> (dexterity?) folderish types use different storage types for some
> information and therefore leads to lacking of the feature for these
> particular fields. Since this is hard to get for normal users, this may
> break existing approaches that rely on availability of this in standard
> types.
> >
> > If I am wrong (just relevant for Archetypes?) forget it. If not make
> sure it is in the decisions points and ends up properly in the docs for
> the (optional or not) migration. I know there are different opinions if the
> feature is necessary. But I have no doubt it is, so make sure we do not end
> up again with strange UX.
> >
> > -- Armin
> >
> > Am 13.11.2014 um 17:49 schrieb Philip Bauer <bauer at starzel.de>:
> >
> > > Hi framework-team,
> > >
> > > Do you want p.a.c to provide only folderish types by default (in Plone
> 5) provided I write a nice upgrade-step that transforms all existing types
> into folderish types?
> > >
> > > A feature that adds support for folderish types and a migration-form
> landed in p.a.c. For now they are still optional but we are still in alpha
> so we could still change this. By default the types would not allow any
> types to be added to them (<property name="allowed_content_types"/>) so
> from a usability-perspective nothing changes for normal users.
> > >
> > > This is only about Collection, Event, Document and News Item.
> > >
> > > Deliverables:
> > > - upgrade-step in plone.app.upgrades
> > > - some documentation
> > > - make sure the appropriate types appear in default_page_types (they
> are now empty when creating a new page).
> > > - only show plone-contentmenu-add-to-default-page if the type actually
> has allowed types (meaning it would not show up by default). This requires
> a change in plone.app.contentmenu.
> > > - show the types in default_page_types (this is now filtered using
> brain.is_folderish, it should instead check if you can add types to the
> portal_type of the brain). This requires a change in plone.app.content.
> > > - tests
> > >
> > > Cheers,
> > > Philip
> >
> > --
> > Armin Carl Stroß-Radschinski | developer at acsr.de | Twitter: @syncmitter
> > Dipl. Designer FH | project-consultant | fon +49 171 21 94699 | IRC:
> acsr | Skype: astrossradschinski
> >
> > ACSR industrialdesign | Armin Stroß-Radschinski
> > Landgrafenstraße 32 · 53842 Troisdorf · Germany | UST. ID Nr:
> DE154092803 (EU VAT ID)
> > info at acsr.de | www.acsr.de | phone +49 2241 946994 · fax +49 2241 946996
> >
> > _______________________________________________
> > Framework-Team mailing list
> > Framework-Team at lists.plone.org
> > https://lists.plone.org/mailman/listinfo/plone-framework-team
>
> --
> programmatic  web development
> di(fh) johannes raggam / thet
> python plone zope development
> plone framework  team  member
> mail: office at programmatic.pro
> web:  http://programmatic.pro
>       http://bluedynamics.com
>
>
> _______________________________________________
> Framework-Team mailing list
> Framework-Team at lists.plone.org
> https://lists.plone.org/mailman/listinfo/plone-framework-team
>
>


-- 
Nathan Van Gheem
Solutions Architect
Wildcard Corp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plone.org/pipermail/plone-framework-team/attachments/20141114/4ea53e1f/attachment-0001.html>