Nice to hear. Thanks mouser. :)

You could try one of these two alternatives, see how you like them:

1. put the long-winded text, i.e. the full description in the FARR item group name field. This is the smaller text underneath the main caption. In FARR's display option it's the column called 'Location'. I could imagine you already tried that.

2. Do what you already tried, i.e. use this as the item's path:

fooscript base64.encode ;; category: codec ;; this will encode the currently-selected text using base64 encoding <<<--- FARR status bar

then, when the user hits TAB on one of the items the complete path with your description will be copied into the FARR search box and onSearchBegin will be called again. In onSearchBegin parse for one of your delimiters and if you find one, start a new search with setStrValue("setsearch", yourPathWithoutDescription). It might be a bit annoying that the whole description appears before it is cleared by your new search. Not sure if it will actually work, you'll have to try.

That's obviously not what I wanted to hear ;). I understand though that you have long term plans with FARR and that they don't correspond with my immediate needs. In context with these long term plans my suggestions might even seem to be wasted time. What I tried to suggest was stuff which I thought would be fairly easy to implement (well, probably not point 2, and I can obviously only guess as I have never seen any FARR source code) but would offer new possibilities for plugins immediately.

To be honest, I'm actually pretty happy with list mode, even as it is now. I think I have shown with FarrMilk that it can already now be used to implement quite powerful plugins (that's what I hope at least). I can see that with the planned grid mode, much more would be possible. I'm just not sure if it's worth the effort when with (what I think) much less effort it would be possible to sufficiently improve what is already there.

These ideas and suggestions are obviously from my very limited view, which stems from my personal requirements of what I think FARR should do for me (besides launching applications of course). The amazing variety of existing FARR plugins shows me though that the public requirements are much broader than my own. The intent of this thread was to show me (and you in the end) how important certain features that would be relevant to me right now would be to others willing to extend FARR's functionality. Well, I think I got my answer.