Bing dictionary UWP version-Development Summary, uwp dictionary Development Summary

Bing dictionary UWP version-Development Summary, uwp dictionary Development Summary
Summary

Bing dictionary UWP has been available for 2 weeks! I believe many users have already experienced it! Thanks to the brand new and powerful APIs of Win10, the performance and UI experience of the new dictionary version have been greatly improved. Today, I will share with you the story of UWP DEVELOPMENT IN THE Bing dictionary. In addition, you are welcome to experience our app and provide us with valuable comments!

Download link:

Https://www.microsoft.com/zh-cn/store/apps/%e5%be% AE %e8%bd%af%e5%bf%85%e5%ba%94%e8%af%8d%e5%85%b8win10%e7%89%88/9nblggh63sw0

First impression

Let's take a look at two photos of our app. Do you think the interface is refreshing? Our UWP is applicable to screens of various sizes and windows of various sizes. In a narrow screen or window, we use the hamburger key and SpliteView as the page switch control, while on a wide screen we use Tabs, in this way, the display of valid content on the screen is more reasonable, and the display meets the windows app design standards. The content display varies with the size of windows. Have you noticed this?

Development story

Let's take a look at the dictionary. Next, let's talk about the development of the Bing dictionary. The Solution of the Bing dictionary is mainly composed of the following core projects:

Fundamental mainly includes the Schema, App Settings, Constants, and some auxiliary tools of dictionary data. Storage, as the name suggests, encapsulates the dictionary Storage interface; Query Engine, it is the core of the Word query logic. Word List implements the native function, and Adaptive UI is the page display we see.

Storage

Storage can be divided into File, Dictionary, and Cache based on different requirements. File Manager implements operations on local files, including storage and reading. In our Dictionary, a local Dictionary is encapsulated to facilitate offline word query. The data in the Dictionary is stored in the sqlite database, and the Dictionary Manager is mainly used for local Dictionary operations, including query and record history. Cache Manager is mainly used to manage the Cache data that users access the network and store it as key-value pairs. The Cache itself is divided into two layers: Disk Cache and Memory Cache. Disk Cache uses sqlite storage in storage to improve query efficiency. We know that the memory access speed is much higher than the Disk access speed. Therefore, based on the Disk Cache, we also have a layer of Memory Cache. At the same time, Memory Cache is based on the LRU replacement principle and does not occupy too much Memory overhead, making queries faster.

Query Engine

Word query is the most important part of our dictionary, including the query of many contents, it can be divided into local vocabulary queries, online vocabulary queries, sentence queries, audio and video queries, and word auto-completion queries. Query in the Search box and display the results in the Result Page. This process is the most important part of the dictionary app. In this process, there are multiple Query steps, and the query Engine only exposes one Query interface. The results of multiple queries are reported to the IQueryEngineListener of the listening query respectively, instead of giving feedback after obtaining all the data, the user will have a continuous and smooth experience during word search.

Word List

The logic of the source text is relatively simple. It is basically the query of several tables in the sqlite database, but the performance has been greatly improved compared with the storage structure of the previous version of xml.

Adaptive UI

The UI Section has already been introduced in the beginning of the article. Here we want to say that the Page we see is not completed by a Page. Specifically, in every Page of the app, the pages that reflect our sights are composed of two pages, as shown in:

The outermost page is called the Main Frame, which includes the hamburger key, Split View, Tabs, and Query Bar to switch the app page. The Section framed in red is used to display the app Content page, which is called Content Frame. This makes the page logic clearer and easier to maintain. For the implementation of nested pages, please refer to another blog: UWP Development notes-Implementation of nested pages (http://www.cnblogs.com/ms-uap/p/4860121.html ).

In the page adaptation, VisualStateManager, provides us with a powerful interface, the specific response-style UI development method, please refer to Windows10 UWP development-responsive design (http://www.cnblogs.com/ms-uap/p/4536459.html ).

This is a general structure of our app.

Summary

Since the App was launched, we have received a lot of feedback from users. Thank you for your comments. We will pay more attention to them and constantly update our products based on your feedback. Because it is the first version, there will be fewer features, and we will gradually add the features such as the synchronization of original tokens and word selection to our products. At the same time, we sincerely hope to receive your praise. Thank you!

 

Download the APP:

Https://www.microsoft.com/zh-cn/store/apps/%e5%be% AE %e8%bd%af%e5%bf%85%e5%ba%94%e8%af%8d%e5%85%b8win10%e7%89%88/9nblggh63sw0