Jquery UI autocomplete with Ajax: the idiotproof to master full guide

i decided to write this post cuz this thing tool my like an hour or 2 to get, and while looking at my solution i saw i should have got it in 2 seconds, so like other places sometime the examles are just not simple enough, so lets go.

stage 1: idiot proof
i'll do everything from the begining, download jquery ui 1.9.2 from their site. i opened an empty asp.net web app, added the jquery-ui-1.9.2.custom.js and the jquery-1.8.3.js and write html:

<input id="MyTextBox" type="text" />
and then JS:
$(function () {
  $("#MyTextBox").autocomplete({
    source: [ "ariel", "avraham", "aviel", "eliyahu", "eliezer" ]
  });
}); 

and run, thas it u have a working auto complete. now in order to have my array from a request i could just do this:
$.ajax({
  url: "default.aspx/BringMeListFromWebMethod",
  contentType: "application/json; charset=utf-8",
  type: "POST",
  async: false,
  success: function (data) { arr = data.d; }
});
 $("#MyTextBox").autocomplete({  source: arr }); 

of course the BringMeListFromWebMethod is a WebMethod that return the same string[].
for any1 who need some instructions about basics of ajax or WebMehtods:
http://bresleveloper.blogspot.co.il/2012/04/ajax-3-simle-ways.html

but then we want to already do the filtering server side, otherwise whats the point? so in order to make it simple we will use what Jquery UI gives us for free,
$("#MyTextBox").autocomplete({
  source: function (request, response) {
    $.ajax({
      url: http://ws.geonames.org/searchJSON,
      dataType: "jsonp",
      data: { name_startsWith: request.term },
      success: function (data) {
        response($.map(data.geonames, function (item) {
          return { label: item.name }
        }))
      }
    })
  }
}); 

i'll put it up to you to call the right ajax thing for you app and make sure its json, its a problem to use webmethod, easier to make a handler or something and u need to json serialize it.

but still a little overview: the url is a ajax handler that returns a large array in json.
the data sends the request.term, that what you put in the textbox, to the right parameter.
lastly the label:item.name, that creates the list you will see.

join us again in the novice stage here
http://bresleveloper.blogspot.co.il/2013/04/jquery-ui-autocomplete-with-ajax-novice.html

Comments

Post a Comment

Popular posts from this blog

OverTheWire[.com] Natas Walkthrough - JUST HINT, NO SPOILERS

game portal: http://overthewire.org/wargames/natas/ PASSWORDS for each level are stored in /etc/natas_webpass/natasX I made this walkthrough for people like me, i needed some help, but didnt want the spoiler, so here i will give you all the information needed to pass each level, yet not the solution. For levels needed custom web request i made a different post for powershell and javascript  with how-to's, since is a piece of learning for itself, and also for those of us that play at work and have only powershell at their hands. Although its not a complete spoiler there, its quite most of the solution so try yourself 1st. Natas The Natas game is from basic to advances web hacking. Every few levels is about whole new exploitation (with some harder ones doing comeback later), so a lot of learning. If you're new, you're the reason i am writing so much even for the 1st level, just please google EVERY topic you see, since in the following levels i assume you know the ...
Read more

Asp.Net Ending Response options, Response.End() vs CompleteRequest()

this blog is for any1 who get the ThreadAbortException when caling Response.End(), and then tried the other options such as HttpContext.Current.ApplicationInstance.CompleteRequest() and found out that there was no replacement. i'll start with the bottom line: if you want to stop right now your response and send it as is you dont have any other option other than Response.End(), period and it's the right thing to throw that EX in that case. the answer is its because there is the "HTTP pipeline" and the "Asp.Net pipeline", and CompleteRequest() cuts the HTTP pipeline but not the Asp.Net one so everything that is from handlers forwars (including all page events) continues but your part, the asp one, stays in your hands so that no information will be lost, so ur suppose to manage your code currectly, since information lost is really a bad thing, although in most cases we use Response.End() we know what we are losing and we want it. see this short article ab...
Read more

SOLVED The item could not be indexed successfully because the item failed in the indexing subsystem

if you got an error like this The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 04081656-B51B-4DCD-96D4-6DB2D2CEEEE7 ) as well as these: The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Caught exception when preparing generation GID[7]: (Previous generation (last=GID[6], curr=GID[7]) is still active. Cannot open GID[7]); Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 92EB0180-C086-4853-BED8-F4878D9748AD ) the solution for me was to clear configuration cache (PS)  and then restart SP Search Services. THX ...
Read more