I just wanted to add that in the RESTful api I am still getting the data for the more results link but if this gets pulled from the API also I must say I probably wont be too impressed as it most likely will start breaking things or throwing js errors since many (basically all) of my scripts are expecting this data.
Sounds like as it is, I will now have to go back through countless scripts to check each and every one of them that they have an exception check in them for the more results data so this announcement has created the same amount of work for me now anyways. I personally feel (IMHO) that it should be the developers decision if they want it or not as long as it is not negatively impacting Google by having them, they at least could have hidden them by default then and still allowed the people who want to provide it with a means to do so (via css preferably or an extended js argument). Alternatively, I do understand the argument and point that (for the same reason Google only provides 64 results max) is that the majority (or according to Adams post 9,999 out of 10,000) of valid end users would have changed their query or refined it by the time they hit the 8th page of results making the more results after the 8th page un- necessary and the only (main ones) asking for more are almost always for SEO sites which the Google API team has indicated they are not catering to those sites or developers with this API. But, I am pretty sure that if the team does start making breaking and/ or undesirable changes then this API will get the same reputation the Gadgets API has where you are always fixing issues and the API can never be trusted to work from one day to the next or the features/ capabilities to be reliable to use. Which brings up the same developer complaint from the Gadgets developer community (since day one) that Google needs to communicate more with their developer community about making adverse and breaking changes to the API and at very least give them an opportunity to comment or prepare for it prior to the change. I must say though, that I did not see this in the issue tracker where people complained about it then voted and stared it to have it removed, nor have I seen this complaint in this group or in the IRC channel either. Just my $0.02 on this. On Apr 18, 4:10 am, Adam Feldman <[email protected]> wrote: > On Apr 18, 3:01 am, omr <[email protected]> wrote:> Thanks for the > explanation. > > > > ... several developers using the [Custom Search] element > > > ... requested the feature be removed. ... > > > I'm not trying to criticize the decision; but IIRC, wasn't the "More > > Results" link given a unique CSS class -- such that developers could > > have used a "display: none" or "visibility: hidden" rule to hide the > > link? (If API TOU 1.4 or CSE TOS 1.4 would not allow that, perhaps an > > exception could have been given?) ... Just wondering. > > To be honest, most developers wouldn't have bothered or been aware of > it. The element is used on a lot of sites where it's thrown up once > and then the code isn't revisited. It seemed to make sense to change > the default to that use case that made the most sense for the most end- > users (especially in light of the fact that it was almost entirely > unused). > > If we start getting requests to bring it back, that's certainly a > possibility (though no promises, of course). For you, Scotty and > others: Do you feel it's important to have "More results" back? If > so, someone should add it to the issue tracker and report back here > for others to vote it up:http://code.google.com/p/google-ajax-apis/issues/list > > Adam > > > > > > > . > > > > ... anyone who uses the element tied to a Filter CSE > > > can use the .setResultSetSize method with the value of > > > google.search.Search.FILTERED_CSE_RESULTSET to set the > > > element to return up to 10 pages of results, > > > with 10 results per page. > > > That is indeed a helpful feature. (Appropriately, Search Element code > > provided in the Custom Search Engine "Control Panel" interface > > specifies that setting by default.) > > > -- omr > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google AJAX APIs" group. > > To post to this group, send email to > > [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/google-ajax-search-api?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google AJAX APIs" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/google-ajax-search-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en.
