web commit by joey

[ikiwiki.git] / doc / todo.mdwn

diff --git a/doc/todo.mdwn b/doc/todo.mdwn
index 71c0eb9727a8e74fc066b78dd63c55e60ace39dd..3e2374a4f37ff5015f3f54bee5576ecd82ce8027 100644 (file)
--- a/doc/todo.mdwn
+++ b/doc/todo.mdwn
@@ -1,25 +1,5 @@
 ## online page editing
 
 ## online page editing
 

-* Missing conflict detection, just overwrites changes and does not svn up
-  first..
-
-  How to resolve this? Would this work when saving a page?
-
-  1. write changes to wc
-  2. svn up (so it can merge with any other changes)
-  3. check for conflicts
-  4. if conflicts, read in page w/conflict markers, svn revert page, and display resolution form
-  5. otherwise, svn commit
-  6. if commit fails, perhaps we were raced and there are conflicts still; so check for conflicts and if found, goto 2.
-
-  No, it won't work, because the other committer updates the srcdir when they make their commit, so svn does not get a chance to merge in the changes on update in step 2. Hmm..
-
-  Well, it could keep track of the version number of the page it started editing, and if it's changed during the edit, ask svn to merge all changes from that version number to head into the page after writing it out. Doing that without races with other svn committers seems tricky.
-
-  If each commit operated in a separate copy of the wc, that was created for the commit, the steps above would work. But it would be very expensive to make and maintain all those copies.
-
-  Note that unless we use `svn lock`, we really can't "warn" about concurrent edits and such the way other wikis do, which is ok, since that system sucks anyway. Using svn up for smart merging will be much nicer most of the time.
-   

 * Eventually, might want page deletion.
 * Eventually, might want file upload.
 
 * Eventually, might want page deletion.
 * Eventually, might want file upload.
 


@@ -117,11 +97,6 @@ recentchanges that goes to the diff for any listed change.
 Possibly add "next 100" link to it, but OTOH, you can just use svn log if
 you need that data..
 
 Possibly add "next 100" link to it, but OTOH, you can just use svn log if
 you need that data..
 

-## base wiki
-
-Need a toned down version of this wiki with a basic frontpage, sandbox and
-docs to use as a seed for new wikis.
-

 ## search
 
 * full text (use third-party tools?)
 ## search
 
 * full text (use third-party tools?)


@@ -138,4 +113,12 @@ Some wikis will need the abiity to lock a page, or the whole wiki, so that only
 
 Probably it's ok if locking is only supported for web commits.
 
 
 Probably it's ok if locking is only supported for web commits.
 

+## User settings page
+
+A cgi page to allow a user to log out and to edit their prefs, including password, email, and anything we add later (subscriptions, etc).
+
+## Logo
+
+ikiwiki needs a logo. I'm thinking something simple like the word "ikiwiki" with the first "k" backwards; drawn to show that it's "wiki" reflected.
+

 ## [[Bugs]]
 ## [[Bugs]]