MoinMoin ideas

This is a holding place for user stories describing potential new MoinMoin functionality. See SeattleMoinMoinExtensions for things already implemented. See MoinMoinPatches for other places hosting MoinMoin extensions.

Specifically, these are interesting to people living in Seattle, so maybe we're close enough to get together and pair on them.

Whatever you do, especially before you invest some time, discuss the implementation on the (developer) mailing list. The WebLog things for example will be built-in when the user-forms stuff is finished.

Update to 0.11 so that I don't ponder every time why a double-click does not open the editor. ;)

New Wiki Features/Bugs ?

Questions

New Stuff

Things wanted and easy to implement

These are ideas from MoinMoinIdeas that are both rather easy to implement, and need no core changes (i.e. are pure extension actions or macros):

GraphViz Integration

I want to be able to enter...

graph G {
  "wxPython Cookbook" -- RecipesControls;
  "wxPython Cookbook" -- RecipesCrossPlatform;
  "wxPython Cookbook" -- RecipesEvents;
  "wxPython Cookbook" -- RecipesImagesAndGraphics;
  "wxPython Cookbook" -- RecipesOther
  "wxPython Cookbook" -- StillToBeWritten;
  RecipesControls -- BuildingControls;
  RecipesControls -- CreatingCollectionOfControls;
  RecipesControls -- DataAwareControlsMixin;
  RecipesControls -- DatabaseCursorDecorator;
  DatabaseCursorDecorator -- DataAwareControlsMixin;
}

...and get out a clickable graph image map.

Not as hard as it sounds, since GraphViz actually does all the graph construction, and even outputs hyperlinks in the image map.

I'd put this on the MoinMoin wiki, but it seems to be down at the moment...

-- LionKimbro 2003-09-09 13:37:22

http://python.kw.ac.kr/moinmoin/komoin/moin.cgi/GnuPlot

Docs

A note on documentation: changeing help and system pages happens in the master wiki. All other changes elsewhere might be lost.

Also, if one of you volunteers to always keep docs in sync while I add new features, this would help a lot. --jh

Diffs

Timestamping

Blogging

What the heck is a Blog, a timestamp of an entry? See WebLog for a description of Blogs. -- BrianDorsey

Survey

Fix password entry

The current password system saves the password in the clear along with the users name and email address. While this may not be a problem at most sites, where I work it could be an offense that ends in termination.

I tried implementing crypt, but what happened is it churned the password. That is, the UserPreferences form gets the current password from the user file that is now encrypted and re-crypts it when the user saves their profile change.

I haven't yet figured out the flow of the code to determine how and when the password comes from and goes to the user file. For now I commented out the input password line of html.

I don't care if password is implemented or not. It is just wrong to have a record of a clear password on the system. It would be nice for the saved password to support any future functionality where it would be required.

This will change with 1.1, and for now the correct thing to do is to remove it from the form if it's a problem.

True literal behavior

Literal markups should be literal. In these examples the first line uses ampersand markup to enter the characters, the second line is the actual literal except the USER and TIME markups were interpreted when I saved the page.

Send new user homepage

One behavior I would like to see in the UserPreferences is to send an email to a new user with their logon link and a link to their homepage so that they will use the site.

I configured the security on my work internal site so that you need to set your UserPreferences before you can edit a page. It would be cool to generate a homepage for the new user with an email link and CategoryHomepage on it, and to set the user subscription to their own homepage.

Misc

Picture posting

Plugin

Another option for implementing this: Since security options have been added to MoinMoin, it's probably possible to have two different moin.cgi & moin_config.py files in different directories on your web server. Setup one to allow editing and one to deny it to everyone. Setup your webserver to authenticate on the directory that allows editing, and make the read only site public. Should probably work, but we need to try it out. --BrianDorsey

Make the 2nd config import the other, and then add the SecurityPolicy class. or you make two ScriptAlias'es to the same moin.cgi and only allow editing when the URL is the editing one.

WebDAV interface

This was suggested by MikeOrr. It would allow you to edit wiki pages using a text editor that supported webdav... or with any editor, by using the WebDAV filesystem for Linux, or Windows' webfolders.

I imagine a button or link (action?) on every wiki page that would launch your favorite text editor to edit the page...

Python Davserver is some WebDAV code for python. Requires 4DOM. Hasn't been maintained in a while.

mod_dav is a WebDAV module for Apache. This requires root access to install. but should be pretty straightforward to configure for use with MoinMoin.

--AdamFeuer

Btw, MoinMoin already supports WikiXmlRpc, or you can get to it through this Perl library (Python bindings for the most important functions are in CVS): WikiGateway. There is also a proxy which can bridge Atom requests and a MoinMoin: AtomGateway.

People who're interested in Pairing on these ideas

If you're interested in working on any of these ideas, please add your name below and contact some of the other people to setup a time and pick one!


See also WikiFeatures, a wiki compiling lists of wiki feature ideas.

MoinMoinIdeas (last edited 2008-03-04 08:33:03 by localhost)