Skip to content

Xojo Programming Blog Posts

We’ve Done This Before: A Net Neutrality Solution

We’ve Done This Before: A Net Neutrality Solution

Published January 30, 2018 by Geoff Perlman

As I’ve written before, the FCC’s claim that rolling back Net Neutrality will result in more competition (which presumably will be better for consumers) is flawed because of the cost of the last mile. What that means, in summary, is that over the last 30 years various cable and telecom companies have bared the cost of laying all the cable/wire necessary to bring internet service to most of the homes and businesses in US cities. They did this because city governments were more than willing to trade the enormous cost of creating a citywide network for the provider having (in most cases) an effective monopoly on providing internet access.

This isn’t the first time a service or utility has evolved in this manner in the United States. The railroads, the telegraph and later telephone service were all networks that were developed in much the same way.

Continue readingWe’ve Done This Before: A Net Neutrality Solution
Comments closed

Avoiding False-Positive Virus Detection in Windows Apps

Published January 29, 2018 by Geoff Perlman

Viruses continue to be a big problem on Windows. As a result, anti-virus software can be a bit over-zealous about detecting what it believes to be apps that have viruses embedded within them. We have had reports over the years that apps made with Xojo are sometimes falsely identified as being infected with a virus. This sometimes occurs because the 32-bit Xojo compiler puts executable code in a location where the anti-virus software doesn’t expect to find it. We’ve seen this occur even when users are debugging apps from the IDE. Fortunately in that case, there’s a fairly easy solution.

Continue readingAvoiding False-Positive Virus Detection in Windows Apps
Comments closed
Compilers 105 – Back End Overview

Compilers 105 – Back End Overview

Published January 29, 2018 by Paul Lefebvre

Once the front end has done its work its time for the back end components to take over.

This is the fifth in our compiler series and the first on the back end. We covered the parts of the compiler that are called the front end in these posts:

Continue readingCompilers 105 – Back End Overview
Comments closed

How to Add User Interface Controls at Runtime

Published January 26, 2018 by Javier Menendez

Admit it – this is one of those questions that, sooner or later, arise to every Xojo newcomer: How can I add new UI controls to the Window at runtime? And if you are considering this too, then the good news is that the answer is more simple than you probably expect… sitting right there on the Inspector under the Attributes tab. Yes, this is all about the Control Set!

Continue readingHow to Add User Interface Controls at Runtime
Comments closed

Supporting Multiple Cores

Published January 25, 2018 by Norman Palardy

With today’s multi-core CPU’s it seems that an application made with Xojo running on a single core is somewhat restricting. If you have a lot of data to process, large images to manipulate or other things that could happen in the background, it would seem that with a multi-core machine you could do this faster “if only Xojo would make threads preemptive”. We get a lot of requests for preemptive threads so that people can take advantage of multiple cores.

Continue readingSupporting Multiple Cores
Comments closed
Compilers 103 – Semantic Analyzer

Compilers 103 – Semantic Analyzer

Published January 22, 2018 by Paul Lefebvre

The Semantic Analyzer is the real heart of the compiler. Its job is to validate code and figure out what the code actually means. Essentially it validates that the code is semantically correct.

This is the third post in our Compiler series. Previous posts:

Continue readingCompilers 103 – Semantic Analyzer
Comments closed
THIS IS NOT A DRILL: Poor Interface Design and its Potentially Dangerous Impact

THIS IS NOT A DRILL: Poor Interface Design and its Potentially Dangerous Impact

Published January 16, 2018 by Geoff Perlman

As most of you know, this past Saturday morning, the people of Hawaii got a shocking notification on their smartphones warning of a incoming ballistic missile and that this warning was not a drill. I can only imagine the fear that raced through the minds of more than a million people. This warning, as well all now know, turned out to be a false alarm accidentally set off by a state employee who was attempting to perform an internal test.

Continue readingTHIS IS NOT A DRILL: Poor Interface Design and its Potentially Dangerous Impact
Comments closed