2014 – Page 8 – Xojo Programming Blog

Using the new If operator

Published March 12, 2014 by Paul Lefebvre

In Xojo 2014 Release 1 there is now an If operator that can return a result.

Comments closed

IDE Improvements in Xojo 2014 Release 1

Published March 11, 2014 by Paul Lefebvre

Xojo 2014 Release 1 includes several IDE improvements to general performance, the Inspector, tabs and auto-complete.

Comments closed

Introducing Xojo Cloud

Published March 9, 2014 by Paul Lefebvre

Introducing Xojo Cloud , the best way to build web apps is now the best way to host them. Xojo Cloud is Secure , Easy and Maintenance Free and the 1-click hosting will make deploying your apps quick and simple!

Comments closed

Picking A Language At Runtime

Published March 5, 2014 by Norman Palardy

One frequent request we get is to make it so users can run an application in any language that an app is built for and NOT the one the OS would use (for OS X see this blog post, Windows and Linux aren’t quite so dynamic).

But sometimes we get requests to be able to create an application that can run in a language that is NOT the same one used by the OS.

Comments closed

Flappy Bird in Xojo

Published March 3, 2014 by Paul Lefebvre

Did you know there is a clone of Flappy Bird written in Xojo?

Comments closed

Extension Methods: What can I extend?

Published February 21, 2014 by Norman Palardy

In Xojo, extension methods are methods that, while not part of the original definition of a type, are treated as though they are part of that data type.

Comments closed

The Real Reason Behind the Canvas/ContainerControl Transparent Property

Published February 13, 2014 by William Yu

When we added this property to the Canvas and ContainerControl there was probably a lot of head scratching going on. Some of you probably asked yourself (or us) “Why is this necessary?” or “Isn’t this pretty much the same thing as enabling DoubleBuffer?”

Well, yes to the latter question on Windows, and a slightly more optimized experience on OS X, but the impetus behind this property was really our redesigned IDE. More specifically, it was a need/requirement because of a long standing issue with our Linux framework.

Comments closed