Talk:Wiki as a book reader: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
(Version control?)
Line 3: Line 3:


We are currently looking into MoinMoin. It has a very good extensible architecture. It is fairly easy to add the missing features by adding actions, macros, and parsers. I will take a look at TiddlyWiki though.
We are currently looking into MoinMoin. It has a very good extensible architecture. It is fairly easy to add the missing features by adding actions, macros, and parsers. I will take a look at TiddlyWiki though.

== Version control? ==

While reading the page, I couldn't help but think "subversion can do that" and "subversion can do that as well" and "yeah that should also be possible with version control". So, how about some kind of mixture between version control and wiki?

Besides, I wanted to say that I don't like those ideas about using special unicode characters:
* breaks the concept
* clutters the document "source"
* disregards needs of colour-blind people
* mixes not only formatting and content (which is bad enough in HTML) but authoring information in addition
All that is just IMHO and my 2 cents.

I'll sign up a different time cos it's late in the night. [[User:84.158.225.130|84.158.225.130]] 19:11, 21 March 2006 (EST) (Benjamin B.)

Revision as of 00:11, 22 March 2006

TiddlyWiki plus synchronization software would be a start. Something like a tiny webserver that used SQLite or dbh for storage would be enough.

We are currently looking into MoinMoin. It has a very good extensible architecture. It is fairly easy to add the missing features by adding actions, macros, and parsers. I will take a look at TiddlyWiki though.

Version control?

While reading the page, I couldn't help but think "subversion can do that" and "subversion can do that as well" and "yeah that should also be possible with version control". So, how about some kind of mixture between version control and wiki?

Besides, I wanted to say that I don't like those ideas about using special unicode characters:

  • breaks the concept
  • clutters the document "source"
  • disregards needs of colour-blind people
  • mixes not only formatting and content (which is bad enough in HTML) but authoring information in addition

All that is just IMHO and my 2 cents.

I'll sign up a different time cos it's late in the night. 84.158.225.130 19:11, 21 March 2006 (EST) (Benjamin B.)