Todo
Color coding is red for high priority tasks (immediately required to proceed on dev.helma.org) and yellowish orange for medium priority tasks (immediately useful).
| Task |
Description |
Time estimate |
Status |
|---|
| Reimplement Updates to improve scalability |
The updates feature currently does not scale, because it creates a new link group for each and every update (by including the update timestamp with up to the second in the link type). Instead, only one linkgroup per day should be created, with the link going to the version page (or revision page, for svn updates) instead of the main page. |
1 day |
|
| Wiki Markup |
Wiki Markup is pretty nice already, but some features are still missing. See http://trac.edgewall.org/wiki/WikiFormatting for inspiration.
|
|
|
| Documentation |
We need user-level documentation describing Gobi forms/types, how to work with custom properties, how to use the list macro and custom skins, etc.
|
|
|
| Notification mailer framework |
Provide a Gobi service that allows pages to send various messages to various persons on various events. |
1 day |
half done |
| RSS feeds |
Implement RSS 2.o feeds for:
Site updates- A page's child pages
Page history
|
1 day |
partly done: looking good. |
| Page creation permissions and layout |
- Ambiguity between "create new page of this type" and "create new child page to this type"
Wiki pages create children, but most often building deep hierarchies is not what you want to let happen.- Display prominent "add page" links for certain spots (wiki, weblog).
- Child type chooser currently doesn't honor create permissions
- Conflict between fixed child type and child type chooser
|
|
partly done, some points may be fixed |
| Introduce better abstractions for common tasks |
Introduce higher level abstractions in basic Gobi application architecture. Currently, many tasks such as copying properties from one object to another are performed ad-hoc, making the code very verbose and dispersed.
This could be done by tightly integrating one of the big JS libraries, or by coming up with our own set of library building blocks. Should be combined with highly integrated rich client/DHTML/AJAX support. |
ongoing |
|
| Form macro |
Complete palette of types supported by form macro |
1 day |
|
| Link Editor |
- Currently there is a duality here: popup link selector for admin stuff, autocomplete input field for custom link properties. I think the two should be combined.
- Missing features in link editor:
- Single selection
- Deep selection (already working for autocomplete?)
- Create-on-demand (already working for autocomplete?)
- (Link editor should be able to return Markup struct rather than writing out directly to response. That way it can easily be used for both skins and programmatic rendering. Currently, the latter is a pain.)
|
2 days |
|
Fixed Todos: Search plugin, Backlinks, Auto TOC, Form property history, Default values for custom properties, Update page, Subversion plugin, Comments for every page
|