Xamarin Android builds its own blog Park app (2)

Good embarrassment, after four months to write the second article, I am embarrassed. This procrastination is so embarrassing, mom-egg!

For those of you who are waiting for the sequel to say Sound sorry!

The following begins the text:

Complete the function:

1. Paging Get home article

2. Pages to get the essence of the article

3. Paging for news

4. Pagination for Knowledge Base articles

5. Blog Park account login, get favorite articles, my blog

6. Article comments

When writing the first article, that time the app interface is called the Blog Park Public WCF interface, a lot of features are limited, there are many inconvenient. I see the official iOS version of the blog park, I use fiddler listening to the next request address, found that the domain name is api.cnblogs.com beginning. Then the surprise came, unexpectedly have Webapi interface. This is much more convenient than the open WCF interface.

WCF Interface Address Http://wcf.open.cnblogs.com/blog/help,http://wcf.open.cnblogs.com/news/help

One is blog-related, one is news-related, less functional, no WEBAPI to provide more. Careful analysis of the next WEBAPI interface address, mom eggs, each request is brought with a token, and this token will expire. What to do, I was wondering if you can apply to the blog park's large application interface call permission, with a disturbed mood to try the next. Originally thought that the big will not bother me, after all, like me this kind of small rookie too many. The result after a few days unexpectedly return mail, let me flattered ah, hurriedly with Thanksgiving letter to greatly back an e-mail.

And then the next success, here Special thanks!

Xamarin Android builds its own blog Park app (2)