Fork us on GitHub

Faster iOS Builds, GUI Builder Improvements & SQL Updates

We've been working on smoother builds and tools
Faster iOS Builds, GUI Builder Improvements & SQL Updates

Faster iOS Builds, GUI Builder Improvements & SQL Updates

I’ve recently noticed that distribution build sizes were identical for appstore and debug builds which wasn’t the case before the xcode 7.x migration we did a while back. This shouldn’t be the case as it indicates that the standard debug builds include both the 64bit and 32bit code which is redundant during debugging.

We made some changes that should apply for the next update this Friday that might double build speed for some of you as it will do less work during compiling but also produce a smaller binary.

I would also recommend unchecking "include source" which slows down the build as the zip and upload of a huge file slows down the whole process

GUI Builder Update

I wanted to put out a new demo today and I have something really nice on the way…​ But then we decided to do it with the GUI builder which resulted in about 15 issues so far.

So the good news is that we are improving the GUI builder and tracking down bugs/inconveniences etc. The bad news is that we’ll need to wait for a nice new demo for next week as this is pretty difficult.

We also added quite a few cool new features to the GUI builder such as:

  • Ability to refresh to see the list of images added to the designer

  • Ability to add a new image directly from the GUI builder without launching the designer

  • UIID editing that allows us to pick from a list of UIID’s in the theme

And quite a few other features.

SQL Updates

Steve made some changes to the SQL Javadocs to clarify some SQL limitations in the JavaScript port.

Besides the lack of portability for the SQL support there (due to the fact that SQL is not an official W3C standard), there are two big issues:

  • Transactions can’t be mapped properly - the browser support for SQL wraps transactions in a very different way and this can’t map to the Java side.

  • There is no database file so the trick of shipping a database file with your app and installing it won’t work!

Ideally I’d love for us to have a better object persistence solution that will remove the need for SQL in the long term.

Share this Post:

Posted by Shai Almog

Shai is the co-founder of Codename One. He's been a professional programmer for over 25 years. During that time he has worked with dozens of companies including Sun Microsystems.
For more follow Shai on Twitter & github.