Paul's response to "Quills Notes"
Document Actions
Arthur has done some interesting detective work re discussiontool
i suspect the problem is that its not possible to change the text_format
of a discussion item to anything other than the text_format of its
container document
as noted here
------------------------------
security.declareProtected(ReplyToItem, 'cookReply')
def cookReply(self, reply, text_format=None):
""" TODO We need this because currently we can not easily change the
text_format on document objects. Discussions in plone are going
to use plain-text for now. stx is too confusing.
------------------------------
this would be because of the display machinery - a document can only
one type if say structured text - any html code would not be able
to be rendered correctly - or if its an html document structured text
would render incorrectly - to solve this problem they restrict the format
of discusson items to plain text
fixing this might require a major rewrite of the display machinery
of course i'm speculating here - because the code is quite complex and difficult
to follow so anything might be happening !!
Arthur says :
------------------------------
So my theory is that by fixing CMFPlone/DiscussionTool.py so that it
does not prevent this stuff working by means of cookReply, or whatever
makes plain text the only form of permitted comment, Quills (and the
rest of Plone) would allow what we need in comments.
------------------------------
testing this would appear to require a simple patch
i tried patching cookreply in
CMFPlone/DiscussionTool.py
so that cookreply just returns the original text without the cooking
but that change crashed my plone - will have to reinstall
maybe Wendy could have a go at that same patch
its quite a small modification - interested to know if your plone
crashes too !!!
(note to self - next time backup original first)
i'll have to investigate as to what's crashing my plone - just had a
thought, maybe it should have
been edited under linux and the dos cr/lf's in the saved file are is
causing problems - ive had that bug / problem before !
Arthur noted the following
------------------------------
In Plone/Instance/Products there are the following (when downloaded
and deployed):
Quills/syndication.py -
class WeblogEntryFeedSource(BaseFeed
"""An adapter from IWeblogEntry to IFeedSource that feeds out the
entry's comments.
"""
This implies that Quills will supply comments as an RSS feed.
------------------------------
this is zope3 code - zope3 makes extensive use of interfaces like IWeblogEntry
and IFeedsource (any object starting with I) - this enable you to
plug in components
to replace other components - its the key zope3 technology
Once plone is completely rewritten in Zope3 - that will allow great
flexibility and probaly
allow the problems with disscussion item to be easily solved.
I looked at qPloneComments that Arthur mentioned and the same authors
have produced:
------------------------------
qPloneBlog is improved blogging tool for Plone based on refactored
SimplBlog product, with the following extra features: tags,
trackbacks, bookmarklets, google adsense, blog aggregators pinging and
RSS2 support .
http://plone.org/products
------------------------------
also mentioned by Arthur - easycommenting
same author is in the processing of releasing easyblog
------------------------------
Features of EasyBlog
* Multiuser/Multiblogs
* Categories
* Monthly archives
* Trackbacks
Receiving
o allow/disallow (per blog/entry)
o show/hide (per blog/entry)
o moderate yes/no
o blacklist: always to be reviewed
Sending
o autodetection (per blog/entry)
o logfile
* Comments
o allow/disallow (per blog/entry)
o show/hide (per blog/entry)
o moderate yes/no
o preview yes/no
o HTML tags/attributes handling
o blacklist: always to be reviewed
------------------------------
he states
EasyBlog 2.0 (Unreleased)
Completely refactored using zope 3 technologies
more evidence that the push is on to move everythig to zope3
this is going to take awhile - but will be a major step forward for plone
--paul
