Paul talks with Tom Catchesides of Light Blue Software about how he started using Xojo, the experience of migrating a FileMaker app to Xojo, surnames and retro computers. Don’t miss this fun-filled episode!
Comments closedYear: 2016
I’m sure you’ve all seen the iOS Mail app, which displays the number of unread messages in a small red badge in the top right of the app icon. You can do this too with your Xojo app and the magic of the Declare command.
Comments closedIn a previous post we saw how to implement the Singleton Design Pattern in our Xojo apps. Now, it is time to look at another useful Design Pattern you can use in your apps: the Observer Design Pattern. This one solves the kind of question “How can the ‘x’ controls be automatically notified every time there are changes on ‘y’?” Sound interesting? Let’s see how!
In fact, this is the first of a two part series regarding the Observer Design Pattern. This one will focus on how easy is to implement using the interfaces already available in Xojo for UI controls like the PushButton, the BevelButton, and also for the Timer class. In Part 2, we will see how to implement the Observer Design Pattern from scratch, using our own Classes and Interfaces, so it will be easier to understand the mechanisms behind this Pattern and how to use it.
Comments closedXojo is a popular way to create cross-platform apps for Windows, OS X, Linux, Raspberry Pi, web and iOS. I’m not surprised because Xojo makes creating software fast and fun! Xojo really is the best way to create cross-platform software.
Comments closedOne of the best things that Xojo offers to programming newcomers is that they can simply jump-in and start to write code. In a matter of a few hours they’ll have a functional app! Nothing new here. (Or for not-so-newcomers, a fast way of creating a functional prototype from a idea).
Methods, properties, controls, any member that you add to project items can have its own scope. What is the scope? The scope essentially describes the code-wise accessibility of the member.
Comments closedSome years ago, Xojo introduced the ability to use Computed Properties, something that is present in other programming languages too and is based on the use of dedicated methods to assign and retrieve the property value itself. So, in other programming languages, the first of these dedicated methods (or functions), the Setter, is the one invoked every time we want to modify the value of the associated property, while the Getter method is the one used from our code to retrieve the associated value. The Object-Oriented Programming (OOP) concept found behind this feature is Method Overloading. Nevertheless, let’s make clear that Xojo Computed Properties are not methods. They aren’t! But they make our life as developers much easier compared with regular Properties.
Comments closedIn this episode of XojoTalk, Paul talks with Jim Meyer, who uses Xojo for NCAA stat tracking, home automation, workflow automation and much more.
Comments closedAnyone who has built an app in Xojo has used the Listbox method AddRow to create new rows. The iOSTable control in Xojo also has an AddRow method. However, unlike building a desktop app, AddRow is not always appropriate for iOS apps.
Comments closedMicrosoft refactored their core app runtimes in 2015. They have made what they call a “Universal C Runtime” which has been distributed via Windows Update to all supported versions of Windows that stay up-to-date (which is the default behavior for Windows Update).
Starting with Xojo 2016r1, the Xojo Windows framework has been updated to use the latest Microsoft tools. This allows Xojo to stay up to date and allows the Windows support to be improved in future releases. This means that Xojo itself now uses the new Universal Runtime and your built apps now require it.
Comments closed