2009/5/6 Chad <[email protected]>: > On Tue, May 5, 2009 at 2:58 PM, Brion Vibber <[email protected]> wrote: >> El 5/5/09 10:57 PM, Chad escribió: >>> On that note and similar, I had been thinking about just this >>> same issue recently. >>> >>> Rather than a new API module (which would be redundant, >>> as Roan points out), what if we added some new Ajax >>> functions? Then JS has access to messages, but we're not >>> relying on custom Http requests to the API to get them. >> >> What do you mean by "new Ajax functions"? If you mean the godawful sajax >> interface, then it should die and be buried and forgotten. >> >> -- brion >> >> _______________________________________________ >> Mediawiki-api mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/mediawiki-api >> > > Whatever the interface, I was more interested in the end result: > ability to get localized messages via JS, and without having to > request them by hand from the API.
I have some Ajax functions to emulate getMsg and a couple of variants. But it's from before API.php and needed two calls for some things: http://en.wiktionary.org/wiki/User:Hippietrail/wfMsgCentre.js Andrew Dunbar (hippietrail) > -Chad > > _______________________________________________ > Mediawiki-api mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/mediawiki-api > -- http://wiktionarydev.leuksman.com http://linguaphile.sf.net _______________________________________________ Mediawiki-api mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mediawiki-api
