change some code to more batter.

To solve cold-start prob, we calculate time based on counted words.

However it is natural that different user spends different time while reading the same article.
So, updating expected reading time based on individual's readability is important, I think.

@leesera or @Csoyee

If user clicks "finish reading" button on the top of the contentView, the signal will be reflected on DB
@juung

• total time using the app
• the most frequent time using the app
• show the number of read pages

• Go back to the ListActivity with renewed recommendation lists?
• Go back to the ListActivity with original lists except read pages?
• Go back to the MainActivity that rewrite spare time?

to motivate user

@leesera

list view design modify

• how about saving wordCount in DB when bring urls from Feedly?
  Unless, for all unread pages, Crawler is called, get wordCount, calculate expected reading time and show chosen list.

issue
to get wordCount, Crawler should be used.
(It is used twice, then.)

When list up contents, it took quite a lot time.

I think it's because using crawler for all new items, so we need to think how to use Crawler efficiently.

contentview with translating option

@juung

Current database get function doesn't bring imgUrl. @sunju0123

@sunju0123