Should TWiki maintain a list of standard extensions? For example TWikiDrawApplet is a very useful tool, but (perhaps) not everyone will want to add on the requirement of Java capable clients. If it is considered an extension, then it is not necessary to install that one component.

On the other hand, Java capable clients are so widely available that as long as the wiki view degrades well over older or simpler browsers, then most of the capability will remain. Only the ability to edit the drawings would be hindered. Likewise anyone viewing a Wiki through a text only tool like Lynx, would be able to see all of the text, but not be able to view images. The current TWiki is still usable through Lynx for 99% of Wiki work that a few images probably wouldn't hurt. Also adding an extension mechanism could increase the complexity of installing TWiki.

-- JamalWills - 27 Jul 2000

---

I would vote for a simple TWiki installation with just one package. At the time we have several useful FeatureAddOns we can put a pointer in the installation package to an "official" TWikiAddOnPackages topic (done already in a similar way for the KnownIssuesOfTWiki01May2000 topic). Users would download the add ons from the web.

- PeterThoeny - 28 Jul 2000