Document directory
The reader is most concerned with the reading content rather than the source of the content. In the same image, there are image versions and text versions on the Internet, the reader can automatically find relevant books from the Internet based on users' reading habits (for example, users only want to read picture chapters.
The core value of a reader is to provide a better user experience than a browser:
1. No advertisement, no pop-up window
2. Pre-load according to user habits, no delay in reading
3. Chapter update notification
4. Unified UI and easy reading
5. You can save your favorite books to the open platform and read them on the open platform. For example, save the favorite books to the QQ space.
6. More secure. Based on Silverlight, malicious code is more secure than Html in the parser.
The above functions are not provided by the browser.
Main business process
The core function of the reader is to provide users with a convenient and friendly way to read. The reading process is illustrated in the following section: reading novels by a user: The image section of the immortal legend.
Core business functions
Core features: user-friendly reading.
Non-core features: e-book production, provided as a plug-in.
Core system functions
To provide a friendly reading experience and complete business functions, the reader must support the following system functions.
Core system functions:
Flexible and efficient Html parsing functions. The HTML parsing module supports arbitrary html parsing and can automatically generate xaml or domain objects for parsing results.
You only need to put the custom resolution file in the directory specified by the reader to automatically add resolution sites.
The cache and pre-load mechanisms can meet the requirement of no delay in online reading.
MVVM mode and MEF provide scalability and portability.
The automatic resolution test automatically downloads the new resolution file from the server after the site revision.
URI generation: The target URI can be generated based on the existing URI to reduce one network communication (non-core)
Constraints
Currently, the browser is implemented based on Silverlight. The following problems limit the functionality of the browser. In particular, the problem of Baidu Library has recently stirred up. At the beginning of the design of the reader, the reader simply used the browser, but showed the content from the web in a better way according to reading habits.
Books are not saved to the server and cannot be read through powerful servers. By enhancing the caching and pre-reading functions, you can achieve smooth reading.
Reader development architecture
The reader consists of three parts: Reader Program (UI), Html Parser, and crawler-focused.
Currently, the focus crawler is not implemented, and the novel URLs output in this part are implemented through the configuration file.
Reader UI Architecture
The top UI of the reader architecture adopts the MVVM architecture to facilitate UI adjustment and porting to other platforms.
Function Roadmap
Currently, the reader is the second version (if it is the third version from the very beginning)
1. In the initial version, use the SilverlightToolkitUI and test version.
Http://www.cnblogs.com/bluewater/archive/2010/07/06/1772466.html
2. Version 2, new UI, similar to iPod interface (V1)
Http://www.cnblogs.com/bluewater/archive/2010/12/20/1911769.html
3. Version 3, mainly non-functional improvements
Http://www.cnblogs.com/bluewater/archive/2011/04/07/2007913.html