Rosetta Code:Village Pump/Unimplemented tasks: Difference between revisions

no edit summary
(reasoning behind a bot.)
No edit summary
 
(3 intermediate revisions by one other user not shown)
Line 1:
{{Vptopic
|topic=Unimplemented tasks
|summary=Announcement of the unimpl pages, and of ImplSearchBot
}}
=It exists!=
I'm really, ''really'' sorry at how insanely busy the Recent Changes log will be by the time this is done. In other news, I have written a bot that will keep a page of tasks for which each language has not had implementations written for it. The process of creating these pages is very CPU intensive, and spams the heck out of the Recent Changes log, so I don't think I'm going to have the bot run very frequently. Probably once per week. And, yes, it will be getting its own bot account, same as GugaTagFixer. On the bright side, we ''finally'' have these lists! --[[User:Short Circuit|Short Circuit]] 08:07, 16 February 2009 (UTC)
:Interesting! How is one expected to find these pages? Are they automatically linked from the language template? How about a [[:Category:Unimplemented tasks]] to index them all? (I was expecting this kind of feature to be an extension to WikiMedia itself, accessed dynamically as a [[Special:SpecialPages|special page]].) --[[User:IanOsgood|IanOsgood]] 15:43, 16 February 2009 (UTC)
Line 9 ⟶ 14:
::I think there's a wiki variable you can add to [[Template:unimpl_header]] for that. --[[User:Short Circuit|Short Circuit]] 17:38, 16 February 2009 (UTC)
 
=To Bot or Not to Bot?=
'''I think that using bots isn't a good thing, it's better try to use a [[PHP]] Script to display unimplemented tasks, take a look at my code. This using rewrite engine will be awesome.'''--[[User:Guga360|Guga360]] 21:59, 16 February 2009 (UTC)
<syntaxhighlight lang="html">
<lang php>
<?
if (!isset($_GET['lang'])) die("Language not specified.");
Line 63 ⟶ 69:
</body>
</html>
</syntaxhighlight>
</lang>
: There are two main reasons I didn't go with that approach.
:# The intersection is calculated every time the page is viewed, which means two queries for each view. That will fail under loads far lighter than MediaWiki will otherwise normally handle.