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?
Xojo Blog Posts
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?
Is 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.
Do you work with a team of 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 specific to that license from their own Xojo account. This solution is also great for companies with a purchasing department – one manager can purchase and control assigning, revoking and renewing all their Xojo licenses as needed.
Assigning your Xojo license to a team member allows that developer to use their own Xojo account to access the Xojo Forum, get tech support and report cases in Feedback. Follow these simple instructions to pair your accounts and then assign your licenses. Remember, all Xojo license is a single-user licenses, so an assigned license can only be used by the team member you assigned it to.
Let’s step through OwnerMarie assigning a Xojo license from her account to DevJason’s 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.
If you have been around the Mac community long enough, you may have ended up with two Apple IDs. I have one for iTunes and another one that came from MobileMe. This resulted in effectively having two iCloud accounts. This can be inconvenient and probably will become more so in the future. Apple doesn’t provide a means to merge Apple IDs. They know they need to provide this, but they do not yet do so. I, however, have found a way.
Since the introduction of iCloud, I have wanted to have a single Apple ID. When Apple recently added the two-step authentication for Apple IDs to make them more secure, I decided to sign in and update my Apple ID account. Part of the process is to verify a device you own which will be used, along with your password, to authenticate that you are who you say you are should you want to make changes (such as your password) to your Apple ID in the future. The webpage said it would list my devices, but none were listed. It didn’t take long to figure out why. The Apple ID I was updating was for iTunes, while the Apple ID Apple was using to find my devices was the one associated with my iCloud (MobileMe/mac.com) account.