Movie Explorer Pro 2.1.2: Compatibility update
Movie Explorer Pro 2.1.2 fixes some compatibility and other issues with TMDb and with iTunes, or the Apple TV app if you are using Catalina.
Missing posters fix
As part of a maintenance project of TMDb, a lot of posters and other artwork has been deleted. This may lead to missing thumbnails in Movie Explorer, especially for movies and TV shows older than 2 years. The following has been implemented in Movie Explorer, to deal with the image deletions of TMDb:
- Automatic poster updates: Movie Explorer will now automatically search for an alternative image when the image reference stored in the catalog is no longer available in the local cache or on the TMDb image server.
- Batch update: all posters for movies, TV shows and discs can also be updated in one operation. To to this, choose
File>Update Postersin the menu. There are two poster update options:- Update missing images: this will only update the images that cannot be found in the local image cached or that cannot be downloaded from the TMDb images server, using the image reference in the catalog.
- Overwrite all images: this will update all poster art for the selected categories. Use this option if you want to export your catalog to PDF or HTML.
Core Data Lab 1.1: Cached object models, and much more
Version 1.1 of Core Data Lab contains a mix of some new ‘must-have’ features, some fixes to cover exotic Core Data ‘use cases’, and new features that wouldn’t exist without the feedback of a few seasoned Core Data developers.
New features
The following features are new in Core Data Lab 1.1:
- Object creation functions: the Data menu has been extended with a ’New Object’ menu item to add new objects for the selected entity, and a ’New Related Object’ menu item to add new objects for the selected Core Data relationship.
- Core Data Model Cache option: the Core Data Object Model that’s cached in the database can now be used as object model in a Core Data Lab project. This is especially useful for developers that generates their object models during runtime (yes, they do really exist!) or when you want to investigate a database without having access to the corresponding compiled object model. Disclaimer: if you have a model file, it’s still better to use that in your project. The existence and actuality of a model cache in the database is not guaranteed. Also the implementation can change at any moment. This feature is supported on macOS 10.15 or newer.
News Explorer 1.9.8 for iOS: Automatic Reader view & more
Version 1.9.8 of News Explorer for iOS and watchOS contains some useful new features, fixes and tons of small improvements. It is also the last planned iOS update before News Explorer 2.0, which is scheduled to be released somewhere this dramatic year.
Automatic Reader view
News Explorer now supports automatic Reader view: when enabled, News Explorer automatically chooses the correct processing for each article, in order to show the full article. This feature is based on the following two new settings:
- Default primary view is a new setting in the Reading section of the News Explorer Preferences. With this you can configure a default setting for the primary view of all your feeds. You can for example open all your feeds using Mercury Reader. This default setting can be overruled on feed level.
- Skip feeds with full articles is a new sub-setting which is available when setting Default primary view is set to Mercury Reader or Arc90 Readability. When enabled, articles of feeds with full articles are not processed by the chosen reader view engine. For example, Cult of Mac articles will be processed to retrieve the full article text, while MacRumors articles will be left alone because they are already complete.
Core Data Lab 1.1, Public Beta
The introduction of Core Data Lab has been received with great enthusiasm by the Apple developer community. Especially after Dave Verwer mentioned Core Data Lab in iOS Dev Weekly, which happens to be one of the most popular newsletters for Apple developers. During this short semi-viral period we received feedback with some interesting ideas, fatal crash scenarios, several ‘glitches’, and more. This all resulted in development of version 1.1, which is a mix of some new ‘must-have’ features, some fixes to cover some exotic Core Data ‘use cases’, and new features that wouldn’t exist without the said feedback.
Core Data Lab, an introduction
Almost all our apps use Core Data to store all kinds of data. This means that during development, we often want to have direct access to the SQLite data from our Core Data apps, in order to check things, detect errors, diagnose problems, discover data trends, and more.
As a Core Data developer you can use regular SQLite viewers to access this data. But it is never really fun or convenient to work with these apps. They don’t know anything about the underlying Core Data Model, so they can't visualize data relationships, they display entities and fields with strange prefixes, show field values in an unpractical way. Many SQLite apps have not been maintained for years, or are not even native macOS apps, so you often have to get used to all kinds of strange GUI stuff.
There are already a few dedicated Core Data viewers. But these are often functionally limited, or have features that are already in Xcode, such as Core Data code generation, or have not been maintained for years and are therefore plagued with bugs and outdated GUI concepts.
So we started to develop a tool ourselves. Over the last few years, our in-house Core Data viewer has grown so much that it would be a waste to keep it to ourselves. So we decided to transform the tool into an attractive app for other developers, and place it on the Mac App Store for a reasonable fee. The proceeds will allow us to maintain the app properly, provide support and add new useful features.
