Issue #SCB2738 () Addon Wiki features

Activity report on

  *Enhancement SCB2738 - Addon Wiki features*

  Scarab Link: http://www.solitone.org/scarab/issues/id/SCB2738
  Module: Scarab


  Activity generated by Hussayn Dabbous ([email protected]) at 12/19/2008 15:20

  *Reasons for the changes*


  *Comments*
  - By Hussayn Dabbous - 12/19/2008 15:24 ---
  "I plan to add following features:

1.) In Comments section:

Currently Scarab automatically converts Issue entries to Hyperlinks. e.g. SCB2738 is rendered as a link to another issue.
I want to add the new syntax:  [Anything], where anthing can either be a pointer to an other issue like above, or ... a pointer to a WikiPage, where "WikiPage" can be

* an internal page, which will be rendered in the Scarab canvas. Such a page will be fully controlles by Scarab itself. The data will be kept within the database, the page is rendered inside the sub page, where we currently see the issues. Such a page basically will behave like a Scarab comment behaves, but it gets an only editing is allowed. The "name" of the page is identical to whatever name has been placed in the [Anything] markup (see above). If such a page does not yet exist, the user is asked to create one, or CANCEL the action. That is basically how Wikis operate.

* an external wiki. The link to the wiki shall be configured in the Scarab properties. The idea is to generate Hyperlinks to the configured wiki. As soon as the user clicks on the link, the Scarab context is lost and the user is working in the external wiki. Optionally the link to the wiki can create a new page.

As a further enhancement i want to allow the syntax:  [human readable title|Anything] where "human readable title" will be rendered as text, whil "Anything" will be used as the Hyperlink anchor.

This add on to Scarab will allow a very tight integration of knowledge data into issues. I want to use this add on for a customer care system, where customers can retrieve information from one single point of information (scarab), before entering a new issue. Especially when all information is hosted by Scarab, the search engine can create hits into Wiki-pages and allow better research. As a drawback we would need to enhance the search result page somewhat to allow other links beside links to issues...


2.) Enable better markup support , so that we can add code sections, chapters, tables, etc. I personally am a fan of jspWiki and they did a great job on that, which i do not want to replicate, but as we have Radeox we could use it ...

3.) As another option i could imagine to replace radeox by a tight wiki-integration where the wiki engine runs in the background, but gives the full functionality to Scarab users. I could imagine to work on such a tight integration for jspWiki, which in my eyes would fit very well..."

  - By Hussayn Dabbous - 12/19/2008 15:20 ---
  "I plan to add following features:

1.) In Comments section:

Currently Scarab automatically converts Issue entries to Hyperlinks. e.g. SCB2738 is rendered as a link to another issue.
I want to add the new syntax:  [Anything], where anthing can either be a pointer to an other issue like above, or ... a pointer to a WikiPage, where "WikiPage" can be

* an internal page, which will be rendered in the Scarab canvas. Such a page will be fully controlles by Scarab itself. The data will be kept within the database, the page is rendered inside the sub page, where we currently see the issues. Such a page basically will behave like a Scarab comment behaves, but it gets an only editing is allowed. The "name" of the page is identical to whatever name has been placed in the [Anything] markup (see above). If such a page does not yet exist, the user is asked to create one, or CANCEL the action. That is basically how Wikis operate.

* an external wiki. The link to the wiki shall be configured in the Scarab properties. The idea is to generate Hyperlinks to the configured wiki. As soon as the user clicks on the link, the Scarab context is lost and the user is working in the external wiki. Optionally the link to the wiki can create a new page.

As a further enhancement i want to allow the syntax:  [human readable title|Anything] where "human readable title" will be rendered as text, whil "Anything" will be used as the Hyperlink anchor.

This add on to Scarab will allow a very tight integration of knowledge data into issues. I want to use this add on for a customer care system, where customers can retrieve information from one single point of information (scarab), before entering a new issue. Especially when all information is hosted by Scarab, the search engine can create hits into Wiki-pages and allow better research. As a drawback we would need to enhance the search result page somewhat to allow other links beside links to issues...


2.) Enable better markup support , so that we can add code sections, chapters, tables, etc. I personally am a fan of jspWiki and they did a great job on that, which i do not want to replicate, but as we have Radeox we could use it ...

3.) As another option i could imagine to replace radeox by a tight wiki-integration where the wiki engine runs in the background, but gives the full functionality to Scarab users. I could imagine to work on such a tight integration for jspWiki, which in my eyes would fit very well..."

------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=458&dsMessageId=987471

To unsubscribe from this discussion, e-mail: [[email protected]].