Skip to content

Category: Learning

Iterators

One feature that was added in Xojo 2014r3 that I haven’t seen much discussion about yet is iterators. In short, iterators are a way to make classes useable with the existing For Each loop feature.

Comments closed

Coding To Be Lazy

I know a lot of people like to write their local variable declarations like this:

dim i, i, j as integerdim k as double, s as string, b as boolean

Personally, I don’t and the reason is not that I like typing…

Comments closed

Guest Post: Learning Xojo

Bob Keeney has been an active member of the Xojo community since 2001. BKeeney Software has offered Xojo consulting work for 15 years with happy clients all around the world. Bob blogs regularly on Xojo and developer topics at www.bkeeneybriefs.com.

I think that Xojo is an amazing product. Clients love the simplicity and power of Xojo which is not found in many software development products. Part of what makes it a great product to work with is the wide array of options to learn more about the language- whether it’s for someone who’s new to programming trying to get an introduction to the language or for an experienced programmer trying to do a deep dive into the framework and what Xojo is capable of.

Comments closed

Oh, Say Can You C?

There is a “bug” here, can you spot it?

dim s as string = "abc" + chrb(0) + "def"
dim c as cstring = s
if s = c then
  msgbox "Yay our software works as we expected!!!!"
else
  msgbox "BOOOOOO!!!!"
end if
Comments closed

Guest Post: Managing Database Schema Control Over Multiple Versions

Wayne Golding has been a Xojo developer since 2005. He operates two IT companies, a Network/Systems services co & DRNine11 an offsite backup & DR co. Though he primarily uses Xojo for internal management systems and utilities, Wayne’s hobby is robotics where he uses Xojo to communicate with Arduino devices.

When distributing applications with a database component you will undoubtedly upgrade your database schema as your application matures. So how do you manage the schema within your application?

Comments closed

Shadowing: You can’t always get what you want (or expect)

Shadowing is when a subclass defines a constant, property or enumeration (almost anything that is not an event or a method) that has the same name as a constant, property or enumeration (but not an event or a method) in the superclass. Generally the best rule is avoid using the same names for constants, properties and enumerations that the superclass has already used.

Comments closed