<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: form input suggestions (google suggest) in Security</title>
    <link>https://community.splunk.com/t5/Security/form-input-suggestions-google-suggest/m-p/13264#M283</link>
    <description>&lt;P&gt;Not simple.  jquery will already be there, courtesy of splunk.  And I believe only 'application.js' is the only filename it will pick up.  No there is essentially no documentation and no examples cause we havent opened up this layer to anyone yet (lack of time and resources)&lt;/P&gt;</description>
    <pubDate>Thu, 13 May 2010 23:33:40 GMT</pubDate>
    <dc:creator>sideview</dc:creator>
    <dc:date>2010-05-13T23:33:40Z</dc:date>
    <item>
      <title>form input suggestions (google suggest)</title>
      <link>https://community.splunk.com/t5/Security/form-input-suggestions-google-suggest/m-p/13260#M279</link>
      <description>&lt;P&gt;So i've set up a form dashboard to filter a query displayed in a table.&lt;/P&gt;

&lt;P&gt;Is there any way to get a "google suggest" type feature for each of the inputs?  like all possible values from the data.&lt;/P&gt;

&lt;P&gt;i saw this post and it works for dropdowns. i'd love to figure out how to populate a suggestion box under a text input or something.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://answers.splunk.com/questions/1891/populate-dropdown-form-field-values-from-a-file" rel="nofollow"&gt;http://answers.splunk.com/questions/1891/populate-dropdown-form-field-values-from-a-file&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;if there is a more hacky approach to custom stuff... i am interested as well.&lt;/P&gt;

&lt;P&gt;TIA, 
   Kirby&lt;/P&gt;</description>
      <pubDate>Tue, 11 May 2010 23:06:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/form-input-suggestions-google-suggest/m-p/13260#M279</guid>
      <dc:creator>hiddenkirby</dc:creator>
      <dc:date>2010-05-11T23:06:22Z</dc:date>
    </item>
    <item>
      <title>Re: form input suggestions (google suggest)</title>
      <link>https://community.splunk.com/t5/Security/form-input-suggestions-google-suggest/m-p/13261#M280</link>
      <description>&lt;P&gt;There's a typeahead endpoint that can get suggested search tokens from the index,   but there is no module that uses that endpoint besides the big SearchBar module. &lt;/P&gt;

&lt;P&gt;As for your question about hacky approaches to custom stuff,  disclaimer disclaimer, but it is technically possible to alter the behaviour of any method on any of the module classes from a custom application.js file in your app.&lt;/P&gt;

&lt;P&gt;There are three generic text-input modules, FieldSearch, ExtendedFieldSearch and TextSetting. 
This one would give you the ability to "do something" when there's a keydown event on a FieldSearch module. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;if (Splunk.Module.FieldSearch) {
    Splunk.Module.FieldSearch = $.klass(Splunk.Module.FieldSearch, {
        _onKeyDown: function($super, evt) {
            var retVal = $super(result);
            //do something
            return retVal;
        }
    });
}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;in this case the something would be get the text content of the input, get the character being added in, make an appropriate jquery request to the typeahead endpoint, binding a js callback function that takes the typeahead data returned and creates a div to put it in and lines it up etc etc.. but that's a lotta handwaving. caveat lector. &lt;/P&gt;</description>
      <pubDate>Thu, 13 May 2010 11:47:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/form-input-suggestions-google-suggest/m-p/13261#M280</guid>
      <dc:creator>sideview</dc:creator>
      <dc:date>2010-05-13T11:47:59Z</dc:date>
    </item>
    <item>
      <title>Re: form input suggestions (google suggest)</title>
      <link>https://community.splunk.com/t5/Security/form-input-suggestions-google-suggest/m-p/13262#M281</link>
      <description>&lt;P&gt;This is great. I would like to accomplish this. Any good documentation on using custom.js or any jquery examples? I don't see anything in the ui-examples app.&lt;/P&gt;</description>
      <pubDate>Thu, 13 May 2010 22:01:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/form-input-suggestions-google-suggest/m-p/13262#M281</guid>
      <dc:creator>hiddenkirby</dc:creator>
      <dc:date>2010-05-13T22:01:01Z</dc:date>
    </item>
    <item>
      <title>Re: form input suggestions (google suggest)</title>
      <link>https://community.splunk.com/t5/Security/form-input-suggestions-google-suggest/m-p/13263#M282</link>
      <description>&lt;P&gt;Simple as placing jquery.js and mycustom.js in the appserver/static folder?   how does it tie into splunk's modules?&lt;/P&gt;</description>
      <pubDate>Thu, 13 May 2010 22:02:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/form-input-suggestions-google-suggest/m-p/13263#M282</guid>
      <dc:creator>hiddenkirby</dc:creator>
      <dc:date>2010-05-13T22:02:10Z</dc:date>
    </item>
    <item>
      <title>Re: form input suggestions (google suggest)</title>
      <link>https://community.splunk.com/t5/Security/form-input-suggestions-google-suggest/m-p/13264#M283</link>
      <description>&lt;P&gt;Not simple.  jquery will already be there, courtesy of splunk.  And I believe only 'application.js' is the only filename it will pick up.  No there is essentially no documentation and no examples cause we havent opened up this layer to anyone yet (lack of time and resources)&lt;/P&gt;</description>
      <pubDate>Thu, 13 May 2010 23:33:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/form-input-suggestions-google-suggest/m-p/13264#M283</guid>
      <dc:creator>sideview</dc:creator>
      <dc:date>2010-05-13T23:33:40Z</dc:date>
    </item>
  </channel>
</rss>

