If you run into a situation where the preview you want is not available as anything selectable in the result-page, you can (provided you run a very recent development version) supply a function to preview instead of a string selector, and this will get a single argument, namely the container of the entire result – this of course means that it will only work if you provide a container that groups the result-data. I only just recently pushed this feature, so it is largely untested – expect bugs and changes to the way it works in the future…

@harmen it looks to me like you are using the parser parameter as it is described in the above document, however, since then it has changed a lot – and most of those changes are described in the two following articles on this blog (there are other changes too though, but none should break anything – they are all just added features)

Now, urbandictionary is not an ideal place to start when you want to learn, because their markup does not group result-data (which would otherwise make parsing much more reliable), and moreover, it’s not really a search page, so the fact that no result is less than ideal (activating a result will get you a page load error)

Still, for the preview alone, this will do what you want:
CmdUtils.makeSearchCommand({
name: “urbandictionary”,
url: “http://www.urbandictionary.com/define.php?term={QUERY}”,
parser: {title: “td.word”, preview: “td.text”}
});


CmdUtils.makeSearchCommand({
name: "urbandictionary",
url: "http://www.urbandictionary.com/define.php?term={QUERY}",
icon: "http://www.urbandictionary.com/favicon.ico",
parser: {container: "tbody",
title: "td.index",
preview: "td.definition"},
description: "Searches http://www.urbandictionary.com"
});


but I cannot get what I expect :-/
Some tips? I really need to understand how to create GET/POST search commands that use preview. Thanks

thanks.
gilad.

@Alberto Santini
POST would indeed be a good idea, and there’s really no reason not to include it – in fact I’ve just written the code needed to do this, only problem is that we depend on CmdUtils.previewGet and there’s no POST equivalent (yet)

On a side note, as I said in the article: this was very recently added, so the parser argument will first be supported in 0.2pre14 and 0.1.7 – execute is (untill the POST-support lands) unaffected.