-
Notifications
You must be signed in to change notification settings - Fork 2
Release Notes 1.1.1
Version 1.1.1 provides some cosmetic fixes for iOS 6 and the Retina 4 display as well as a couple of minor bug fixes.
January 8, 2013
-
Corrected search result sort order when matching inflections Issue 44 Now if you search for frozen, you'll get freeze (v.) and frozen (adj.) in that order as exact matches at the top, before full text matches.
-
Fixed incorrect help text Issue 45 This affected a number of pointer types. Instance hyponym is one. Now in the Sense and Synset views, these will be listed as "Instance hyponyms," and the help text will say, "instances of this class."
-
Fixed incorrect aspect ratio on Retina 4 display Issue 46 Now the application can use the full screen on an iPhone 5. In particular, this means that the user will see up to 5 suggestions from the autocompleter instead of just 3.
Build 1.1.1.2 was submitted 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 now requires iOS 4.3 or higher, since that was the lowest option available in XCode 4.5. Dubsar has been primarily tested on an iPad 2, an iPod Touch 4G and an iPhone 5, all running iOS 6.