If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

google maps and twitter geocoder hash tag support

I am currently using this tutorial by MARCIN DZIEWULSKI to create an "INTERACTIVE GOOGLE MAP USING THE TWITTER API" ( http://tympanus.net/codrops/2011/04/...ve-google-map/ ), however i would like to expand on this tutorial by providing twitter hash (#) support. I would like to do this by placing a input field that when submitted will retrieve the users profile pic, last five tweets, and placement on the google map.

Can anyone point me to a tutorial or provided direction on how i can accomplish this task?

Hi Xelawho - Very cool!!! Thanks again! If I wanted to leave the users location on the map after searching for another user how would i go about doing that? so in other words can i leave the searched users on the map?

This works perfect. Certain aspects of the tutorial i used was unclear would you be able to elaborate of the code when you get a moment? You are a terrific programmer. What books and tutorials have you read and currently use? Thanks again.

you're very kind. I have never read a book or taken a tutorial on javascript. I just learn by doing stuff, and seeing how other people do it. I have a soft spot for google maps because that's how I started writing javascript.

Most of the changes that I made to that code were taking out things that were unnecessary or were getting in the way. The biggest change I made was to push the markers onto an array, here:

Code:

gmarkers.push(marker);

That was mostly to do with a thing called function closure that in plain terms means that when you click a marker or the info bar at the bottom the code knows which information to put into the infowindow and where to open it up. That's also why I added the addList function to the code - it's a simple workaround to get a number (in this case the length of the gmarkers array at the time that the marker was created) and "bind" that number to the click listener for the marker. The original code didn't work with one infowindow, but rather a whole lot of hidden elements, so that was probably the biggest change.

The rest of the code is pretty much how the guy wrote it - it seemed to work ok so I didn't look at it too much, but if there's anything that is confusing you I will see if I can explain it.