Opera support for Google Instant: ‘Shortly’
On Wednesday, when the world’s dominant search company launched the Google Instant search-as-you-type service, a technically savvy section of Web users were left out: those who prefer the Opera browser.
But they won’t be for long, Google said Thursday. “We hope to support Opera shortly after launch,” the company said in a statement.
Google Instant works on newer versions of the four most widely used browsers: Google’s Chrome version 5 and later, Firefox version 3 and later, Safari for Mac version 5, and Internet Explorer 8, the company said. “We encourage people to upgrade to the latest version of their favorite browser,” Google added, expressing a sentiment shared by innumerable Web developers.
In the meantime, Opera’s Bruce Lawson offered quick advice on enabling Google Instant in Opera by telling the browser to masquerade as Firefox at Google. The advice and Google Instant worked for me on both Mac OS X and Windows 7, though the left edge of the search box was missing.
Opera users got a preview of coming disappointment with this week’s dynamic Google Doodles–the rejiggered Google logos that appear on the company’s home page. Opera users didn’t see either Tuesday’s doodle, in which Google’s logo was rendered in colored circles that evaded the user’s mouse, or Wednesday’s, in which letters of Google’s logo written in gray letters turned colored as a person typed in search terms. Again, faking out Google by using Firefox’s identity enabled the special effects.
Google vice president Marissa Mayer introduces Google Instant. (Credit: James Martin/CNET)
And the effects weren’t even cutting-edge by some measures. Google is on a tear to develop and promote new-era Web technologies for elaborate, graphically rich applications, and has been promoting elaborate demonstrations accordingly. But the mouse-evading circles doodle used fairly conventional, pre-HTML5-era technologies, according to one discussion of the doodle on an HTML5 mailing list.
Those who are curious can check demonstrations using new-fangled approaches: Robin Berjon’s bouncy balls in SVG (Scalable Vector Graphics) or Rob Hawkes’ Canvas version. (In neither do the balls eventually lose their mouse pointer aversion, as in Google’s original, but you get the point.) Also worth a peek is Ian Devlin’s “AreGooglesBouncingBallsHTML5.com site.
What did require newer technology was Google Instant itself. Using it, Google has to deliver five to seven times the number of search pages as is needed for a typical search, and Google already serves more than a billion such pages per day, according to a blog post Thursday by Google Instant engineer Ben Gomes. He shared a little detail on how the company cached data in a new way, kept track of users’ search activity so it didn’t have to retrieve the same search data multiple times, and tailored the JavaScript programming on the results page to match the new service.
Read more: http://news.cnet.com/8301-30685_3-20016008-264.html#ixzz0zE8zDM61
Incoming search terms for the article:
- google instant opera (35)
Share This
About the author
I would not make the second class CirclesComponent. I would just use the Ellipse2D class to make 2 circles inside your first class.
Ellipse2D circle1; // or bigCircle.
Ellipse2D circle2; // or smallCircle.
Then in the paintComponent method always draw circle1, as you make this one.
First up, check if circle1 is null, if it is, make it how you need to with the size, etc.
If it is not null, you do not need to create it.
Then display it as you know.
Then check if circle2 is null.
If it is, ask the user to input the dimensions for it.
If it is not null, the user has already put in the dimensions.
Then check if they intersects using the intersects method of the Ellipse2D class. The API for this class is here:
I would also change the way you are doing the first (and only) class, you should make the JFrame etc in the constructor, and in the paintComponent only paint the components.
In the constructor, you will have to set up the big circle. You may also want to get the input for the small circle. Then in painComponent, you paint the big circle, and check if the circles intersect and paint the color that you need.