A discussion of Sycamore development.
Currently being worked on by Philip and others:
"Wikis"/Farm support this is a big one. It's essentially reworking the code to operate effectively with multiple wikis running in the same Sycamore instance. There are lots of little details pertaining to how the individual wikis work together.
Some relevant details in the Wikis branch that don't have to do with how wikis work together are:
-
Better, easier access controls. The MoinMoin style access controls are hard to use and prone to breaking. New "Security" button, concept of user groups, security settings wiki-wide is all more straight-foward and all configurable via the wiki itself.
-
Better wiki configuration. The configuration of the specifics of a given wiki are easily do-able via the wiki interface.
-
Integrated Please provide an address. support.
Future stuff I'm interested in but haven't aren't working on or haven't worked on in a while:
-
Generic parsing/formatting. There's a branch called "parser experiments" that, I believe, has some old code I was playing with. The basic idea is that the underlying representation of a wiki page be a generic XML document and then it is rendered to HTML (and cached as such). The client can then be sent Wiki Markup (XML->Wiki Markup) or some sort of semantically markup-ed HTML (XML->HTML). Client can send back Wiki Markup (Wiki Markup->XML) or semantically marked-up HTML (HTML->XML).
I started writing the XML->HTML part. The idea was that, with these transforms in place, we could add on a WYSIWYG editor (this transformation is the first step, that is).
-
Semantic Wiki - Allow pages to contain relations and attributes.
Because the editor would be in java, it could be possible to allow users to choose between editor modules to use if we develop multiple models, thusly allowing more user compatibility. ~Dave
