Someone called me yesterday to ask for a competent mediawiki developer to help with... something vague. combining a wiki with other content sources. I wish there were a simple place to point them to post a job request... SJ On 6/6/07, aretai aretai <aretaiuc(a)gmail.com> wrote: puny accomplish software. ;) on to don't promoting -- ++SJ _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

On 06/06/07, aretai aretai <aretaiuc(a)gmail.com> wrote: Hmm... two thoughts about this 1) why not use the opportunity to charge people to advertise positions? it seems very standard... and a wasted opportunity to do it for nothing.

screams "threaded discussions/forum style environment" to me. A wiki's not intended to perform every conceivable purpose for every conceivable website. So why not use that is designed to handle threaded discussion, ie forum software?

documentation. see? use software for their strengths, not for EVERYTHING :) ps to Aretai. if my ideas succeed I hope it is because they are good and I present them well and they meet the right ears, not because I'm female. cheers Brianna _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

If I write a parser extension for a tag <foobar>, is it possible for the extension code to obtain the string "foobar", that is, the name of the tag that invoked it? I know how to get the tag body (first argument to the parser function) and the attribute array (2nd argument), but not the tag name itself. Thanks, DanB --------------------- Confidentiality note The information in this email and any attachment may contain confidential and proprietary information of VistaPrint and/or its affiliates and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may cause liability. In case you have received this message due to an error in transmission, please notify the sender immediately and delete this email and any attachment from your system. --------------------- _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

In a single function, branch on the tag name to use the appropriate SqlServer object, and pass it to a single, general function

Jim Wilson writes: require called, right? True, but I am trying to write some highly reusable/maintainable code where the tag name is just input data, since the MediaWiki programming model to "statically map tags to parser functions" doesn't seem optimal for our situation. Here's the scoop. At my company, we have many database servers. For each server, we have a separate wiki tag, <server name here>, that allows adhoc queries to that database server. All these wiki tags have the same implementation, but direct the operation to the named database server. We could have done this instead with a single tag, e.g., <sql server="server1">...</sql>, but for convenience of our wiki users (as well as legacy reasons), we have one tag per server. Right now, whenever we add wiki support for a new database server, we have to modify several pieces of code by hand to add the wiki tag: 1. Create the parser function (very short, just a wrapper that calls a more general function using the specific server's connection string) 2. Create a new setHook call 3. Append the tag name to the $wgExtensionCredits 'description' entry 4. Possibly create a bunch more parser functions & setHook calls in the future, for new purposes This is for EACH server we add. It is a maintenance pain as the number of servers grows, and requests for new kinds of database functionality are growing too. So I want to refactor things to abstract away the servers, make things completely data driven, and stop adding code. In the new model, I simply maintain a collection of "SqlServer" objects that represent the servers. To add support for a new server, I'd just add it to the SqlServer collection and be done. No other code-writing involved. All the above 4 steps go away. But in order to do this, I need to detect the tag name which invoked the extension, so I can do the following: - Get the tag name - Generate all the necessary setHook call(s) - In a single function, branch on the tag name to use the appropriate SqlServer object, and pass it to a single, general function I hope this explanation makes sense. DanB --------------------- Confidentiality note The information in this email and any attachment may contain confidential and proprietary information of VistaPrint and/or its affiliates and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may cause liability. In case you have received this message due to an error in transmission, please notify the sender immediately and delete this email and any attachment from your system. --------------------- _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

It is not about luck! MediaWiki is a wiki software written for Wikipedia, it happens to work for other website too. The main "customer" is still Wikipedia.

Maybe we can add a page somewhere that points to the WMF donation page though.

I think we received "job offers" on the mediawiki-l list, some developers also received private offers to write extensions.