21426
FARR Plugins and Aliases / Re: New FARR plugin : FSubScript enable loading of multiple javascript plugins
« Last post by mouser on November 19, 2008, 04:26 PM »ecaradec is right -- the plugins should not do the filtering -- farr can do a smarter job (or else farr should be fired!)
i think it just requires an extra function for me to write that the plugins can call.
Let me explain:
There are two ways that a plugin normall gets called:
1) either because its keyword is typed by the user
2) or what user types matches a regular expression.
in case 1, usually what farr does is automatically filter the results returned by the user based on subsequent words on the search string after the first keyword that matched plugin name.
in case 2, usually you do not want subsequent filtering, since presumably you are catching other text on the line besides just the one keyword at the front.
---
now i think the problem with fsubscript is that the parent fsubscript script basically has to match on the raw string (or by matching .* regex) -- so farr doesnt know how to do subsequent filtering.
so i think what i need to add is a pluginp->set_strvalue("filteron",rest of typed search to filter on)
and then fsubscript can call this function with search words after the first matching keyword.
does that make sense?
i think it just requires an extra function for me to write that the plugins can call.
Let me explain:
There are two ways that a plugin normall gets called:
1) either because its keyword is typed by the user
2) or what user types matches a regular expression.
in case 1, usually what farr does is automatically filter the results returned by the user based on subsequent words on the search string after the first keyword that matched plugin name.
in case 2, usually you do not want subsequent filtering, since presumably you are catching other text on the line besides just the one keyword at the front.
---
now i think the problem with fsubscript is that the parent fsubscript script basically has to match on the raw string (or by matching .* regex) -- so farr doesnt know how to do subsequent filtering.
so i think what i need to add is a pluginp->set_strvalue("filteron",rest of typed search to filter on)
and then fsubscript can call this function with search words after the first matching keyword.
does that make sense?

Recent Posts