Nearly all CPUs used by your devices, from computers to tablets to phones, now contain multiple CPU cores. With a multi-core CPU, your computer can literally do multiple things at one time, which is called multiprocessing. And with a little careful planning, your Xojo apps can use multiprocessing for significant performance improvements in your apps.
Comments closedYear: 2013
As of July 23rd, Xojo is now available in the Ubuntu Software Center. Did you know you can also easily make your Xojo-created Linux apps available in the Ubuntu Software Center?
Comments closedI’ve discovered a way to potentially speed-up your Internet access. Before we get to that, it occurs to me that the way in which computers find each other on the Internet may be a bit of a mystery to many. If you’d like to understand how it all works read this first.
Your devices (computers, tablets and smartphones) are constantly accessing their assigned DNS server and since they often can’t continue until a response is received, the speed of your DNS server can have a big effect on the speed of your Internet access. If you’re using any of the Internet classes in Xojo, this will of course affect the performance of your apps as well. Not all DNS servers are created equal. You are probably using one at your Internet provider and it may not be the fastest DNS server available to you. But with all the DNS servers out there, how can you know which one is fastest?
Comments closedIs it possible to put a Xojo-made application in the Mac App Store?
The answer is simple: Absolutely.
However, it can be a lot of work and you’ll have to pay heed to Apple’s rules regarding the Mac App Store and follow their very stringent requirements.
Comments closedMake it easier to launch Xojo web apps- add them to your iOS device’s home screen.
To add a web app to the home screen, you open it using Mobile Safari and then click the “Sharing” button and choose “Add to Home Screen”.
Managers, Coordinators, Purchasing Agents, Xojo has got you covered! Did you know you can assign Xojo licenses from your account to other accounts? Assigning a license to a member of your team gives them access to that Xojo license, while you retain the ability to revoke and extend those licenses.
This blog post steps through a license owner assigning their Xojo license to an end user.
TL;DR Go to go your Team pages. End users share their connection key with the license owner, then owner connects with end user’s account by adding that connection key. Now, the owner can assign licenses to anyone they are connected with from their Licenses Page.
Comments closedGood bug reports are like art or great code. Often you can’t say specifically what it is about the piece of art that appeals to you, or what makes a certain piece of code great- but you know them when you see them.
Comments closedIf you use WebSessionContext in your Xojo web projects, you’re probably aware by now that they’re not working very well. I thought I’d take a few minutes to tell you what’s going on and how we’re planning to fix it.
What is a WebSessionContext anyway?
First of all, a quick description of what WebSessionContext is supposed to do for you. WebSessionContext is a mechanism for accessing a particular existing WebSession from within an area of your application that would otherwise not know where it belongs. These include Threads, Timers, System Events, App Events, etc. Normally you could tell because you would get a SessionNotAvailableException when trying to access a particular WebSession in your code.
Comments closedNow that you have tried Xojo, you’re probably thinking of creating stand-alone apps. Maybe you are considering selling your app or maybe you just want to share your app with some friends.
So now you are ready to build and deploy your apps, and to do that you need a Xojo license. No problem, Xojo has a straightforward licensing scheme.
Perhaps you already knew, but with desktop apps it has always been considered bad form to directly access any part of your user interface from within a Thread. Alas, even though this was frowned upon, it generally worked in most of your desktop apps.
Starting with 2013r1, this no longer works with Xojo for Cocoa apps. If a Cocoa app tries to access the UI from a thread, a ThreadAccessingUIException is raised. But what exactly does “accessing the UI” mean? In the case of Cocoa, it means any access to a built-in property or method on any UI control or Window. You can access your own methods or properties added to control subclasses as long as they do not access the UI themselves.
Comments closed