-
Notifications
You must be signed in to change notification settings - Fork 2
Release Notes 1.1.0
Version 1.1.0 introduces a local SQLite database and fulltext searching.
October 4, 2011
-
Local SQLite database The SQLite database from the main Dubsar server is now deployed with the iOS applications. Except for the Word of the Day and the FAQ, all data content is now local.
-
Support for fulltext searching The database includes an FTS3 virtual table that allows fast fulltext searching, in the vein of most search engines. All searching is now case-insensitive. Results include anything that contains the search terms as discrete terms. The asterisk (*) matches any non-whitespace string, including the empty string. Certain operators like OR may be included in all uppercase, e.g., "law OR order." Results are sorted in ASCII order, with exact matches sorted to the top.
-
No more match case switch on the iPad Now that all searching is case-insensitive, this has been removed.
-
Fixed occasional positioning glitch on rotation Issue 21 This was actually fixed in version 1.0.1, but since it occurred sporadically, it was not reported closed right away. It has not been observed since that version was released.
-
Fixed inaccurate descriptions in Synset views Issue 41 Sample Sentences in Synset views are now simply labeled, "examples of usage."
Build 1.1.0.8 was released to the App Store.
See Dubsar's full current list of open issues at https://github.com/jdee/dubsar_ios/issues.
-
iPad autocompleter popovers slightly too small in landscape after keyboard disappears Issue 9 The server can return up to 10 autocompletion responses. The table views are sized for 10 rows in both orientations. In landscape orientation, with the keyboard present, the popovers are shortened to the available room, having only about seven rows. After the keyboard disappears, the popovers are restored to the correct size. If they first appear in landscape mode, once the keyboard vanishes, they will be a little too short, having only nine complete rows and a fraction of a tenth.
-
Word of the Day can be unresponsive on iPad Issue 15 The Word of the Day popovers on the iPad are implemented in two steps. First, the /wotd.json request is made to get the basic word information. Then a request is made for that word. The popover is only created when the word request is made. Sometimes the Word of the Day button appears somewhat unresponsive, since in extreme cases no popover may appear for a couple of seconds after the button is tapped.
-
Word of the Day not persistent Issue 42 Each Word of the Day has an implicit expiration time (which may become explicit in a later version of the API). Once it's successfully retrieved, there's no need to get a new WOTD until that expiration time has passed. This should be recorded in the DB's daily_words table as on the server or otherwise stored on each device.
-
Remote FAQ not ideal Issue 43 Having a web-based FAQ has certain virtues, but for one thing, where the main web-based FAQS (http://dubsar-dictionary.com/faq, http://m.dubsar-dictionary.com/m_faq) link to word entries in their respective webapps, it's not easy to link from the web-based FAQ in an iOS app to local word views. Further, though the counts ought to be the same, the web-based FAQS count rows in the server's database. It would be nice to have the iOS FAQ count rows in the local database now. And of course, the FAQ is unavailable if the network is out. Text formatting with UIKit is a bit tedious, and the iOS FAQ will lose the benefits of centralized distribution. But it's probably a good idea eventually to make the FAQ consistent with the rest of the app.
Dubsar requires iOS 4.2 or higher. Dubsar has been primarily tested on an iPad 2 and and iPod Touch 4G, both running iOS 4.3.5. It has also been verified to work on iOS 4.2 and iOS 5 Beta.