Summary | Render wiki page as help file |
Queue | Wicked |
Type | Enhancement |
State | Rejected |
Priority | 1. Low |
Owners | |
Requester | duck (at) obala (dot) net |
Created | 08/05/2008 (6175 days ago) |
Due | |
Updated | 08/18/2008 (6162 days ago) |
Assigned | |
Resolved | 08/18/2008 (6162 days ago) |
Milestone | |
Patch | Yes |
State ⇒ Rejected
Patch ⇒ Yes
case we go back to it, and take this discussion back to the mailing
list.
vs. modifying the help system to point into a local wiki if one is
available?
having two separate mechanism for the same thing (programming and
updating files). Someone would like to keep the current help mechanism
because of off-line installations, so I created this renderer. But
now that we can synchronize wikies or render pages into static html
files I think this cannot be a big issue. I personally vote for wiki,
as is much more feature list (attached files, images, internal links,
multiply pages...) and easier to contribute.
State ⇒ Feedback
vs. modifying the help system to point into a local wiki if one is
available?
Priority ⇒ 1. Low
New Attachment: helpwiki.tgz
Patch ⇒ No
Milestone ⇒
Summary ⇒ Render wiki page as help file
Type ⇒ Enhancement
State ⇒ New
Queue ⇒ Wicked
An example of turba help.xml is added. help.wiki is the wiki page
source I created from turba current help file and the help.xml is the
rendered output.