Blog about the Xojo programming language and IDE
Posts related to web development.
The most direct way to support HiDPI* for custom controls is to draw into the Graphics object passed into the Paint event. That graphics object is already configured with the appropriate scale factor and double buffering- the entire control will be handled correctly by the framework if the DoubleBuffer property is set.
*As with other posts, we’ll use “HiDPI” to refer to both HiDPI on Windows and Retina on OS X.
2 Comments“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 CommentsMost of us build apps without thinking too much about how much memory the app will need. Sure sometimes you end up creating an app that is a real memory buster but that’s unusual. With virtual memory, gone are the days when your app would just run out of memory and crash, or are they?
Comments closedAre you a consultant that uses FileMaker to create solutions for your clients? Do you work in an office and use FileMaker to run your company’s business?
Comments closedOn Tuesday, January 12th Microsoft is ending support for Internet Explorer 8, 9 and 10.
Comments closedBy default the built-in Web Browser that is used on Windows to show web pages uses the Internet Explorer 7 rendering engine. Which means the Xojo HTMLViewer and the ActiveX WebBrowser controls also use this older rendering engine.
Comments closed
UPDATE: Xojo Retina is here, April 2016
Comments closedI’m seeing more and more headlines about how citizen developers are helping create the apps that business need.
In particular, a recent article at ZDNet, “The advent of the citizen developer” talks about how non-programmers can help create the apps needed by an enterprise company:
So the business-side has long had to place their fate in the hands of those with the requisite skills but often with little sympathy for or first-hand knowledge of the business itself. Or they just ended-up acquiring pre-existing software that was a close enough fit, and then had it configured to their needs. Neither path has typically produced tech solutions that fit business needs very well, and ‘good enough’ has usually been the mantra of the day.
These articles explain how “citizen developers”, sometimes referred to as a business analysts (or maybe even power-users), are using rapid application development tools to create apps that helps the business solve a problem more quickly than going through a more formal and lengthy IT process.
Comments closedAs you may have heard, Xojo 2015 Release 3 added the long-awaited ability to create 64-bit apps. And it also added the ability to create Raspberry Pi 2 apps (Linux ARM). This now means there are lots more apps that can get built.
Comments closedFormatting SQL for display can sometimes be a pain, particularly for the many different flavors of SQL. One easy way to do the formatting is to use a web service.
Comments closed
