It may be notable that I'm also working on another extension. It
duplicates code from a number of ParserFunction extensions, cleans them
up, extends them, and adds a number of more features not offered
anywhere else.
With that being the case, there are a lot of requests for new
parserfunctions, and a lot of them don't fit within the small extension,
a number of those can always be pointed towards WikiCode instead.
For those of you interested, it's still in the development stages but:
http://dev.wiki-tools.com/wiki/WikiCode <- Testcases for some of the
parserfunctions being developed currently.
http://dev.wiki-tools.com/wiki/Test <- Testcases for looping functions
(My only bug left to handle is the nested parserfunctions... I think I'm
expanding at the wrong point in time)
http://wiki-tools.com/wiki/WikiCode/Drafting <- Some documentation on
planned additions and improvements to parserfunctions. (Do note it's
rather old and some things have changed, that Proposed Escapes section
is completely irrelevant now, since the preprocessor allows us to nest
parserfunctions in a way that works for loops... <g> not that Tim
intended in his rewrite being used for evil... heh)
http://svn.nadir-point.com/viewvc/mediawiki-extensions/trunk/WikiCode/
<- Current source code for the extension.
Oh, Expr.php is listed there, however I'm thinking of doing something
else. Originally I hunted around for some C math parsers (ie: Something
you could input a formula into and get a returned result). However, now
I'm thinking of writing my own math engine, using the way the new
preprocessor works as an idea on how to do it. Hopefully this should
allow for a far more featured #expr tag.
Do note, that WikiCode's purpose is making complex templates more
readable (easier to understand), easier to create, and lighterweight on
the servers. Not really turning WikiText into a programming language,
^_^ the Code bit is just a bit of a joke alluding to how close the
extension actually goes to that line.
Though, I'm happy to say that one of my favorite little creations is
near complete. #split-and-merge, it's a nice little tool that'll make a
lot of the things we use ugly and evil repetition on much cleaner.
Though, I need to extend it to support templates, and also predefined
patterns as well. Though actually, I think I'm also going to need to
support a first=.
~Daniel Friesen(Dantman, Nadir-Seen-Fire) of:
-The Nadir-Point Group (
http://nadir-point.com)
--It's Wiki-Tools subgroup (
http://wiki-tools.com)
--The ElectronicMe project (
http://electronic-me.org)
--Games-G.P.S. (
http://ggps.org)
-And Wikia ACG on
Wikia.com (
http://wikia.com/wiki/Wikia_ACG)
--Animepedia (
http://anime.wikia.com)
--Narutopedia (
http://naruto.wikia.com)
Siebrand Mazeland wrote:
The ParserFunctions extension currently has 44 open
issues in Bugzilla (38 new, 1 assigned, 5 reopened - 1 major, 20 normal, 3 minor, 1
trivial, 19 enhancement)[1]. Recently there have been some discussions on this list on
triage and assigning of issues. Who volunteers to do work on ParserFunctions, and get some
issues closed?
Cheers! Siebrand
[1]
https://bugzilla.wikimedia.org/buglist.cgi?bug_file_loc=&bug_file_loc_t…
_id&query_based_on=