[Zope-CMF] Re: Some first steps with CMF2
David Pratt
fairwinds at eastlink.ca
Tue Feb 28 20:11:39 EST 2006
Hi Jens. I should have spoken up sooner I guess but I feel this idea has
merit. Well it's the Five bridge that is needed here since this is a
Zope3 package at this point. I am in the process of trying to become a
bit better acquaited with ZCML but I may need some help to get this to work.
Regards,
David
Jens Vagelpohl wrote:
> I'm afraid integrating a separate product at the last minute is not in
> the cards. We're in beta, and that means feature freeze. One way of
> achieving what you want, if missing code is indeed the problem, would
> be to write a addon Zope product which provides the missing pieces.
> That can be done independent of the CMF roadmap, which you can find here:
>
> http://www.zope.org/Products/CMF/docs/roadmap/view
>
> jens
>
>
> On 28 Feb 2006, at 22:38, David Pratt wrote:
>
>> Hi Yuppie. Is there some interest in having CPSSkins V3 work together
>> with CMF in the new release? The CMF on its own is still very nice
>> framework but it would be nice if it was usable with a new skin.
>> CPSSkins V3 is ZPL. The old default templates are really not pretty
>> but CPSSkins could give CMF on its own a new life don't you think?
>> What it is missing is a Five bridge. Is this something that we could
>> make happen. I am willing to help (but my ZCML knowledge is not
>> particularly great at this stage). I am not sure when the final CMF
>> 2.0.0 but it would be a real milestone if we could give CMF a new
>> exterior for it's debut as 2.0.
>>
>> Regards,
>> David
>>
>> David Pratt wrote:
>>
>>> Hi Yuppie. Many thanks for this help. Yikes with the profiles. Not
>>> sure which way I will go. I'll wait for Rocky on 2.9 pythonproducts
>>> which will hopefull be shortly. I was hoping the Z3ECM CPSSkins
>>> could be used with CMF Default so that views could be integrated
>>> into something good and new. CPSSkins is ZPL. I guess formlib will
>>> be a bit so I should not be so anxious. It all takes time. :-)
>>> Regards,
>>> David
>>> yuppie wrote:
>>>
>>>> Hi David!
>>>>
>>>>
>>>> David Pratt wrote:
>>>>
>>>>> My first question has to do with GenericSetup. I have portals that
>>>>> require the adding of a variety of tools etc. So first off
>>>>> how/where do I create my site configuration so that I can create
>>>>> clones with my own configuration instead of default?
>>>>
>>>>
>>>>
>>>>
>>>> In general it should be easier to customize a site and create the
>>>> profile by exporting the site configuration compared to customizing
>>>> the XML files directly.
>>>>
>>>> A tarball import function is still missing, so the easiest way to
>>>> use your own profiles is creating a small product that registers
>>>> your profile.
>>>>
>>>> There are two possible strategies for creating your profiles:
>>>>
>>>> 1.) Create your own base profile(s)
>>>>
>>>> pro: This is an automated process because exports are always base
>>>> profiles.
>>>>
>>>> con: You create a lot of redundant configuration data that will
>>>> become hard to maintain if the default profiles are changed or you
>>>> need many similar configurations.
>>>>
>>>> 2.) Create your own extension profile(s)
>>>>
>>>> pro: It just represents the difference to the base profile and
>>>> other extension profiles. Keeping track of changes in those
>>>> profiles is an automated process.
>>>>
>>>> con: While a diff helps you to identify changes between two
>>>> profiles creating an extension profile is manual work.
>>>>
>>>>> Second, does CMF now support products as a package instead? If so
>>>>> where are the packages to be located for CMF and is there some
>>>>> sort of code somewhere that would exemplify an approach for moving
>>>>> my own products forward.
>>>>
>>>>
>>>>
>>>>
>>>> It is not officially supported but it might work with the latest
>>>> Five / pythonproducts code. I haven't tried it so far.
>>>>
>>>>> I see that five views are now available for default types. This is
>>>>> very exciting. How would one deal with the main portal template?
>>>>
>>>>
>>>>
>>>>
>>>> The main_template is one of the oldest parts of the CMFDefault
>>>> skin. I guess it needs a major refactoring if we port it to five
>>>> views. For now you customize it the old way or make your own
>>>> experiments.
>>>>
>>>>> Last question has to do with formlib. Does this integration exist
>>>>> in CMF2 currently?
>>>>
>>>>
>>>>
>>>>
>>>> CMF doesn't integrate Zope 3 features faster than Five. CMF 2.0
>>>> just requires Zope 2.9 (Five 1.3) which has no formlib support.
>>>> Maybe CMF 2.1 will use formlib and maybe you can already do useful
>>>> things with the latest Five code and formlib in CMF 2.0.
>>>>
>>>>> Sorry for so many questions but I am really pumped about the
>>>>> changes and I am anxious to begin moving things over.
>>>>
>>>>
>>>>
>>>>
>>>> You are welcome!
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Yuppie
>>>>
>>> _______________________________________________
>>> Zope-CMF maillist - Zope-CMF at lists.zope.org
>>> http://mail.zope.org/mailman/listinfo/zope-cmf
>>> See http://collector.zope.org/CMF for bug reports and feature requests
>>
>> _______________________________________________
>> Zope-CMF maillist - Zope-CMF at lists.zope.org
>> http://mail.zope.org/mailman/listinfo/zope-cmf
>>
>> See http://collector.zope.org/CMF for bug reports and feature requests
>
>
> _______________________________________________
> Zope-CMF maillist - Zope-CMF at lists.zope.org
> http://mail.zope.org/mailman/listinfo/zope-cmf
>
> See http://collector.zope.org/CMF for bug reports and feature requests
>
More information about the Zope-CMF
mailing list