|
|||||
|
In a previous post, we walked through the process of building Qt using the LTIB tool, but we were a bit cavalier about the steps involved. Since that time, we’ve been shipping demo software based on LTIB and Qt with our Nitrogen53 and Nitrogenboards, and the lack of documentation shows. In order to remedy that . . . → Read More: Revisiting LTIB and Qt on i.MX51 and i.MX53 Here’s another favorite for fixed-point Android users. How do we skip the home screen and go directly into our own custom application on system start? Once again, this is an easy change to make, and we really don’t even have to mess with the framework code to make it work. If you have any Android . . . → Read More: Booting into your own application on Android While working with a multi-touch display under Android recently, I had some questions about what data was being received from the touch screen, which is connected to our Nitrogen53 board over i2c. My early debug steps involved instrumenting the kernel, but I really wanted the quicker cycle time of the i2c-tools package. It turns out . . . → Read More: i2c-tools under Android Android’s user-focused, touchscreen-driven interface lends itself well to fixed-point applications such as kiosks and control panels. However, since it was originally designed for mobile devices, there are a few features that need to be tweaked. For example, Android puts itself to sleep after a certain amount of inactivity. You may not want your device to . . . → Read More: Disabling sleep mode on Android The default screen orientation for the Android-ready Nitrogen and Nitrogen53 is landscape. That’s fine for most people, but say you want it in portrait. Or upside down, or whatever. That’s a problem, since Android usually takes rotation instructions from code that expects motion sensor input, and since most Nitrogen use cases don’t need the board . . . → Read More: Set Android default orientation to portrait mode Now that we’ve covered the internals, we can talk a little about how the surface application should look. As a reference we’ll use the AOSP’s own default Camera app; you can find the source here. It’s a lot of code, so we’ll do a lot of skipping through looking for the important stuff that you . . . → Read More: How to write an Android camera app "We need to go deeper" That’s kind of how I felt as a naive software intern thumbing through the vast amount of information in the Android source code. There’s a lot to take in: Android covers an enormous set of use cases, and it follows a secure and extensible model that requires function calls . . . → Read More: Camera subsystem overview for i.MX Gingerbread In the previous two blog posts, we described how you can integrate a mag stripe reader and barcode scanner into the Qt Webkit framework by using the Qt Webkit Bridge. In this post, we’ll build upon those two examples by integrating a proximity smart card (RFID) reader, which is somewhat more complicated because it allows . . . → Read More: Qt Webkit with Proximity Smart Card (RFID) on Freescale i.MX51 In our previous post we described how you could hook up a magnetic stripe reader to the Qt Webkit browser using the Qt Webkit Bridge and a relatively simple set of C++ code. This approach of using C++ to write extensions for Webkit isn’t specific to magnetic stripe readers, though. Once in C++, the entire . . . → Read More: Barcode input to the Qt Webkit browser At Boundary Devices, we’re relative newcomers to the world of Qt, but we were somewhat surprised to learn about Nokia’s decision to favor Windows CE instead of MeeGo for future smart phone designs. It’s hard for us to say what the right direction may be for the cell-phone marketplace; nevertheless, we’re very impressed with the . . . → Read More: Qt Webkit and Javascript magnetic stripe example |
|||||
|
Copyright © 2012 Boundary Devices - All Rights Reserved |
|||||
