The web framework got some love in Xojo 2016r2… General Changes First, the Web Framework now has support for Retina/HiDPI in supported browsers. All controls…
Comments closedAuthor: Greg O'Lone
“Retina” is the name for high resolution screens on Mac and iOS devices while “HiDPI” is the Windows equivalent. For simplicity, I’ll use HiDPI (which really is the universal technical term) for the rest of this blog post. Now that we have HiDPI support in Xojo, if you app doesn’t use any pictures, you can simply open your project, click on Shared under Build Settings and turn on the “Supports Retina/HiDPI” option. That’s all you need to do to have a HiDPI version of your app!
Having said that, if you are creating or using pictures in your project, there may be a few adjustments you’ll need to make to your code. A little over a year ago the process of making sure we had all of the necessary graphics together to build a Retina/HiDPI IDE was added to my to-do list. While 95% of the icons created for the Xojo IDE in 2013 already existed, most of the graphics that made up the IDE itself did not, and the IDE itself needed a bit of an overhaul to get it ready for the big change, both in graphics and in code…
2 CommentsAt Xojo, we work with a lot of HTTP REST APIs. So many in fact that I’ve spent time creating custom test harnesses to make sure that whatever I was currently coding would be compatible as well as being a test suite just in case the API changed in some subtle way (whether it be a bug fix or an API refactor gone awry). The problem with the custom test harnesses is that they’re not very portable and you end up having to create a new one for each API that you interface with.
Comments closedHTMLViewer on the desktop has two engines that you can select from, Native and Webkit. Native uses the built-in browser engine on each platform – Webkit on OS X, Internet Explorer on Windows, and Webkit on Linux, if it’s installed. If you select “Webkit”, the Chrome Embedded Browser libraries are included with your built app and HTMLViewer will use that instead. There are pros and cons to each, but usually the reason people choose WebKit over Native on Windows is because choosing Native gets you whatever the minimum version of Internet Explorer is for a particular OS. This means:
Comments closedOne of the most popular Xojo Cloud feature requests was to add database support. On Tuesday Feb 10th, we added MySQL and Postgres databases for Xojo Cloud. In addition to having a database server right on your Xojo Cloud server, we have also enabled the creation of SSH Tunnels so you can connect directly to the databases using a 3rd party management tool.
Comments closedAbout two years ago a Feature Request was filed for the Web Framework to allow users to handle incoming requests in standalone apps for things which would normally return an HTTP 404 Missing Page error. At the time, there were a few obstacles in our way which prevented bringing this request to fruition, but no more…
Comments closedIn the spring of 2011, we added an event to the WebApplication class called HandleSpecialURL which was intended to give developers a way to create their own API endpoints within a web app, and we mostly succeeded…
Comments closedOne of the most highly requested features for Xojo Cloud since its release in March 2014 has been the ability to transfer files to the server using a client other than the Xojo IDE. Now you can…and it’s really easy to use.
Comments closedThere’s a sneaky little, well hidden fact about how differently typed fields act on iOS.
Comments closedIn Xojo 2012r2 we released the Web Control SDK, making it easy for anyone to create custom web controls for use with the web framework. Prior to that, some of you created web controls using a method that was not officially supported. The purpose of the Web Control SDK is to provide a way to create controls that is supported and will continue to be supported in the future.
Comments closed