File: wikid.info, Node: Hacker, Next: Index, Prev: User, Up: Top 4 Hacker ******** WIKID can be improved in many ways. (This is another way of saying it is very far from perfect!) Here are some ideas, by no means exhaustive, to get you started: * Replace listener w/ GNU Serveez. This would also have the benefit of wikid being able to use fifos (and whatever else Serveez supports in the future). * Reorgnanize database tables. Currently there are four tables, two of which are used for reverse mapping, somewhat of a waste. It would be better to use one table for the pages and have the data be in rfc822-compliant form. This allows easy representation of Title, URL, Last-Update, Permissions, and other meta-data, which can be kept in core and crossreferenced as needed. * Make page header, footer, etc (styles / eye-candy) configurable. * Use correct HTTP caching protocols. At the moment, WIKID simply uses the "Refresh" for the "ok" page, but doesn't add anything for other pages. * Make markup items configurable. * Internationalize buttons, etc. * Use cookies (gasp, horror) to save user preferences (if any). * Add "wikid-admin archive [DIR]" command. The archive directory should be specifiable in the configuration file. * Make "wikid-admin init" handle single arg DIR instead of requiring explicit listing of all files (interpret DIR as "DIR/*" and do globbing). * Come up w/ a way to have special pages trigger other cgi scripts. For example, a wikid page used for "code analysis" could trigger the running of `guile-tools lint', which would be appended. * Augment "append" functionality to mimic bulletin boards, etc. * Keep statistics, publish them. * Enable easy access to published archives (if any). This is the so-called "right to fork" support. Please feel free to discuss these or propose new ideas (as long as they don't support for "WikiWords" :-) on the `guile-user' mailing list. You can post patches to `guile-sources' or send them to the author directly.