Xojo on iOS
Creating apps for iOS is coming this year
Issue: 11.3 (May/June 2013)
Author: Marc Zeedar
Author Bio: Marc taught himself programming in high school when he bought his first computer but had no money for software. He's had fun learning ever since.
Article Description: No description available.
Article Length (in bytes): 18,541
Starting Page Number: 52
Article Number: 11307
Related Link(s): None
Excerpt of article text...
Undoubtedly the biggest sessions of all of XDC (Xojo Developer's Conference) were Joe Strout's on iOS. Everyone wanted to see just how far iOS has progressed since last year, and wanted a little more depth into the process than Geoff Perlman's brief demo in the Keynote provided.
Joe demonstrated the same app as Geoff, but went into more detail. He explained that many of the basic controls have some cool options. For instance, the Imageview control—which is similar to the rather useless ImageWell on the desktop—includes four scale modes which set how its picture displays inside the control. You can specify
fitto display the picture with no adjustment, stretch its longest edge to fit into the control, crop it, or just resize the image so it fits unproportionally into the control. The same control also has an on/off frame option, as well as a background setting (clear or a color).
There are also clever new classes, such as
CappedImage: that's an image where the endcaps aren't stretched when you adjust the control size (only the middle portion is enlarged). It's ideal for things like rounded-corner buttons.
Like Geoff, Joe showed how the onscreen keyboard is automatic when editing text (with Xcode, the developer has to manually move controls out of the way). But Joe pointed out a detail I had been wondering about: the onscreen keyboard
doesn'tpop up when you're using a Bluetooth keyboard. It's all automatic with Xojo.
New Framework and Namespace
For iOS, Xojo includes a new framework. This is necessary because iOS is similar, but different from other platforms, so something like a Listbox doesn't quite translate to iOS. Joe said that his goal was to keep the best parts of the current framework while modernizing the bad parts. So we get our terminologies straight, the new framework is to be called the "Xojo Framework" while the old framework will be called the "Classic Framework."
...End of Excerpt. Please purchase the magazine to read the full article.