Very recently I needed to improve the generation tens of thousands of images with a Xojo Desktop project. The image generation code had already been written, and takes advantage of several desktop specific features (custom font activation with MBS most specifically).
The process took minutes originally. It was so bad that the initial author of the code stuck a confirmation dialog to the user prior to running the batch. Now, because of the world events, the batches were larger than ever. On a whole it had to be improved.
Obviously the best way to speed this up was to split the batch into chunks for helper processes. This was going to be a new adventure in Xojo for me, and I was ready to take a bite.
Continue reading Appception: Helper Apps
Deploying a standalone Xojo Web app for the first time may look unfamiliar or confusing. One might look at the built product and wonder where the files are. None of this ends in .asp, .cgi, or .php; and where is index.html?
I promise, this whole package makes things easier for developers. With a Xojo Web app, the built product is the web server. Once it’s running, the web app handles everything for us.
So how does a Xojo Web app get running? There are a few “easy button” solutions. One is, of course, Xojo Cloud the built in service. Additionally, there is at least one third party hosting service dedicated to Xojo Web apps. These tools can simplify deployment, but require that a developer relies on customer service when there’s a problem.
For mission critical applications, DIY-ers, and cost conscious developers the option to deploy to a Linux server might be a more appealing choice.
Continue reading Xojo Web: What to Do After You Click Build