• Project Home

  last modified October 29, 2007 by reinout


Plone realestatebroker is an ancient (but still working) plone 2.0 product. It runs for instance on http://vanleeuwenmak.nl/, the site where Zest software originally developed it for. It is also used on some other sites worldwide.


Goal of the project: plone 3.0 product

Our current plans involve:

  • Plone 3 Support including migration [mostly done]
  • Move House state to actual workflow states (already on trunk, but needs migration) [DONE]
  • Dropping CMFPhotoAlbum as a dependency and use default Image instead [DONE]
  • Nicer Slideshow and allowing larger photo's to be uploaded - http://plone.org/products/slideshowfolder [DONE (though custom-made)]
  • Allow upload of multiple images using PloneFlashUpload - http://plone4artists.org/products/ploneflashupload/ [DONE]
  • Adding Geo information using Google Maps based on the address information - http://dev.plone.org/collective/browser/Maps [mostly DONE]

One of the requests was to create an UML model for this product to allow customisations. Unfortunately we dropped support for ArchGenXML and
prefer to write Zope 3 code instead, which gives programmers far more advantages.


Terms and Conditions

This openplans project coordinates the nice task of updating the product for plone 3.0. This means a complete re-write, though without changing the overall architecture. It must be a good, up-to-date, fresh plone 3.0 product. No, no plone 2.5. So:

  • Full unit test coverage. Read Rocky Burt's article about it. I want every single line to be tested.
  • No more install.py, we have generic setup now. [Well, we have an install.py back as that's safer, the actual work is done in genericsetup, though.]
  • Squeaky clean content types without display logic. Display logic is for browser views.
  • Templates and styles and images? Zope3 resources. Inside the browser/ dir.
  • lib/python, no Products/ .


Current status (2007-10-29)

A lot is finished. It runs on 3.0. Content type fields need work and the UI needs tighter integration. So: great improvements, the finished product will be great.


Main resources