Jeff, Thanks again for your helpful example.
As for your last post, I've found the code for using CSE on two pages via an iframe very simple and straightforward: just a few lines of < form > for our home page and a simple < iframe > on our results page, so I don't think it makes it more complicated for web developers. And for the user I think it's more intuitive to enter a search on a home page and then land on a results page, the way they/we do on Google (or Google Toolbar, via any page on the Web). Before you gave your example, to use some cool Google AJAX API it would have to be on a Search page that would just be linked from the home page, so a user would have to click "Search" and then search, rather than just entering a search on the home page, which is less seamless. So I do think hooking up some of those AJAX search features with a two-page option is very useful. Speaking of which: As I posted above, I can't get your example to draw tabbed results. Is there an easy way to do that? Thanks, Nathan On Mar 3, 4:48 pm, "Jeff S (Google)" <j...@google.com> wrote: > Hi omr, > > Good questions. I think one of the challenges with a two page approach > like this is that it requires more work on the web developer's part > than an all-in-one-page-ajax solution. You would need to wire up page > 1 to send the user to page 2. One of the things that I think our users > like about the custom search control is that it provides the results > to the end user without taking them off of the current page. For the > people who do want to user to go to another page, they are free to > build their own solutions as I've done. > > Happy coding, > > Jeff > > On Mar 1, 5:14 pm, omr <omr99...@yahoo.com> wrote: > > > Thanks Jeff for posting that example. > > > In the Custom Search forum, some Custom Search Engine users have > > requested such functionality since last year. So I had considered > > posting essentially the same kind of solution that you've suggested > > today. But I hesitated, because I wasn't quite certain if such an > > implementation was permitted. > > > If such an implementation is permissible for use with CSEs, then I > > wonder why such requested functionality has never before been > > officially provided or documented for use with the AJAX Search API- > > based Custom Search Element. > > > For years, Custom Search Engines have provided an option to host CSE > > results within an Iframe on a separate results-page. That > > implementation (which has some IMO significant known issues and > > limitations, discussed many times in the current and archived CSE > > forums) doesn't use the AJAX Search API. > > > Given the longtime existence of that option, and the desire for a > > better alternative, I was disappointed to see that the AJAX Search API- > > based Custom Search Element (using the Custom Search Control), > > introduced last year, only supports (in its official implementations > > and documentation) a single page, not a separate results-page. > > > So for the past few months I have been wondering why the CSE folks > > chose not to provide a separate results-page option for the Custom > > Search Element, using an implementation similar to what you have shown > > in your example. > > > -- 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 google-ajax-search-...@googlegroups.com. To unsubscribe from this group, send email to google-ajax-search-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en.
