Introducing the “Welcome to Xojo” Bundle!

New to Xojo and looking for guidance? We've put together a terrific bundle to welcome you! Xojo Bundle

This bundle includes six back issues of the magazine -- all of year 21 in printed book and digital formats -- plus a one-year subscription (beginning with 22.1) so you'll be learning all about Xojo for the next year. It's the perfect way to get started programming with Xojo. And you save as much as $35 over the non-bundle price!

This offer is only available for a limited time as supplies are limited, so hurry today and order this special bundle before the offer goes away!

Article Preview

Buy Now

Issue 15.6 ('Green Screen Saver')
Instant purchase and download via GumRoad!



Issue: 15.6 (November/December 2017)
Author: Scott Boss
Author Bio: Scott Boss is the founder of Nocturnal Coding Monkeys, Llc, who specialize in writing custom software. Scott has been a developer, system administrator, storage engineer, consultant, and architect to businesses from startup to global 100.
Article Description: No description available.
Article Length (in bytes): 5,260
Starting Page Number: 90
Article Number: 15611
Related Web Link(s):


Excerpt of article text...

This month we are going to discuss a solution that extends Xojo Web Edition. Xojo Web Edition is great at creating web applications. But Xojo Web Edition is weak for creating websites. That is where Aloe (http://aloe.zone) by Tim Dietrich comes in.

Aloe extends the functionality of Xojo Web Edition so it can serve static pages or templated pages better than Xojo Web Edition can natively (see Figure 1).

This is not Tim's first foray into extending Xojo Web Edition: he's also made Luna (http://timdietrich.me/luna/), XWF (http://timdietrich.me/xwf/), and others.

Hal Gumbert has just recenty updated his Xandu (https://campsoftware.com/products/xanadu-for-xojo.php) product to use Aloe over using XWF. Xandu is Hal's way of replacing Filemaker Web version with a Xojo-based system.

Now if we look at the code, Aloe utilizes the HandleURL or HandleSpecialURL event to process the WebRequest.

In this example, we are using the HandleURL event. (If we were to use HandleSpecialURL, there would be either an /api/ or /special/ in the URL path.) Look at the example code below. As you can see, it's very straight forward. We just take the WebRequest object and hand it off to a method to process it.

...End of Excerpt. Please purchase the magazine to read the full article.