A5KellerClark
Last modified by Hal Eden on 2010/08/20 11:06
A5KellerClark
Group Members
Scott Keller, Matthew ClarkTask 1
Matt: Another meta-design environment is a bulletin board, or message board, where users can ask questions. This has an even lower barrier of entry to a wiki; a user can just post a question to the group, or post a response. Message boards still work well at distributing information from knowledgeable users to new users. Wikis are navigated by built in navigation and a search function, but neither of these will always find the information a user is seeking in a reasonable amount of time. With a message board, a user can post their question in whatever language they want, and the group can ask for clarification, redirect them to other threads, or answer the question. Scott: Immediately when I think of a meta-design environment, the persistent online world of Second Life comes to mind. Like a wiki, the entirety of its content is user-created. Also, like a wiki, the design framework of the application was created with this intent in mind. However, a wiki is purely a means to convey information with limitations of being restricted within the framework of the website and formatting options available. Second Life has far extended these limitations by allowing users to completely create their environment and create the rules within it. If you really wanted to, you could even create a library in Second Life that works like a wiki. The meta-design mentality firmly planted in all stages of the design and implementation of SL, have created a completely free form world where users can do anything and contribute anything.Task 2
| xwiki | swiki/AniAniWeb | xwiki is a second generation, full-featured, professional wiki. XWiki software is developed in Java and under the LGPL open source license.[1] | swiki is a wiki aimed at education, written in the Squeak programming language. The AniAniWeb tries to answer the questions "What will personal home pages look like once their use and meaning is determined by user needs, rather than current limitations? What practices do these personal home pages afford? What do the adopters get out of them?[2]" |
|---|---|---|---|
| Blog | ? | ||
| excellent versioning, easy to roll back to any prior version | shows you the previous versions, but roll back has to be done by copy and paste. | ||
| strong rights management- supports page-by-page locking | supports locked pages, but it is not clear how to create them. | ||
| LDAP authentication | simple authentication scheme, which supports groups | ||
| PDF export | ? | ||
| skinning | skinning | ||
| scripting engine | ? | ||
| extensible | ? | ||
| highly modular architecture. | ? | ||
| Java, large application, saving is quite slow. The preview has bugs. Text wrapping issues. | Squeak, smaller application, saves are fast. |
