#9283: A more lightweight backend for collections ----------------------------+----------------------------------------------- Reporter: elvix | Owner: Type: PLIP | Status: new Priority: minor | Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | ----------------------------+-----------------------------------------------
Comment(by elvix): Replying to [comment:23 erikrose]: > * How much do products currently depend on Collections API that would change? How popular are custom criteria in the wild? These could hurt hands-free migration, so I like Calvin's idea of a manual, optional migration. I don't know about others but : We (Jarn) commonly add criteria registrations for new indexes. We almost never write custom criteria types. I think the latter is very uncommon. > * I'd encourage the implementors to work closely with Hanno on this to make sure any API changes change once: not now and then again in 5. It sounds like they already have this in mind. We share offices with Hanno, and would never do this without consulting him. > * Can we get a UI (''any'' UI) for reordering Subfolders along with this? I've had that request and personally done the crazy ZMI manual- bubble-sort workarounds for it. What is reordering subfolders and how does this relate to collections? Subfolders in collections? Shouldn't they use the same ui as other subfolders do? I don't think this PLIP will supply any such UI. -- Ticket URL: <http://dev.plone.org/plone/ticket/9283#comment:24> Plone <http://plone.org> Plone Content Management System
_______________________________________________ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories