Re: [Zope-CMF] Re: [z3-five] Re: CMFonFive and CMF 1.6
On 1/5/06, Rob Miller <[EMAIL PROTECTED]> wrote: > Lennart Regebro wrote: > > And CMF 1.6 already has more changes that just GenericSetup, some of > > which are already causing me other headaches. > > which are these? the most significant changes are in the TypesTool, and > this was done in order to achieve more parity btn the 1.6 and 2.0 site > creation code... there's nothing that i know of that's not directly > related to the GenericSetup stuff. Yeah, well that's it. And here I am trying to achieve more parity between 1.6 and 2.0. [ Well, now I'm only teasing you on accord of the wobbly argumentation. ;-) ] -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] Re: [z3-five] Re: CMFonFive and CMF 1.6
On 1/5/06, Rob Miller <[EMAIL PROTECTED]> wrote: > maybe i'm being dense, but i don't see how merging the code into the CMF > core improves this. if i'm understanding this correctly, you wouldn't > be increasing the number of supported combinations at all; No, I'd just get rid of a whole lot of potential version combinations, thereby lessening the support headache that this already is. Although I admittedly can handle that problem by completely ignoring it, which seems to be the preferred option here. And I just realized that Five 1.3 and Five in 1.2 differs much more than I thought too. Glaaah. :-P And CMF 1.6 already has more changes that just GenericSetup, some of which are already causing me other headaches. I guess my main problem is that everything else is currently changing so fast that I don't have time to keep up with the changes, and the more stuff I fix, the more stuff seems to remain to be fixed. CalZope 2.0 (which is needed for the CalPlone implementation) just looks further and further away. :-/ > anyway, it's moot, since you've agreed to keep it a separate product for > now. thank you. Yeah, but that doesn't mean I like it. :-) -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] Re: [z3-five] Re: CMFonFive and CMF 1.6
On 1/5/06, Jens Vagelpohl <[EMAIL PROTECTED]> wrote: > Sorry I didn't follow this discussion closely, so you want to merge > the last remnants of CMFonFive into CMF 1.6 and 2.0, is that the > suggestion? It's already merged into CMF 2.0 (although it's not actuall *working* yet. ;) ) So it's only 1.6 that is the question yet. The result would be that CMF 1.6 would only support one major version of Zope, which I guess would be 2.9, which doesn't seem to sit well with the Plone community. Anyway, I'll release a CMFonFive 1.3 today, which will work with Zope 2.9, and CMF 1.5.5, and should work with CMF 1.6 (although I haven't tried it yet). -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] Re: [z3-five] Re: CMFonFive and CMF 1.6
On 5 Jan 2006, at 09:40, Lennart Regebro wrote: this makes sense. i'm -1 on the final CMFonFive piece landing in CMF 1.6 itself, though. the original scope for CMF 1.6 was "CMF 1.5 + GenericSetup", i don't see a compelling reason to complicate things by expanding that scope. if CMFonFive stays separate, then you can code it to support only Zope 2.9 without having to impose this same restriction on the CMF core. Well, it doesn't make sense, because it continues a complex versioning dance, and leaves many combinations unsupported, but if nobody else wants that fixed, then I won't fix it. :-) And it doesn't really complicate things by expanding any scope, it just moves a bit of code from on product to another. Sorry I didn't follow this discussion closely, so you want to merge the last remnants of CMFonFive into CMF 1.6 and 2.0, is that the suggestion? jens ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] Re: [z3-five] Re: CMFonFive and CMF 1.6
> this makes sense. i'm -1 on the final CMFonFive piece landing in CMF > 1.6 itself, though. the original scope for CMF 1.6 was "CMF 1.5 + > GenericSetup", i don't see a compelling reason to complicate things by > expanding that scope. if CMFonFive stays separate, then you can code it > to support only Zope 2.9 without having to impose this same restriction > on the CMF core. Well, it doesn't make sense, because it continues a complex versioning dance, and leaves many combinations unsupported, but if nobody else wants that fixed, then I won't fix it. :-) And it doesn't really complicate things by expanding any scope, it just moves a bit of code from on product to another. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
