| At line 7 changed one line |
| I am considering using JspWiki as a lightweight CMS for web site. Maybe, you might think of JspWiki as Plone-light more than a Wiki in this case. With JspWiki templates you can get it looking nice, like a "real" web site not just a Wiki and with the upcoming auth* you can managed security more like a CMS than just a Wiki. Also, being able to disable CamelCase and use brackets with alternative display text is nice for more general web site development. |
| I am considering using JspWiki as a lightweight CMS for web site. Maybe, you might think of JspWiki as Plone-light more than a Wiki in this case. With JspWiki templates you can get it looking nice, like a "real" web site not just a Wiki and with the upcoming auth* you can managed security more like a CMS than just a Wiki. Also, being able to disable autolinking of CamelCase and use brackets with alternative display text is nice for more general web site development. So you have several features which make JspWiki possible for more than the usual Wiki functions. |
| At line 11 changed one line |
| It provides a menu tree for use in the left menu. This is a custom tree defined in a Wiki page called MenuTree using nested bullets and links. This is not an attempt to autogenerate some messy graph out of the wiki links. The most significant benefit over a plain left menu is that it expands and collapses to diplay the link for the current page. So you can have a large number of links in the menu without having to have them all displayed all the time. It also highlights the link for the current page and displays it's children. Different CSS styles are used so that you can use images for open/closed folders as well as distinguish between nodes with children and leaf nodes. |
| It provides a menu tree for use in the left menu. This is a custom tree defined in a Wiki page called "~MenuTree" using nested bullets and links. This is not an attempt to autogenerate some huge messy graph out of all the constantly changing wiki links. A significant benefit over a plain left menu is that it expands and collapses to diplay the link for the current page. So you can have a large number of links in the menu without having to have them all displayed all the time. It also highlights the link for the current page and displays it's children. Different CSS styles are used so that you can use images for open/closed folders as well as distinguish between nodes with children and leaf nodes. |
| At line 14 changed one line |
| a page called "TeamsAndWorkingGroups" is being displayed which corresponds to the link just called Teams in the menu.\\ |
| a page called "~TeamsAndWorkingGroups" is being displayed which corresponds to the link just called "Teams" in the menu.\\ |
| At line 18 changed one line |
| The data for the menu is maintained in a wiki page called "MenuTree". The example used in the screen shot was using this for MenuTree\\ |
| The plugin is included in LeftMenu like this\\ |
| At line 20 added 5 lines |
| [{INSERT org.ecoinformatics.seek.web.wiki.MenuTreePlugin }] |
| }}} |
|
| The data for the menu is maintained in a wiki page called "~MenuTree". The example used in the screen shot was using this for ~MenuTree\\ |
| {{{ |
| At line 39 changed 4 lines |
| and the plugin is included in LeftMenu like this\\ |
| {{{ |
| [{INSERT org.ecoinformatics.seek.web.wiki.MenuTreePlugin }] |
| }}} |
| It currently only works for internal wiki links.\\ |
| At line 44 changed one line |
| The [source code|MenuTreePlugin.zip] is attached. Like I said, this is really just a rough proof of concept for now, so I haven't even bothered with a Jar file install. It's just the source files and a sample.css showing you the names of the classes used. |
| The plugin checks the latest version of ~MenuTree and refreshes the data structure when it changes. |
| At line 48 added 3 lines |
|
| The [source code|MenuTreePlugin.zip] is attached. Like I said, this is really just a rough proof of concept for now, so I haven't even bothered with a Jar file install. It's just the source files and a sample.css showing you the the classes used (alhought I still haven't got list styles with images which work well across browsers). |
|
| At line 48 changed 3 lines |
| ** instead of the tree display the path horizontally (similar to breadcrumbs), e.g. TopPage > ChildPage > CurrentPage |
| ** option to do display only the ancestors and decendents of the current page. Currently top level nodes are always shown which is appropriate for a menu, but not if you were just wanting to show related pages by including the plugin in the current page rather than the left menu it would be in appropriate. |
| * related to the above, I am consider developing a version which has a set of top-level tabs and have the left menu be the submenu of the the current tab. |
| ** instead of the tree, display the path horizontally (similar to breadcrumbs), e.g. Top Page > Child Page > Current Page |
| ** option to do display only the ancestors and decendents of the current page. Currently all top level nodes are always shown which is appropriate for a menu, but not if you were just wanting to show related pages by including the plugin in the current page rather than the left menu it would be in appropriate. |
| * I am considering developing a version which has a set of top-level tabs and have the left menu be the submenu of the the current tab. |
| At line 52 changed one line |
| -- ~SteveTekell |
| --~SteveTekell |
