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.
Xojo Blog Posts
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?
I’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?
We regularly get customers asking if it is possible to put a Xojo-made application in the Mac App Store.
The answer is simple: Absolutely.
However, you’ll have to pay heed to Apple’s rules regarding the Mac App Store and follow their very stringent requirements.
Make 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”.
Do you work with other developers and need to manage their Xojo licenses? Good news! You can easily assign licenses from your Xojo account to your coworkers’, giving them access to tech support and other features from their own Xojo account.
Good 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.
We’ve talked about the importance and the value of good bug reports before:
Great Bug Reports
The Importance of Feedback
Or try this Google search: writing good bug reports
It can never be stressed enough that a good bug report is the BEST way to see that your particular bug gets reviewed and action is taken sooner rather than later. Here are a few facts that you should always include in your bug reports:
If 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.
Now that you have tried Xojo, you’re probably thinking of creating stand-alone builds of your app. Maybe you are considering selling your app or maybe you just want to share your first app with some friends.
You already know the Xojo IDE is free to use for developing, testing and debugging on any platform. But, now you are ready to build and deploy your apps, and to do that you need a Xojo license. No problem, Xojo has a simple and straightforward licensing scheme.
These are the available licenses and prices:
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.