- v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
- Use this page to report any issues related to the migration.
Difference between revisions of "User talk:Briess"
m (→Contact info?: new section) |
m (→Favicon: new section) |
||
| Line 22: | Line 22: | ||
Thanks for stepping up. Are you going to have an e-mail contact addy, for less public communication? --[[User:Albedo|Albedo]] 17:31, 16 September 2009 (UTC) | Thanks for stepping up. Are you going to have an e-mail contact addy, for less public communication? --[[User:Albedo|Albedo]] 17:31, 16 September 2009 (UTC) | ||
| + | |||
| + | == Favicon == | ||
| + | |||
| + | The favicon for the previous wiki seems not to have been copied over. [[User:VengefulDonut|VengefulDonut]] 18:36, 17 September 2009 (UTC) | ||
Revision as of 18:36, 17 September 2009
Extension request
(mostly copied from User talk:senso)
A string manipulation extension would allow things to be dynamically created from raw files and other powerful templates. With the upcoming big change to creature structure in DF, something that pulls info directly from raw data would really help rework the creature pages. I've been looking through some extensions, and one of these would fit well (in order of preference)
- http://www.mediawiki.org/wiki/Extension:MultiReplace
- http://www.mediawiki.org/wiki/Extension:RegexParserFunctions
- http://www.mediawiki.org/wiki/Extension:StringFunctions
The first one is a replacement function that can preform multiple replacements in one call (and it supports regex). The second one is a straightforward regex engine, and the last one is a collection of string manipulations. For my suggested purpose just one of the three would be enough, but none of them completely covers the tasks the of others. So, if possible, having all of them would be best. VengefulDonut 21:35, 15 September 2009 (UTC)
- Their functionality does overlap a lot. The differences are as follows:
- Multireplace can preform multiple replacements with one call, which the second one cannot. It can evaluate regular expressions for the replacement.
- RegexParserFunctions can preform a regex replacement. It can also be used for a regex search, which multireplace isn't meant for.
- Multireplace would be better suited for a template that generates diagrams. Regexparserfunctions could do this by nesting the function call many times, which I don't think is a good idea.
- Regexparserfunctions would be better suited for a template that pulls information from raw data files. Multireplace could do this by matching everything before and after the matchtext and cropping it, like so: (.*)(matchtext)(.*)=$2. However, to do this multireplace is effectively matching the entire page at once. VengefulDonut 22:50, 15 September 2009 (UTC)
Archive Subdomain problem
Sorry to bother, i sent an email to senso, but it seems that you are the new admin. Grats. Yesterday i was surfing the archive [1] and suddendly it started to redirect to a french blog. Now it redirect to the main wiki. (Actually every subdomain redirects to the main wiki, also invalid ones) Can you bring it back? I know that it's rarely used, but sometimes it's funny to build 2D nostalgia fortresses. --Tempus 09:13, 16 September 2009 (UTC)
Contact info?
Thanks for stepping up. Are you going to have an e-mail contact addy, for less public communication? --Albedo 17:31, 16 September 2009 (UTC)
Favicon
The favicon for the previous wiki seems not to have been copied over. VengefulDonut 18:36, 17 September 2009 (UTC)