It has been a great and a busy summer for us here at Datalogics! There have been a lot of activities taking place:
- We are learning and working on EPUB 3 support
- We are testing ACS 6 from the ACS 6 prerelease from Adobe
- We have signed up a few customers to the prerelease program (so let us know if you are interested!)
- DL Book Club is adding a new theme, and a few related books, every month. So come and check it out at bookclub.datalogics.com
In addition, we are keeping an eye out for the upcoming releases of Xcode 6 and iOS 8 from Apple. We don’t know when Apple will announce the big release date but it will be here soon; and we will be ready! Our engineering team is busy working on integrating iOS 8 support into DL Reader. This also means that we will be supporting building both RMSDK and DL Reader in the new Xcode 6 environment.
There are two parts to working this: (1) adding the ability to build both RMSDK and DL Reader under the new (now in beta) Xcode 6, and, (2) making necessary changes, almost entirely in DL Reader, to be compatible with iOS 8 (also in beta). Both aspects of this are underway so that we can deliver solid, improved products when that magical day arrives (Rumors we’ve heard say September 10th!)
In addition to the iOS 8 work and necessary changes to incorporate some new UI design guidelines from iOS 8, we are also improving our general UI in DL Reader to provide better user experience. We are improving the RMSDK and DL Reader for our customers who rely on us to deliver a robust platform for them to expand and build upon. While we are doing this, we will also be building better DL Reader apps for end users who download our apps from various app stores and markets.
Speaking of the end users… On the other end of the iOS spectrum, we will be discontinuing the support for iOS 5. This will enable us to build better quality products that are easier to expand and maintain for newer iOS . But don’t panic! We hear you that there are end users who can’t or don’t have time to update to new versions of iOS, they are still using iOS 5 apps. We still want to support you, so we are going to create a separate reading app using the current version of DL Reader in the App Store and make this app available for download on iOS 5 devices. Of course, new features will not be added to this app. The current version of the DL Reader will be updated with the new iOS 8 support in the App Store once iOS 8 comes out.
We will follow up with more blogs as soon as we have more details from our engineering team on the new iOS 8 support, as well as the version of the DL Reader for download to iOS 5 devices.
Today, we are going to start with an important question : where do your Android applications store their data? Do you know off the top of your head? Do you use internal storage or external storage? Are you writing the data to a private location that only your application can read or are you writing to a public directory?
When we started working with Reader Mobile SDK and developing our DL Reader sample eBook application, we were new to the world of developing applications for Android and Android was still relatively young. For the past 4 years, we have stored data in DL Reader for Android in a few different places (depending on what kind of data it is). We have never gone back and thought through why the data was being stored where it is; it was just a given “this is where this type of data goes and this other location is where this other type of data goes.” We did not have good answers to some parts of our storage architecture and so we are reevaluating whether the decisions we made should stay or go!
Summer is (sadly) beginning to wind down, and people are squeezing in travel plans before the fall chill rolls in and the kids head back to school. People’s travels may take them to national parks, white sandy beaches, busy metropolitan cities or the quiet countryside; perhaps the English countryside of West Yorkshire where the famous literary Brontë sisters grew up. The three sisters, Charlotte, Emily and Anne, are the focus of the Datalogics’ Book Club theme for August.
Charlotte, Emily, and Anne Bronte are well known for enjoyable classics such as Jane Eyre, Wuthering Heights and The Tenant of Wildfell Hall. The sisters, as well as their younger brother, Branwell, began writing at a young age. They had a childhood rich with imagination, writing complex collaborative stories for Branwell’s toy soldiers. As the children grew, so did their writing. They went on to author poems and novels (often using pen names) that were ahead of their time. Our book of the month is Charlotte’s Jane Eyre. First published in 1847, this is a coming of age story for the title character as she enters adulthood and falls in love with the enigmatic Mr. Rochester. Mr. Rochester hired her as a governess for his ward, but mysteries and questions abound at Thornfield Hall. It has been said that some of the events in Jane Eyre are loosely based on the incidents of Charlotte’s life, such as losing parents and siblings at a young age, having a tragic experience at boarding school, and spending time as a governess.
Other Brontë novels available in the Datalogics Book Club for you enjoyment are Wuthering Heights, Agnes Grey and The Tenant of Wildfell Hall.
We hope you enjoy these perfect vacation novels as much as we do before the summer ends.
Some time ago we posted an overview blog article on Adobe Content Server Permissions. As one of the three follow-up posts, this blog will cover what happens when you apply certain combinations of permissions to a book and try to do certain things with that book. This post in particular is the last in the series and will cover copying permissions. It is not dependent upon the previous post covering reading or the post covering printing. However, if you are new to ACS permissions, it may help to read our permissions overview blog first.
We’ll start with the glossary to define some terms, followed by a few use cases. Afterwards we’ll explain some of the caveats and best practices for using reading permissions.