On Sat, Jul 10, 2010 at 8:44 PM, Chris Marshall <[email protected]> wrote: >>> I don't need to know by person, just the aggregate >>> sequences of searches. Even the sequence of topics >>> would be a useful for this purpose. If we know that >>> this was a common search sequence: >>> >>> xxx -> yyy -> zzz -> tada! >>> >>> That could give us ideas where the docs and completion >>> features could be modified to enhance the PDL experience... > > I'm not a web programmer but it would seem that a simple > wrapper around the call to google search could save the > words searched for and the return URLs from the results, > say the first page worth along with a session ID.
Here is the JS code from Google: <script src="http://www.google.com/jsapi"; type="text/javascript"></script> <script type="text/javascript"> google.load('search', '1', {language : 'en'}); google.setOnLoadCallback(function() { var customSearchControl = new google.search.CustomSearchControl('005624475199589227813:0cr_qvao0qc'); customSearchControl.setResultSetSize(google.search.Search.FILTERED_CSE_RESULTSET); var options = new google.search.DrawOptions(); options.setSearchFormRoot('cse-search-form'); options.setAutoComplete(true); customSearchControl.draw('cse', options); }, true); </script> If you see a way to add "a simple wrapper around the call to Google" let me know. If you scan the code you'll see that I never call Google directly. All that behaviour is provided by Google's ajax library. That is as it should be. Setting up series of event handlers and reacting to events is precisely the sort of hassle that you'd expect the library to do for you. Daniel. -- No trees were killed in the generation of this message. A large number of electrons were, however, severely inconvenienced. _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
