我不知道您是否已经测试过 Google IO 应用程序,但有一个很酷的功能,可以显示包括 Google IO 主题标签在内的所有推文。
我真的很想为我的用户提供相同的功能。
我可以使用 API 做类似的事情,但我必须创建一个自定义列表视图,解析 XML/JSON 提要,这非常复杂! 当然,这个列表不会自动更新并且是实时推送。
在应用程序中,我刚刚看到,当我关闭wifi时,这确实是一个具有以下网址的网络视图:
http://www.google.com/search?%20tbs=mbl%3A1&hl =en&source=hp&biw=1170&bih=668&q=%23io2011&btnG=Search
这是应用程序的屏幕截图和浏览器中的相同网址
高分辨率图片:http://cl.ly/3q1r0c2J3H163E3G2p2X
但是在网络视图中使用此网址仅显示谷歌搜索,并且不提供相同的功能。
我知道这个应用程序肯定会开源,但我对谷歌承诺的“未来几天内”非常持否定态度。
我们仍在等待 Twitter 应用程序源代码!
I don't know if you already tested the Google IO application, but there is a cool feature displaying all the tweets including Google IO hashtags.
I really would like to offer the same feature to my users.
I can do something similar using the API, but I would have to create a custom listview, parsing XML/JSON feeds and that's quite overcomplicated! and of course this list will not update automatically and be a livefeed.
In the application, I have just seen that when I turn off wifi, This is indeed a webview with this url:
http://www.google.com/search?%20tbs=mbl%3A1&hl=en&source=hp&biw=1170&bih=668&q=%23io2011&btnG=Search
Here is a screenshot of the app and the same url in the browser
High resolution picture: http://cl.ly/3q1r0c2J3H163E3G2p2X
But using this url in a webview display only a google search, and does not offer same feature.
I know this app will certainly be opensources, but i am so negative about "within next days" that google promise.
We are still waiting for the Twitter app source code!
发布评论
评论(2)
如果您等到会议结束后,您将在此处。您还可以在那里找到去年应用程序的源代码。
更新:
刚刚查看了源代码,你几乎是对的。这是一个具有以下网址的网络视图:http://www.google.com/search?tbs=mbl%3A1&hl=en&source=hp&biw=1170&bih=668&q=%23io2011&btnG=Search 所以看起来你可能不小心把 %20 放在那里了。
代码:
If you wait 'til after the conference is over, you'll find the source code for the app here. You'll also find last year's application's source code there.
Update:
Just viewed the source code, and you're almost right. It's a webview with this URL: http://www.google.com/search?tbs=mbl%3A1&hl=en&source=hp&biw=1170&bih=668&q=%23io2011&btnG=Search so it just seems you put %20 in there by accident maybe.
Code:
可能是通过带有限制的 Loaders API 实现的。
也在焦急地等待源码。
Probably implemented with Loaders API with throttling.
Impatiently waiting for source code as well.