Creo 1.1.5

This version, even if it is a minor release, introduces a lot of improvements and usability enhancements.
A complete release note is available from https://docs.creolabs.com/creo/version-history.html but I’d like to point out in detail some of them.

Search Panel
After so many user requests we finally introduced an advanced search panel that let’s you perform complex searches within the project. Searches are performed both in object’s properties and in source code.

When selected, the search result automatically loads the correct object/code.

Error reporting
This was one of the most requested feature. Error reporting is hard and we wanted to expose it in the right way. We invested a lot of time and we are now able to reports a lot of details about runtime and compile time errors.

When you press the Go To Error button the correct source code is loaded and selected.

NULL objects
By default messages sent to NULL objects are silently ignored and sometime this can cause confusion and misleading behaviours to your app. If you want to catch unknown messages sent to NULL you can just activate the check in Creo preferences.

SQLite Databases
SQLite databases dropped to assets are copied into app bundle when you build your IPA. App bundle is a read-only location and so if you need to update your database file at runtime (on a real iOS device) you are forced to copy the file in a read-write location. This requires some checks and operations usually performed during application launch time. We decide to give you a way to automate this frequent task by using a simple checkbox from the SQLite database inspector.

If you select a Copy Action other than none then Creo will transparently take care of all the details for you.

This version also introduces a couple of important features:

Enjoy this new version!


CreoPlayer no longer available

This evening I was sitting on my sofa with my wife and my newborn daughter when I received a call from San Jose. It was Apple. The guy from the other part of the phone informed me that Apple no longer accept CreoPlayer like applications and the only supported way to test apps is to use TestFlight.

I asked if there was anything we can do in order to prevent this from happening and he kindly replied NO. The decision was already made and he called me just to inform us that our CreoPlayer app would be removed after the phone call.

On iTunesConnect I can see that the official rejection reason is:

Guideline 2.5.2 – Performance – Software Requirements

Your app appears to be designed for clients or users to preview apps prior to being submitted to the App Store for review. This type of design allows you to change your app’s behavior or functionality to differ from the intended and advertised primary purpose of your app, which is not in compliance with App Store Review Guideline 2.5.2 and section 3.3.2 of the Apple Developer Program License Agreement.

Next Steps

It would be appropriate to use TestFlight to invite users to test your apps before you release them on the App Store.

When Apple called, we were watching a movie about a small Italian village, worldwide famous for the incredible taste of the wine it produces. That wine is known all around the world thanks to its quality and for the passion put every single day by its passionate producers. The same passion and determination drove us during the past years and our hard work lead us to create some incredible technologies.

There is nothing we can do against Apple’s decision. The only thing we can do is to create something that our users will love even if CreoPlayer will be no longer available on App Store.

Please note that nothing will change for Creo desktop and for all the new projects we plan to release in the upcoming months. We are currently investigating alternative ways to let you better test your apps.

P.S. we are thinking about the opportunity to release CreoPlayer as open source


Creo 1.0

Creolabs team is incredibly proud to announce the immediate availability of Creo 1.0.

Creo 1.0 is a huge milestone for us and we raised the bar so high that our ultimate mission is to change how people design and develop software and we really need all your support and help. We have already started working on several new incredible technologies and we really can’t wait to show you all of them in the upcoming weeks.

Thanks a lot again for your invaluable support.
Marco Bambini
Creolabs CEO and Founder


Creo 1.0b19

Creo 1.0b19 contains several new features and some important fixes.

This version contains tons of changes and it also contains several changes that can affect your existing code.

We completely rewrote some controls like Toolbar, Tabbar and SegmentedControl. In the previous version you was forced to configure all their items from within the inspector with a very bad user experience and some issues due to the fact that individual items cannot be easily accessed via code. With the introduction of the new subnodes feature, items are exposed in a more natural and easy to use way.
The old project need to be converted to a new format and a self explanatory warning message will show you if your old code needs to be updated.

We also rewrote the Database and RecordSet classes. In particular all indexes inside a RecordSet are now 0-based (was 1-based) so you probably need to upgrade your code. All Databases methods now accept a pair of closures (onSuccess and onFailure parameters) so you have control about the asynchronous or synchronous execution of all the methods.

Keyboard customization and input views are now supported (via subnodes) from within the TextView and TextField controls.

Subviews can now be created just dropping controls inside an existing view.

All know issues and crash bugs has been fixed and b19 is considered features completed.
Complete version history is available here.

CreoPlayer has also been updated to version 1.0.17.

Expects a final 1.0 release pretty soon!