Tips – Page 30 – Xojo Programming Blog

Guest Post: A Few Little Xojo Code Performance Tips by Eric Gibbon

Published August 5, 2015 by Xojo

Eric Gibbon has been using Xojo to develop bespoke cross-platform applications for Mac and PC and for the web for 15 years. He lives in Stamford, England, and is an active member of the Xojo UK User Group.

There’s an old programmer’s saying: If it works, leave it alone. But sometimes we have to go back to code that works to make it go faster, because it’s too slow.

Over time I have picked up some tips on how to get better performance from Xojo code. I have used these tips to improve old code running on all platforms and have seen big improvements. They are quick and easy to do.

Comments closed

Time for a Reminder to Backup Your Data

Published July 31, 2015 by Paul Lefebvre

If you work with computers, having backups of your data is essential. This particularly came to light recently with people testing out Apple Music and discovering that it could make a mess of your iTunes library. In fact, this happened to me!

But “luck favors the prepared” and I had backups, so this Apple Music glitch only proved to be an annoyance and not a catastrophe.

In my case, I just restored my iTunes library from my Time Machine backup. But I know far too many people that don’t even have any type of backup system in place. I’m here to help.

Comments closed

Source Control Solutions

Published July 28, 2015 by Paul Lefebvre

Anyone who is developing software, even if they are the only person working on the project, should be using source control (aka as version control). As you can see, this comes up a lot:

Comments closed

Code Editor Tip: What code goes with what?

Published July 9, 2015 by Norman Palardy

The code editor tries to help you see what code groups together. For instance, it draws small lines between matching block beginning statements like IF, SELECT CASE and their closers (END, END IF or END SELCT):

Comments closed

Your Anti-Virus Software and Xojo

Published June 11, 2015 by Jason Parsley

We’ve occasionally heard from Xojo users that their anti-virus software gives them a warning about Xojo. All of these have been false positives and we ask that you report these to your virus software makers if it happens to you.

Comments closed

Casting about in both 32 and 64 bit worlds

Published June 8, 2015 by Norman Palardy

Consider the following code:

dim i64 as Int64 = 1234567
dim i32 as int32 = 7654321

i32 = Int32(i64) // cast
i64 = Int64(i32) // cast

i32 = Ctype(i64, Int32) // convert
i64 = Ctype(i32, Int64) // convert

It all seems reasonable enough. Not useful, but seems reasonable. Only one problem. It won’t compile. Why not? The two casts to int32 and int64 will fail. Now why is that?

Comments closed

Operator_Lookup and ParamArray

Published May 15, 2015 by William Yu

Operator_Lookup and ParamArray are two language features that have been in Xojo for a while now, but most probably don’t know why they were originally added. The need grew out from having to support COM on Windows.

Comments closed

HTTPSocket, now with support for HTTP 1.1

Published May 6, 2015 by Paul Lefebvre

With Xojo 2015 Release 2, most of the new Xojo framework is available for all project types. This includes Xojo.Net.HTTPSocket, which adds support for HTTP 1.1.

Comments closed

Xojo Framework: Working with JSON

Published April 16, 2015 by Paul Lefebvre

Much of the new Xojo framework is available for all project types staring with Xojo 2015r2. The Data namespace includes two methods for dealing with JSON data: GenerateJSON and ParseJSON. This is how they are used in comparison to JSONItem in the old “Classic” framework.

Comments closed

Using Using

Published April 15, 2015 by Paul Lefebvre

With Xojo 2015 Release 2, much of the new Xojo framework is now available for use in all project types. Because the new Xojo framework uses namespaces, you might want to take advantage of the Using command to help make your code easier to read and write.

But first, a brief aside about namespaces. The Xojo framework uses namespaces to provide better grouping of related features and to allow for classes with the same name to co-exist (Xojo.Core.Dictionary and Dictionary, for example). In fact, you can mix classic framework code and Xojo framework code together in the same method!

Comments closed

Category: Tips