Microsoft is ending Windows XP support in April. Here are some suggestions to help you switch to a newer version of Windows.
Month: January 2014
For several years now, Apple has been telling developers to stop using QuickTime and move to AVFoundation, Apple’s preferred API for audio and video. This past June at WWDC, Apple took the next step labeling QuickTime as deprecated meaning that it would be receiving no further love and would eventually disappear entirely.
As we posted in September of last year, Microsoft announced that Windows XP, which was released 12 years ago, will no longer be supported after April 8, 2014. Our information tells us that only 3% of Xojo users are using Xojo on Windows XP. Supporting XP is limiting our ability to move Xojo forward on the Windows platform. Therefore, starting with Xojo 2014r1, we will no longer support Windows XP for the IDE itself.
One of Xojo’s features we’ve focused on improving recently is the Profiler. For me, the work has been immensely useful as it has permitted me to hunt down certain code paths that were quite slow.
A little over a year ago, we started adding the features that were needed to directly support SSL connections in standalone web apps. We ran into a few issues during beta testing which blocked our ability to release at that time and the feature was pulled.
A recent flurry of questions regarding this feature, and the addition of Travis Hill to the web framework team this fall, prompted us to look at this feature again. It turns out that the items which were blocking the release of this feature got fixed as a result of other bug fixes in the fall and we have been able to confirm that standalone SSL does in fact work! If you’re using Xojo 2013r3 or higher, you should be able to actually use them!
We continue to work towards Xojo support for iOS. Since the last update, we have been working on support for Auto Layout. We demonstrated Auto Layout at XDC last year. However, at the time we only had support for it in the framework; not the IDE. In case the term Auto Layout is unfamilar to you, it’s a technology for controlling the size and postion of controls. In Xojo today, you use the locking properties. We determined early in the development of our iOS framework that locking would not be sufficent for iOS since the user will often radically change the size of the layout by rotating the device. Instead of locking, you will use Auto Layout. Think of it as locking on steroids.
While no one likes to admit it, we all write software that has bugs. Recently, I was analyzing some code that seemed to be slower than desired in the Xojo IDE and I literally stumbled on a bug that has very likely been causing issues in VCP projects for a while.