From: Alexander Limi <limi@pl...> - 2003-06-21 04:51:22
We should really look into this thing, as it produces reSTX and/or STX docs
for APIs, and also has changable Page Templates, so we can make it match
the layout on plone.org in a good way.
Any of the more more hardcore Python people here want to take a look?
Alexander Limi ¤ Co-Founder·Plone
http://limi.net ¤ http://plone.org
Interface Design ¤ Usability Analysis
高联合 · アレクサンダー リミ · 이미짱
From: Simon Michael <simon@jo...> - 2003-07-15 13:51:22
Alexander Limi <limi@...> writes:
> We should really look into this thing, as it produces reSTX and/or STX
> docs for APIs, and also has changable Page Templates, so we can make it
> match the layout on plone.org in a good way.
Cool, thanks for this link.
I installed this on zwiki.org. It doesn't work in INSTANCE_HOME/Products.
I made a symbolic link in SOFTWARE_HOME/lib/python/Products for now.
Created a Zpydoc in the root folder. Created a ZopeRenderer, then created
a ZpyDocumentable for SOFTWARE_HOME/lib/python/Products
(INSTANCE_HOME/Products wasn't an option). This was empty, so I went back
to Renderers and created a PythonRenderer and a pydocRenderer. At this
point Zope crashed (SIGBUS(10)). Reloading the Renderers page crashed it
every time (except once..) NB I'm on freebsd and used to see a lot of
these but this is the first one I've seen since increasing python's stack
size to 1Mb some months ago.
Deleted the Zpydoc and started over. Created a PythonRenderer. Tried to
create a ZopeRenderer and got::
Traceback (innermost last):
File /usr/local/zope/software/lib/python/ZPublisher/Publish.py, line 98, in publish
File /usr/local/zope/software/lib/python/ZPublisher/mapply.py, line 88, in mapply
File /usr/local/zope/software/lib/python/ZPublisher/Publish.py, line 39, in call_object
File /usr/local/zope/instance/Products/Zpydoc/renderers/Zope.py, line 84, in manage_addZopeRenderer
File /usr/local/zope/software/lib/python/OFS/ObjectManager.py, line 244, in _setObject
File /usr/local/zope/software/lib/python/OFS/ObjectManager.py, line 77, in checkValidId
Bad Request: The id "Zope" is invalid--it is already in use.
but a ZopeRenderer is created - looks like it's doing it twice.
Tried some more combinations of ZpyDocumentable path & renderer::
But all were empty.
Other niggles: no version.txt in the product directory, no contact email
Conclusion: this sounds really useful but it doesn't work yet. I'm looking
forward to the next release/more docs/working demo on the home site.
From: Simon Michael <simon@jo...> - 2003-07-17 22:13:26
Alan Milligan writes:
> It sounds like you are doing the right things - excepting you MUST
> select which modules within your ZpyDocumentable are to be documented -
> use the 'File Permissions' tab for this.
Ah, I missed that step didn't I ? Thanks Alan, will try it next chance I
get (also Dieter's DocFinder product).