Pacman is 30 years old! Yeay. It's playable on Google for a while, but suspiciously easy to beat. For once I won. :p
In the meantime, the official google at US launched a search via SSL. Don't know what it means for our searches though...
Saturday, May 22, 2010
Friday, May 7, 2010
Google Chrome
Posted by
餅餅
at
10:54:00 AM
Oh, have I failed to mention that Google Chrome is back in business on my laptop? No, I didn't solve the SCIM problem. The story goes like this:
When I first tried Google Chrome for LINUX, I was unable to have Chinese input in Chrome, and Chrome causes SCIM (the Input Method (IM) that I was using) to entirely crash and not able to load. Then I removed Chrome and SCIM worked OK again. Then I installed Opera, which version 10.52 was supposedly announced, but yet to be available for LINUX. Opera 10.51 did not make SCIM crash, but there's no input in Opera itself. So help was seek from Google, the almighty (yea, I'm a fangirl, so?). Apparently, SCIM does not support well the browsers (or any application, for that fact) that uses QT. Ah, so no wonder I had problems with frozen input on my instant messenger that uses QT.
Then comes more googling and a surprise (ta-daa): Ubuntu Karmic Koala ships with iBus, an IM recommended by net users. I swear if you never poked around in the Administration tab, you will never know of its existance. iBus is apparently a build-in IM for non-ASCII characters! So, I removed SCIM, totally! Yea, well, switching over was a bit hard. The native iBus IM only inputs one character at a time and it does not input Chinese punctuations, so it was a pain. But then, more googling brings me to install the ibus-pinyin packacge, that supports both the function missing in native iBus. Cool! And so, it's proven again that Google can do anything.
Ah, back to Google Chrome... With the IM problem solved, I was happy with Opera for a few weeks, until it starts being weighted down by reasons unknown to me. It started to startup really slooowly and started to load pages slower too. And then, one fine morning I had a lightbulb: if SCIM is out of the way, then Google Chrome should be a breeze, right? Except I have to test if it works with iBus. So I reinstalled Google Chrome, and had aptitute look for an update (and there was one so I installed it), and then viola! Google Chrome is back in action on my laptop and I'm one happy user!
All the apologies to Google for previously damning Chrome. And more to readers (if there were any out there) for an unexpectedly long post on Cookie-googles.
When I first tried Google Chrome for LINUX, I was unable to have Chinese input in Chrome, and Chrome causes SCIM (the Input Method (IM) that I was using) to entirely crash and not able to load. Then I removed Chrome and SCIM worked OK again. Then I installed Opera, which version 10.52 was supposedly announced, but yet to be available for LINUX. Opera 10.51 did not make SCIM crash, but there's no input in Opera itself. So help was seek from Google, the almighty (yea, I'm a fangirl, so?). Apparently, SCIM does not support well the browsers (or any application, for that fact) that uses QT. Ah, so no wonder I had problems with frozen input on my instant messenger that uses QT.
Then comes more googling and a surprise (ta-daa): Ubuntu Karmic Koala ships with iBus, an IM recommended by net users. I swear if you never poked around in the Administration tab, you will never know of its existance. iBus is apparently a build-in IM for non-ASCII characters! So, I removed SCIM, totally! Yea, well, switching over was a bit hard. The native iBus IM only inputs one character at a time and it does not input Chinese punctuations, so it was a pain. But then, more googling brings me to install the ibus-pinyin packacge, that supports both the function missing in native iBus. Cool! And so, it's proven again that Google can do anything.
Ah, back to Google Chrome... With the IM problem solved, I was happy with Opera for a few weeks, until it starts being weighted down by reasons unknown to me. It started to startup really slooowly and started to load pages slower too. And then, one fine morning I had a lightbulb: if SCIM is out of the way, then Google Chrome should be a breeze, right? Except I have to test if it works with iBus. So I reinstalled Google Chrome, and had aptitute look for an update (and there was one so I installed it), and then viola! Google Chrome is back in action on my laptop and I'm one happy user!
All the apologies to Google for previously damning Chrome. And more to readers (if there were any out there) for an unexpectedly long post on Cookie-googles.
Subscribe to:
Posts (Atom)