I haven’t made any Quills checkins for the past couple of days, so I thought I’d explain the current status of my main development branch (<a href=”http://dev.plone.org/collective/browser/Quills/branches/maurits-traversal/”>maurits-traversal</a>).<br /><br />As I <a href=”http://quills.sitefusion.co.uk/blog/archive/2007/06/02/ipublishtraverse-and-a-plone-3-dependency”>mentioned before</a>, there is now a hard dependency on Plone 3. After chatting to Derek Richardson about his work on <a href=”http://dev.plone.org/collective/browser/Vice”>Vice</a>, this seems even more inevitable as that is likely to have a Plone 3 dependency as well. (Vice is the new, improved, outbound syndication code that will replace base/fatsyndication as soon as it’s ready.)<br /><br />So, onto the current specifics of the maurits-traversal branch. WeblogArchive has been removed and posts are now stored directly within the Weblog object. This means that the “evil” workflow that would cut-and-paste weblog entries into a hierarchy of archive folders is now gone too. Yay! The previous folder hierarchy of the form “[weblog]/archive/2007/06/13/entry_id” is now `faked’ with an IPublishTraverse adapter.<br /><br />Not only is the banishment of “evil” inherently good, but removal of the custom workflow makes it possible to be more Plone-ish in the operation of a Quills blog. The use of standard Plone author/editor roles should now be possible as weblog entries don’t need to be (implicitly) deleted during the publish step. So, the WeblogAuthorRole should now be superfluous.<br /><br />The main thing stopping me from merging this branch to the trunk is a security issue that means it is necessary to declare __allow_access_to_unprotected_subobjects__ = True on the (non-persistent) topic and archive classes. This is obviously a bad thing as it competely circumvents security. For some reason, security and/or the acquisition chain seems to get a bit screwy when the new plone.portlets code gets invoked. At first, I thought this was something to do with my traversal of non-persistent, non-standard-plone, objects, but Martin Aspeli recognised my traceback as something he’s trying to chase down in a different context (pardon the pun). Hopefully, he can figure out what’s going wrong as I’ve been all through things in a pdb session, and am still none-the-wise.<br /><br />The other notable change on the branch is that QuillsTool has now been removed. In its place is a view that has all the same methods, plus some extra ones factored out from over-complicated skin templates. I’m not completely convinced that the view is the right place for all these methods, though, so a utility may grow back at some point.<br /><br />The upshot of all this is that the maurits-traversal branch should be in a state for people to check out and give a test run to (as long as you understand it is pre-alpha). Migrations are not there (yet), so you’ll have to use a fresh instance. Unit tests almost certainly don’t pass, either. They probably need quite a lot of work after the major surgery that has happened…<br /><br /><br />That’s it for now.<br />
Tim Hicks: Status update
Originally from Planet Plone by Tim Hicks
http://plonewars.com/2007/07/24/tim-hicks-status-update/