Future
FutureBack to Snip <-- Previous Change
| Diff Summary | |||||
|---|---|---|---|---|---|
| Title | |||||
| Date | 2008-04-19 23:45:26 | 2008-04-19 23:54:14 | |||
| Editor | Herbert Poul | Herbert Poul | |||
| Tags | |||||
| 2008-04-19 23:45:26 by Herbert Poul | 2008-04-19 23:54:14 by Herbert Poul | ||||
|---|---|---|---|---|---|
| f | 1 | This document describes a few possible future dire | f | 1 | This document describes a few possible future dire |
| > | ctions of SCT - and what features could be impleme | > | ctions of SCT - and what features could be impleme | ||
| > | nted. | > | nted. | ||
| 2 | 2 | ||||
| n | 3 | Some things might already be started in the subver | n | 3 | Some things (from the 'Framework' section) might a |
| > | sion trunk without any documentation. | > | lready be started in the subversion trunk without | ||
| > | any documentation. | ||||
| 4 | 4 | ||||
| 5 | If you are interested in any of those features, or | 5 | If you are interested in any of those features, or | ||
| > | want to discuss the future of SCT, don't hesitate | > | want to discuss the future of SCT, don't hesitate | ||
| > | to [use the forum](http://sct.sphene.net/board/sh | > | to [use the forum](http://sct.sphene.net/board/sh | ||
| > | ow/15/) | > | ow/15/) | ||
| 6 | 6 | ||||
| t | t | 7 | |||
| 8 | # Wiki | ||||
| 9 | |||||
| 10 | The wiki application has not seen as many feature | ||||
| > | enhancements lately as the forum, basically becaus | ||||
| > | e i think it is already "good enough" for my purpo | ||||
| > | ses. But considering the endless possibilities for | ||||
| > | wikis there are many ideas: | ||||
| 11 | |||||
| 12 | - Wiki snip discussions/comments | ||||
| 13 | - Not necessarily "only" simple comments which | ||||
| > | can be added at the bottom of a page - maybe even | ||||
| > | discussions directly for each paragraph ? section | ||||
| > | ? headline ? | ||||
| 14 | - 'Publish status' for a wiki snip | ||||
| 15 | - ever modified a wiki snip but wished to "sav | ||||
| > | e" the current status, without modified what end u | ||||
| > | sers can see online ? - or have someone else revie | ||||
| > | w it first ? - i think this could even be useful f | ||||
| > | or wiki snips, not just for a full-blown CMS. | ||||
| 16 | - Fine-grained permissions (not very creative, it' | ||||
| > | s on the issue tracker) | ||||
| 17 | |||||
| 18 | |||||
| 19 | # Forum/Board | ||||
| 20 | |||||
| 21 | The [Board|forum] is already very powerful thanks | ||||
| > | to the 'Category Types' - but there is still more | ||||
| > | potential. | ||||
| 22 | |||||
| 23 | - Dynamic categories (for example to create the co | ||||
| > | mments feature for the wiki - one category for eve | ||||
| > | ry wiki snip ? automatically created as soon as a | ||||
| > | user posts a "comment") | ||||
| 7 | 24 | ||||
| 8 | 25 | ||||
| 9 | # Framework | 26 | # Framework | ||
| 10 | 27 | ||||
| 11 | I have always tried to keep things as generic as p | 28 | I have always tried to keep things as generic as p | ||
| > | ossible - this made the [Community] application (i | > | ossible - this made the [Community] application (i | ||
| > | n my opinion) a good toolbox for developing django | > | n my opinion) a good toolbox for developing django | ||
| > | applications. | > | applications. | ||
Powered by Sphene Community Tools