Andrew Dunbar wrote:
2009/1/20 Platonides platonides@gmail.com:
Andrew Dunbar wrote:
Just the couple I needed for checking for and fetching raw articles: /w/index.php?title=...&action=raw /w/api.php?format=json&action=query&titles=...|...&redirects
And what's the point of Firefox retrieving article contents when you're offline?
Err well being able to read articles when you're offline.
But also analysing Wiktionary. Checking whether it had entries for certain words etc.
Then why the API? I'd prefer a graphical interface, not just wikitext into XML. :)
Do you place all articles on the same page using AJAX?
plus an extension which returned a list of languages for which there were articles in an English Wiktionary page
For outside Firefox I also had a Perl CGI version but on my Eee PC that was way more expensive to run
Probably because the perl is interpreted and the extension compiled.
Well Firefox extensions are in JavaScript, also an interpreted language, but the cost of starting up the perl interpreter was expensive, especially doing a few simultaneous operations.
I thought it was a binary one. Firefox extensions can be in javascript or XPCOM. Still, it caches the opcodes and the trunk version is even faster.
The use case I would deem more common would be to access page contents from outside for processing, eg. to show it on a page, as http://wiki-web.es/mediawiki-offline-reader/
Perhaps. I wasn't making something for the more common use case, I was making something I had a use for (-:
Well, showing mediawiki pages is exactly what that app does. It's just that I wouldn't use the dumps into offline Firefox to feed the API. Seems you have different uses (or perhaps I have completed misunderstood it :)