150
edits
Labs/Ubiquity/Parser 2 API Conversion Tutorial: Difference between revisions
Jump to navigation
Jump to search
Labs/Ubiquity/Parser 2 API Conversion Tutorial (view source)
Revision as of 00:30, 11 July 2009
, 11 July 2009→Supporting both Parser 1 and Parser 2 in Your Command Feed
Heatherpedia (talk | contribs) (→Supporting both Parser 1 and Parser 2 in Your Command Feed: changed if statement to support all parser 1 versions) |
Heatherpedia (talk | contribs) |
||
| Line 25: | Line 25: | ||
There is a property added to the Command API that allows you to present different commands to clients running Parser 1 and Parser 2, called CmdUtils.parserVersion. A command can provide different options to CmdUtils.CreateCommand() and behave differently depending on this value, allowing a single command feed to cater to whatever parser the user is using. | There is a property added to the Command API that allows you to present different commands to clients running Parser 1 and Parser 2, called CmdUtils.parserVersion. A command can provide different options to CmdUtils.CreateCommand() and behave differently depending on this value, allowing a single command feed to cater to whatever parser the user is using. | ||
if ( | if (CmdUtils.parserVersion == 2) | ||
//parser 2 command here | |||
else | |||
//parser 1 command here | //parser 1 command here | ||
== Converting your command == | == Converting your command == | ||