Re: [Zope-dev] Proposed Additional reStructuredText Deliverables
I'll volunteer for (1). I think implementing it will be easy, but writing tests for it could be tricky... On Monday, November 11, 2002, at 10:44 PM, Andreas Jung wrote: 3) is a *must-have feature*, 1) and 2) are *can-have features* (especially 2) ). At least for 1) I need a volunteer ;-) -aj 1. reStructuredText support in the Zope Help System. 2. reStructuredText support for Product README handling. 3. Ensuring that Page Templates and Python Scripts can access the reStructuredText.HTML() function. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Proposed Additional reStructuredText Deliverables
With Andreas plugging away at reStructuredText Integration into Zope,
I'm thinking of some extra deliverables. I'm not sure how deep we want
to put ReST support in at the moment, considering that while the spec
is pretty solid the codebase is still a moving target, but I would like
to add and help work on the following proposed deliverables to the
project:
1. reStructuredText support in the Zope Help System.
2. reStructuredText support for Product README handling.
3. Ensuring that Page Templates and Python Scripts can access the
reStructuredText.HTML() function.
#1 looks like it would require adding a ReSTHelpTopic class in the
HelpSys package which could probably mimic (or even sublass) the
HelpSys.HelpTopic.STXTopic class. Then support would have to be added
into ``ProductContext.registerHelp()`` to map certain file suffixes to
the ReSTHelpTopic ('.rst', etc).
#2 could probably be handled the same way (look for a 'README.rst'
file), but may be served better if the contents of the README.txt could
be introspected enough to detect format. :\
#3 is easy, I just want to make sure it's not forgotten. We just have
to decide the right one way to do it: expose it in
'Products.PythonScripts.standard' where all of the other DTML
formatters are exposed, or out of its own namespace (ie:
tal:content=structure python:modules['reStructuredText'].HTML(foo)).
Or both ways.
--
Jeffrey P Shell
[EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposed Additional reStructuredText Deliverables
3) is a *must-have feature*, 1) and 2) are *can-have features* (especially
2) ). At least for 1) I need a volunteer ;-)
-aj
--On Montag, 11. November 2002 22:29 -0700 Jeffrey P Shell
[EMAIL PROTECTED] wrote:
With Andreas plugging away at reStructuredText Integration into Zope, I'm
thinking of some extra deliverables. I'm not sure how deep we want to
put ReST support in at the moment, considering that while the spec is
pretty solid the codebase is still a moving target, but I would like to
add and help work on the following proposed deliverables to the project:
1. reStructuredText support in the Zope Help System.
2. reStructuredText support for Product README handling.
3. Ensuring that Page Templates and Python Scripts can access the
reStructuredText.HTML() function.
# 1 looks like it would require adding a ReSTHelpTopic class in the
# HelpSys package which could probably mimic (or even sublass) the
# HelpSys.HelpTopic.STXTopic class. Then support would have to be added
# into ``ProductContext.registerHelp()`` to map certain file suffixes to
# the ReSTHelpTopic ('.rst', etc).
# 2 could probably be handled the same way (look for a 'README.rst' file),
# but may be served better if the contents of the README.txt could be
# introspected enough to detect format. :\
# 3 is easy, I just want to make sure it's not forgotten. We just have to
# decide the right one way to do it: expose it in
# 'Products.PythonScripts.standard' where all of the other DTML formatters
# are exposed, or out of its own namespace (ie: tal:content=structure
# python:modules['reStructuredText'].HTML(foo)). Or both ways.
--
Jeffrey P Shell
[EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists - http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
-
-Andreas Jung http://www.andreas-jung.com -
- EMail: andreas at andreas-jung.com -
-Life is too short to (re)write parsers -
-
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
