[Zope-CMF] Switching to Chameleon

2011-09-28 Thread Charlie Clark
Hi,

finally getting some development done for probably the first time this  
year. I've been able to switch all my CMF-based projects to Chameleon (via  
five.pt) and have not hit any problems. Should we do this for CMF 2.3?

Charlie
-- 
Charlie Clark
Managing Director
Clark Consulting  Research
German Office
Helmholtzstr. 20
Düsseldorf
D- 40215
Tel: +49-211-600-3657
Mobile: +49-178-782-6226
___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-CMF] [dev] working on the trunk

2011-09-28 Thread Charlie Clark
Am 27.01.2011, 17:05 Uhr, schrieb yuppie y.2...@wcm-solutions.de:

 zope.formlib is not made for DateTime values and encoded strings. So you
 *always* have to make sure these values are converted correctly. And it
 is hard to do that inside the form code. Obviously you did have trouble
 to get it right that way. After I started using adapters for the edited
 objects I had much less trouble using formlib. Of course you don't need
 an adapter if your objects already provide the right interface.

 And one more benefit: Inside the form code you can completely ignore the
 old-fashioned implementation of the edited objects and write nice modern
 code.

Finally have made the time to look at this. I've written a schema adapter  
for the forms and it looks like SettingsEditForm handles the conversion to  
Zope's DateTime nicely. Now, I'm stuck with the problem of getting my view  
unit tests to work. Looks like I need a few adapters registered. :-/

 In my defence I hope it's worth noting that we now
 have tests for a heap of stuff in CMFDefault which previously didn't  
 exist.

 Regarding SyndicationInfo - I'd appreciate any pointers on writing a
 migration step. Given the hopelessly outdated state of the current
 implementation I'm not convinced anyone will need to do the migration

 What was wrong with the old implementation? I never had trouble using
 the old configuration objects and forms. The old RSS template didn't
 work for me, but that's a different issue.

I think the old implementation was just wrong headed to use SimpleItem for  
this. But think I've worked out how to do the migration.

 but
 then, of course, one of the aims of CMFDefault is to provide exactly  
 this
 kind of example.
 I'm sure I'm not the only one who has existing CMF sites with
 SyndicationInformation objects in it. Making sure these sites can be
 upgraded without trouble is essential. And not a nice to have extra.
 Especially if the old implementation did work and the new one doesn't
 provide any new features.

I agree that a migration step is necessary and will put one in.

Charlie
-- 
Charlie Clark
Managing Director
Clark Consulting  Research
German Office
Helmholtzstr. 20
Düsseldorf
D- 40215
Tel: +49-211-600-3657
Mobile: +49-178-782-6226
___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


[Zope-CMF] cmf-tests - OK: 4

2011-09-28 Thread CMF tests summarizer
This is the summary for test reports received on the 
cmf-tests list between 2011-09-27 00:00:00 UTC and 2011-09-28 00:00:00 UTC:

See the footnotes for test reports of unsuccessful builds.

An up-to date view of the builders is also available in our 
buildbot documentation: 
http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds

Reports received


   CMF-2.2 Zope-2.12 Python-2.6.6 : Linux
   CMF-2.2 Zope-2.13 Python-2.6.6 : Linux
   CMF-trunk Zope-2.13 Python-2.6.6 : Linux
   CMF-trunk Zope-trunk Python-2.6.6 : Linux

Non-OK results
--

___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests