![xojo blog xojo blog](https://www.xojo.com/assets/img/casestudies/everweb.png)
It would be a challenge for a large, well funded, and well staffed development company to achieve that goal. Over the past 9 months, I’ve begun to think that Xojo's goal of being a rapid application development platform, that can be used to develop native desktop, mobile, Web, and console apps, and can compile to multiple targets (macOS, Windows, Linux, iOS, Web, and eventually Android) is simply too ambitious. However, there are no timeframes associated with the features - not even rough estimates.Ī Difficult Goal, and A Difficult Decision The list is helpful in that it shows the order of importance for the upcoming features. It lists everything that the Xojo team is either currently working on or planning to implement at some point. In July, Xojo posted a development roadmap.
![xojo blog xojo blog](https://blog.xojo.com/wp-content/uploads/2020/01/wpxojologoupd.png)
They're nowhere to be found in Xojo 2019 R2.
#XOJO BLOG ANDROID#
But for now, there's really not much benefit in using it, at least not for me and the type of work that I'm doing these days.īut what about the other features that I mentioned in that post from January? Android Support. I think API 2.0 is a step in the right direction, and that its benefits will become more clear over time.
#XOJO BLOG CODE#
We now have legacy code that needs to be carefully examined and in many cases modified in order to run properly. To some extent, I think Xojo has done that. In my post from January, I described API 2.0 as an "attempt to modernize Xojo." I think it's also an attempt to standardize the language and make it a little easier for newcomers to learn. The primary change in this release is API 2.0. It just seemed logical that most, if not all, of those features would be available as part of Xojo's 2019 releases. Some of the features that I listed in that post had been "in the works" for what had seemed like a very long time. To give you an idea of how it is to integrate check out this screenshot of the 'App.It's been exactly 9 months to the day that I wrote "Xojo in 2019: What I'm Looking Forward To." At the time, I honestly expected that everything mentioned in that post would be available this year.
#XOJO BLOG HOW TO#
It demonstrates how to map the folders and the Xojo Web app presents links to test the functionality very quickly. The example project demonstrates two distinct static folders with a PDF, image, and text file. It is a drop in module that extends the 'App' object of your Xojo Web project making integrating it super simple. The code we are presenting on GitHub today allows you to easily map folders to the Xojo Web application to be served as static content. It would be great if you could simply write your static files to a sub-folder inside of your app directory and serve those files directly.
![xojo blog xojo blog](https://slidetodoc.com/presentation_image/5b38f409de143f8ccf140f458f6dcdd0/image-9.jpg)
The other obvious downside is you now need a secondary web server and domain/sub-domain to serve these files. So it requires extra configuration to get your Xojo standalone app to be able to write to a specific folder of another domain. The problem at ServerWarp is we isolate your apps and domain web servers from each other to protect from vulnerabilities and provide the most secure environment. What if you want to email your user a link to the download? You can only access files that way if you have an active Xojo Web session. Technically the "WebFile" class works for this purpose but the user and development experience is a bit subpar especially for mobile clients.
#XOJO BLOG PDF#
In order to serve those PDF reports they have often relied on writing those PDF files to another directory of another domain or subdomain because Xojo Web could not natively serve those files. This is especially useful if you are running standalone or load balanced apps and do not want to depend on another web server.įor example at ServerWarp we host many load balanced applications for customers. Now available on GitHub is open sourced code to help you serve static files from your Xojo Web application.