OpenWetWare:Software/Extensions: Difference between revisions
No edit summary |
|||
Line 20: | Line 20: | ||
**'''[[User:Austin|Austin]] 13:27, 13 March 2006 (EST)''': Good point, I actually hadn't thought about using this as an includable page rather than just for each user using it to filter their own recent changes. | **'''[[User:Austin|Austin]] 13:27, 13 March 2006 (EST)''': Good point, I actually hadn't thought about using this as an includable page rather than just for each user using it to filter their own recent changes. | ||
**'''[[User:Bill Flanagan|Bill Flanagan]] 13:27, 11 August 2007 (EST)''': I'm going to look into the extension. If we can create a map that exists as a wiki page that controls the behavior of the filtering, we can isolate at least some of the problems associated with upgrading. Content can be managed independent of the structure. Development can be done by more than one person: the technical details of modifying the code can be separated from the way the site is categorized. This may be more of a meta-goal than a specific outcome but I'll look into it and find out. | **'''[[User:Bill Flanagan|Bill Flanagan]] 13:27, 11 August 2007 (EST)''': I'm going to look into the extension. If we can create a map that exists as a wiki page that controls the behavior of the filtering, we can isolate at least some of the problems associated with upgrading. Content can be managed independent of the structure. Development can be done by more than one person: the technical details of modifying the code can be separated from the way the site is categorized. This may be more of a meta-goal than a specific outcome but I'll look into it and find out. | ||
**'''[[User:Austin J. Che|Austin Che]] 11:13, 11 August 2007 (EDT)''': I'm not sure what you're suggesting but there's already nothing in the extension that has anything to do with content. | |||
* [http://meta.wikimedia.org/wiki/ParserFunctions ParserFunctions] and [http://meta.wikimedia.org/wiki/StringFunctions StringFunctions]: useful for simplifying templates greatly. | * [http://meta.wikimedia.org/wiki/ParserFunctions ParserFunctions] and [http://meta.wikimedia.org/wiki/StringFunctions StringFunctions]: useful for simplifying templates greatly. | ||
Line 33: | Line 34: | ||
**'''[[User:Austin|Austin]] 18:03, 26 May 2006 (EDT)''': right...ok, done. | **'''[[User:Austin|Austin]] 18:03, 26 May 2006 (EDT)''': right...ok, done. | ||
**'''[[User:Bill Flanagan|Bill Flanagan]] 8:36, 11 August 2007 (EDT)''': I notice this extension's link has "gone missing". Is there another place we can link to it for information? Thanks! | **'''[[User:Bill Flanagan|Bill Flanagan]] 8:36, 11 August 2007 (EDT)''': I notice this extension's link has "gone missing". Is there another place we can link to it for information? Thanks! | ||
**'''[[User:Austin J. Che|Austin Che]] 11:13, 11 August 2007 (EDT)''': Nope...This is one of those extensions that probably is better if it didn't exist, at least in it's current form. Once the registry actually gets an API for getting more information about parts other than just linking to it, then it might actually be more useful. | |||
* http://meta.wikimedia.org/wiki/Cite/SpecialCite.php: 'Cite this page' support | * http://meta.wikimedia.org/wiki/Cite/SpecialCite.php: 'Cite this page' support | ||
* [[User:Austin/Extensions/LatexDoc|LatexDoc]]: For writing a LaTeX document on the wiki (see example at [[OpenWetWare:Feature test/LatexDoc]]). Now supports images and bibtex! | * [[User:Austin/Extensions/LatexDoc|LatexDoc]]: For writing a LaTeX document on the wiki (see example at [[OpenWetWare:Feature test/LatexDoc]]). Now supports images and bibtex! | ||
Line 46: | Line 48: | ||
* [[User:Austin/Extensions/WikiChat|WikiChat]] | * [[User:Austin/Extensions/WikiChat|WikiChat]] | ||
**'''[[User:Bill Flanagan|Bill Flanagan]] 8:36, 11 August 2007 (EDT)''': This is a fantastic extension. But I've heard that it puts a big load on the server when 20 or more folks are using it. Have there been any measurements done on the load it's responsible for? Since it uses AJAX (i.e., receiving and sending tons of small messages from every client while in use), even a bigger server may not allow it to scale very well. There may be a way to do the same thing with IM clients such as GoogleTalk. The log of the IM sessions could be scrolled onto the chat page interactively while the chat is executed within GoogleTalk. This is a long-term item but I wanted to make a note of it here. Please reply if you have anecdotal evidence of how useful it is and how it could change to work better. | **'''[[User:Bill Flanagan|Bill Flanagan]] 8:36, 11 August 2007 (EDT)''': This is a fantastic extension. But I've heard that it puts a big load on the server when 20 or more folks are using it. Have there been any measurements done on the load it's responsible for? Since it uses AJAX (i.e., receiving and sending tons of small messages from every client while in use), even a bigger server may not allow it to scale very well. There may be a way to do the same thing with IM clients such as GoogleTalk. The log of the IM sessions could be scrolled onto the chat page interactively while the chat is executed within GoogleTalk. This is a long-term item but I wanted to make a note of it here. Please reply if you have anecdotal evidence of how useful it is and how it could change to work better. | ||
**'''[[User:Austin J. Che|Austin Che]] 11:13, 11 August 2007 (EDT)''': See this [http://www.phpfreechat.net/forum/viewtopic.php?pid=6628 thread]. Some seem to be able to get it to scale while others can't. It also links to this [http://www.chabotc.com/javascript/webchat-20-first-release WebChat2.0] which looks neat but seems to be less browser compatible (doesn't work on my Opera). But I think the idea of using a web chat program that talks with IRC is great. | |||
*[[Special:Editcount]]: Show edit stats for users. Can be linked as <nowiki>[[Special:Editcount/user]]</nowiki> and included <nowiki>{{Special:Editcount/user}}</nowiki> | *[[Special:Editcount]]: Show edit stats for users. Can be linked as <nowiki>[[Special:Editcount/user]]</nowiki> and included <nowiki>{{Special:Editcount/user}}</nowiki> | ||
*[[User:Austin/Extensions/UserDefaultPage|UserDefaultPage]]: allow users to change their default page in their preferences | *[[User:Austin/Extensions/UserDefaultPage|UserDefaultPage]]: allow users to change their default page in their preferences |
Revision as of 08:13, 11 August 2007
Back to Community Portal |
Installed ExtensionsGo to Special:Version to see the definitive list of installed extensions and their versions. See OpenWetWare:Feature test to check that the extensions are working. If you wish to discuss extensions on openwetware, sign up for the mailing list. The following extensions are installed on OpenWetware: Critical ExtensionsCritical extensions are either those which if they break would cause many pages to "break" and as such, these extensions should be considered as important to support (for upgrades, etc). Another way to look at this: if we aren't willing to support these, then we shouldn't encourage people to use these. The known dependencies of these are listed to help in smooth upgrades.
Unknown criticality
Non-critical extensionsNon-critical extensions are defined as those which don't significantly change pages or remove important functionality. Users may use these as they wish and they should be able to easily adapt if we turn them off suddenly.
Deprecated extensionsDo not use these extensions. They may be removed at some point in the future. Desirable or pending extensionsList extensions you would like to install here and vote or de-vote for ones you'd like.
See http://meta.wikimedia.org/wiki/Category:Mediawiki_Extensions for some extensions.
Will not be installed
Writing new extensions or special pages
|