Yesterday I posted about an issue with type checking in Delphi (and other Pascal) compilers. As mentioned in that post, range checking is fundamentally flawed as a supposed solution to the problem for reasons that are explored further in this post.
A brief post on a long standing omission in type checking in Pascal and the limitations of Range Checking as applied to the problem.
When discussing mobile device application development using Oxygene or other RemObjects Elements technologies, the question of user interface designers doesn’t usually take long to come up (particularly with Delphi developers). Up to now the answer has always been Xcode Interface Builder for iOS/OS X, Visual Studio WinForms/WPF Designers for .Net and… um… your favourite text editor for Android (if you don’t like the XML editing facilities in Visual Studio).
But not for much longer.
In the run up to the announcement of the new iPhone 6 and the Apple Watch, Apple also revamped iTunes Connect, the portal through which apps are submitted to the App Store. Unfortunately the new interface has a number of problems which I
spent wasted hours dealing with yesterday.
As of the XE7 release of Delphi/RAD Studio, the long deprecated BDE is finally dead. And almost properly this time.
So Saturday morning I finished the iOS version of my application and published it to the App Store. Of all of the app stores, the approval process with Apple evidently takes the longest. So, whilst waiting for my app to be released, I developed (and published) the Windows Phone version of my app.
Earlier this week I mentioned that I had published my TXT-2-PARK app for Android in the Google Play Store. Today I published the iOS version to the Apple App Store (still awaiting approval at this stage). As with the Android version, I implemented the iOS version using Oxygene, and things proved a little less straightforward.
On Saturday I was out and about with my family and found myself inspired to write an app. By Sunday evening, it was done and in the Google Play store.